Sign up ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

OS: Windows 8

I have a cabled NIC (connected to router with ip and a WIFI NIC (connected to a router with ip . I want all traffic to go through the cabled NIC, except the range should use the wifi-nic.

This was working fine in Windows 7, without any manual configuration. In Windows 8 however, it's not.

My routing table:

Interface List
 14...f2 7b cb 13 e7 f0 ......Microsoft Wi-Fi Direct Virtual Adapter
 13...b8 ac 6f 54 d2 5c ......Realtek PCIe FE Family Controller
 12...f0 7b cb 13 e7 f0 ......Dell Wireless 1397 WLAN Mini-Card
  1...........................Software Loopback Interface 1
 15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 16...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface

IPv4 Route Table
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
     20         On-link    306         On-link    306         On-link    306         On-link    276         On-link    276         On-link    276     31         On-link    286         On-link    306         On-link    276         On-link    286         On-link    306         On-link    276         On-link    286
Persistent Routes:

I added the rule for I would think Windows should use this rule for the IP because it's more specific than the default-route.

However it's not:


Tracing route to over a maximum of 30 hops

  1    58 ms     4 ms     4 ms
  2    68 ms    12 ms    11 ms  ^C

So... What do I do wrong? And how can I make Windows use the wireless NIC for

share|improve this question
My route command: "route add mask if 12 metric 1" If Windows is not prefering more specific routes, and only looking to metric, how can I add a route with a lower metric than the default route? If I add a route of metric 1, a route of metric 31 (metric default route + 1) is created. So my route can never override the default route? :-/ Then how do I make Windows use another NIC for a certain IP range? – Lander Nov 26 '12 at 15:34
Have you tried disabling the route/nic it's using to see if it will actually use the one you want? just to test the connection and verify it can use it? if it works, a likely hypothesis would be that it takes the speed link into account as mentioned in the article. – Johnnie Nov 27 '12 at 6:45
any luck with this? – Johnnie Dec 1 '12 at 18:28
If I disconnect the cabled NIC, I can access the range. So what should I do to make it work, even when cabled NIC is connected? – Lander Dec 29 '12 at 16:36
OK, If I disable DHCP on the second NIC, and set a static IP but no default gateway, I can ping devices on the However, I still can't print to my networkprinter in this range. I can ping the device, but the device is "Offline". When I disconnect the wired NIC, I can print... So the question is: How do I set a route to a secondary NIC for a specific IP range, while both NIC's have DHCP enabled? – Lander Dec 29 '12 at 17:11

4 Answers 4

You can use route add -p command. It can add persistent route, which can have lower metric than 30.

share|improve this answer

Can you show the route command you used to add your route.

Generally if two routes exist for the same location, windows chooses the route with the lowest metric. Your metric for the new rout is 31 so it won't normally be chosen.

There are a couple of questions related to this as in How does Windows 7 decide which route to take if 2 connections to an internet source exist? (e.g. a Wireless and an Ethernet one to a router)

share|improve this answer

That doesn't seem to help either. It seems like the routing is looking for 'On-link' as the default GW when dialup is establishes before it routes the request through the requested interface.

For example, no default route is set;         On-link    257       On-link    257       On-link   286

The following will route through which is IF 12 but if you manually add the correct GW for the IP then it does not go through.

share|improve this answer

I had exactly same problem. In Wireshark I could see, that ping was using wrong source address. When I used ping -S hostname I could reach the host.

After disabling all NDIS items on my LAN and WIFI adapters, routes started to work as expected.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.