Metric not respected on routing
MS team, I think that the metric is not being respected as people have suggested in this forum. I have a wired connection, intended to be the default and a wireless connection to connect to a NAS via a gateway router. My intent is for the wireless router to be be used only in order to reach clients on its network: IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.109 30 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.15 10 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 192.168.0.0 255.255.255.0 On-link 192.168.0.109 286 192.168.0.109 255.255.255.255 On-link 192.168.0.109 286 192.168.0.255 255.255.255.255 On-link 192.168.0.109 286 192.168.1.0 255.255.255.0 On-link 192.168.1.15 266 192.168.1.15 255.255.255.255 On-link 192.168.1.15 266 192.168.1.255 255.255.255.255 On-link 192.168.1.15 266 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 192.168.0.109 286 224.0.0.0 240.0.0.0 On-link 192.168.1.15 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 192.168.0.109 286 255.255.255.255 255.255.255.255 On-link 192.168.1.15 266 =========================================================================== Persistent Routes: None However, all traffic appears to be heading off down the wireless route (the 0.1 interface). Why? The metric for the wired route is lower but no traffic is going that way (the 1.1 interface). I have also gone into the Advanced section of the adapters and made sure the wired route is the top priority in the list. What am I doing wrong here? Regards, Jeremy
December 28th, 2012 6:45am

Hello, It seems to me a static route should be set up like: 192.168.0.0 255.255.255.0 GW-> 192.168.0.1 0.0.0.0 0.0.0.0 GW -> 192.168.1.1 This way default traffic goes out of 1.1 and only traffic destined for the NAS goes out of 0.1 wireless. IMHO, I think this should be better done some other way. I'm not sure Windows is going to do a good job of routing in a multi-homed environment. Miguel Fra | Falcon IT Services, Miami, FL www.falconitservices.com | www.falconits.com | Blog
Free Windows Admin Tool Kit Click here and download it now
December 28th, 2012 8:10am

Same problem for me. I have a UDP VPN, which if connected leaves me with no internet as the metric is being ignored. The 192.168.8.17 interface is the VPN, once connected I have no internet or access to anything over the VPN as Windows is trying to use it as the default gateway despite having the highest metric. Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.8.1 192.168.8.17 19998 0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.20 2 Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 192.168.8.1 9999 0.0.0.0 0.0.0.0 10.0.0.1 1
January 8th, 2013 4:43pm

Hello, You have 0.0.0.0 with two gateways, Windows will not do a good job here because it will send traffic out the first interface that's active, in linear fashion. You can turn on RRAS if you have a server product to get IGRP and use two gateways otherwise remove one of the gateways because Windows will not do a good job when multi-homed RIP is used. http://windows.microsoft.com/en-US/windows7/Configuring-multiple-gateways-on-a-network Miguel Fra | Falcon IT Services, Miami, FL www.falconitservices.com | www.falconits.com | Blog
Free Windows Admin Tool Kit Click here and download it now
January 10th, 2013 6:29am

A VPN connection will usually disable your Internet connection. By default it will make the VPN connection the default gateway and change the metric of your normal DG so that it is not used (so that all traffic goes across the VPN link). If you are using the Microsoft VPN client you can alter that by changing the "Use default gateway........" setting in the connection properties. See KB254231 . Bill
January 10th, 2013 7:07am

My VPN uses a TAP adapter and I have manually set interface & route metrics correctly so it should never try to use the VPN for internet. The whole point in route metrics is to prefer a specific route, so it should not even try to use my VPN for internet (unless I bind to that interface) as the metric is set to the maximum.
Free Windows Admin Tool Kit Click here and download it now
January 10th, 2013 1:26pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics