Setting up gateway on different subnet than IP address

▲
3
▼

My provider has a (stupid) setup where the IP address for the gateway is on a totally different IP range than the assigned IP address. They insist on doing this for whatever reason. I'm trying to get Windows Server 2012 R2 configured using a static route but have had no luck. I was able to get the network configured on FreeBSD using the following configuration in /etc/rc.conf:

ifconfig_vtnet0="inet 142.4.196.xxx netmask 0xffffffff"
static_routes="net1 net2"
route_net1="-net 192.99.16.254/32 -iface vtnet0"
route_net2="default 192.99.16.254"

Is there anyway to convert this so it will work on Windows Server 2012 R2? I've tried doing route ADD 0.0.0.0 MASK 0.0.0.0 192.99.16.254 but no luck.

Here's my IP address info:

IP Address: 142.4.196.xxx
(Required) subnet mask: 255.255.255.255
Gateway: 192.99.16.254
networking
routing
windows-server-2012
gateway
asked on Server Fault May 14, 2014 by ub3rst4r • edited May 14, 2014 by ub3rst4r

3 Answers

▲
2
▼

OVH hosting does this same thing. the ip block you are assigned does not contain your gateway.

they provide per OS directions which perhaps can help you: http://help.ovh.co.uk/BridgeClient

your default route in your post will work, but you must provide a route to that gateway

answered on Server Fault May 14, 2014 by driz
▲
0
▼

You should not need to setup a static route, setting right netmask should be enough. You seem to have it set to 255.255.255.255, but you need to set it to 0.0.0.0

answered on Server Fault May 14, 2014 by phoops
▲
0
▼

After finally getting a hold of my provider, it turned out the problem was that the MAC address was wrong and thus causing it to not connect. I didn't have to add any static routes or anything to get to work (luckily).

answered on Server Fault May 15, 2014 by ub3rst4r

User contributions licensed under CC BY-SA 3.0