Route goes to wrong interface (WIN7 pro 4.3.4 activeted) / Bug Reports / NetSetMan Support

NetSetMan Support

Search for already answered questions about NetSetMan (Pro) or ask new ones

You are not logged in.

#1 2017-03-22 13:29

thorgfi
Member
Registered: 2017-03-22
Posts: 1

Route goes to wrong interface (WIN7 pro 4.3.4 activeted)

I have 2 connection,
1) WLAN with DHCP and which is default route
2) LAN which I will config with NSM (IP and route)
The IP config goes OK but when I try to config route it goes to wrong interface (WLAN, not LAN)
NSM1.png

Here is log and route print. So I tried to create route to int 11 which is LAN but it goes to int 12 which is WLAN.

           -
[0:00] Gateway: OK
[0:00] Adapter - Refresh...
[0:02] Waiting for network...
[0:03] Adapter - Refresh: OK
[0:03] Route Table: Start
           +  10.107.0.0  255.255.0.0  10.107.46.1
[0:03] route add 10.107.0.0 mask 255.255.0.0 10.107.46.1 if 11
[0:03] OK!
[0:03] Route Table: OK

[0:03] Finish (14:03:39)



s:\Wireless>route print
===========================================================================
Interface List
17...34 f3 9a b0 74 34 ......Bluetooth Device (Personal Area Network)
15...00 a0 c6 00 00 17 ......HP lt4120 Snapdragon X5 LTE Network Adapter
14...36 f3 9a b0 74 30 ......Microsoft Virtual WiFi Miniport Adapter #2
13...36 f3 9a b0 74 31 ......Microsoft Virtual WiFi Miniport Adapter
12...34 f3 9a b0 74 30 ......Intel(R) Dual Band Wireless-AC 8260
11...30 e1 71 80 b6 df ......Intel(R) Ethernet Connection I219-V
  1...........................Software Loopback Interface 1
19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
21...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
20...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
40...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4
23...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #5
41...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #6
18...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter
24...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0     192.168.43.1   192.168.43.139     25
       10.107.0.0      255.255.0.0      10.107.46.1   192.168.43.139     26
        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.43.0    255.255.255.0         On-link    192.168.43.139    281
   192.168.43.139  255.255.255.255         On-link    192.168.43.139    281
   192.168.43.255  255.255.255.255         On-link    192.168.43.139    281
        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.43.139    281
  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.43.139    281
===========================================================================
Persistent Routes:
  None

Last edited by thorgfi (2017-03-22 13:30)

Offline

#2 2017-03-22 14:30

NetSetMan Support
Administrator
Registered: 2005-08-06
Posts: 1,878

Re: Route goes to wrong interface (WIN7 pro 4.3.4 activeted)

NetSetMan provides a UI for the native route.exe tool in Windows.
In your activation log you see the command that is used:

[0:03] Route Table: Start
           +  10.107.0.0  255.255.0.0  10.107.46.1
[0:03] route add 10.107.0.0 mask 255.255.0.0 10.107.46.1 if 11

For this feature we're basically simply forwarding your configuration to the official routing tool in Windows. The result is purely based on its internal actions that we do not have control of. If you feel that the result is wrong, you can try using that command outside of NetSetMan in a native console to verify that it has the same result. If the result is the same, then we recommend reporting the issue to Microsoft or searching for a solution regarding this issue for the route.exe tool, as we don't have control over that tool.

Offline