Router add bug.

oycol527 · 2024-08-03 01:53

The routes added when the configuration is activated for the first time will not take effect, and will only take effect when it is activated for the second time.
If a gateway exists in the system when the configuration is activated for the first time (the gateway is not affected during activation), the routes from the first activation will be added to the network card of the gateway, resulting in duplicate routes when activated for the second time.

oycol527 · 2024-08-03 01:57

Operating system version: win11
Software version: 5.3.2

NetSetMan Support · 2024-08-08 08:33

The route feature is just a GUI for the Windows route.exe command line tool. All commands are executed one after each other and you will see the results in the activation log that you can open at the bottom of the activation dialog. We don't see how this would only work when activated second time. Please review the activation log for further details.

oycol527 · 2024-08-19 03:14

Hello， this is the process of replicating the bug.
The picture doesn't look clear. An external chain was used. https://upload.cc/i1/2024/08/19/eFbRPC.png

Last edited by oycol527 (2024-08-19 03:20)

oycol527 · 2024-08-19 03:19

The picture doesn't look clear. An external chain is used

NetSetMan Support · 2024-08-19 14:32

In the activation log shown in your screenshot, you can the command that is used to apply the configured route:

route add 30.55.32.0 mask 255.255.240.0 30.55.41.126

The rest is done by Windows or its route.exe tool. If the outcome is not as expected, then we need to analyze the circumstances in detail.

You have not configured the IF/Interface parameter. While is is generally possible, it has its limitations.
First of all, if IF is not provided, it is determined by the gateway. In your case, you are setting the IP settings manually, but are not setting any gateway. This constellation is not defined by Microsoft, so the outcome might not be as expected.
Please have a look at the description provided by Microsoft:
"When the if parameter is omitted, the interface is determined from the gateway address."
https://learn.microsoft.com/windows-ser … ute_ws2008

Another aspect to consider is the fact that the route table is applied immediately after changing the IP settings. While is is generally no problem if you provide all necessary parameters, it might be an issue if some of the parameters have to be determined automatically and your adapter is not 100% ready to do this.

Please try providing the Interface parameter in your settings.
If that still does not work as expected, disable the route option in NetSetMan, activate your profile and then open a command line window and run the route command manually to see the result. If this leads to the same problem, then the cause is not a malfunction but an incorrect configuration. Try finding a solution that works manually (outside of NetSetMan), then it can be applied to a profile to automate the process.

oycol527 · 2024-08-21 14:16

I think the adapter under the current configuration file will be used when the if parameter is empty. Maybe this will be a feature request rather than a bug request。

Last edited by oycol527 (2024-08-21 14:18)

NetSetMan Support · 2024-08-21 16:33

We don't think it would be a good idea to automatically add parameters to the route configuration that the user did not provide. There can be valid reasons to leave the IF parameter empty, which is usually no problem if the gateway is not left empty on purpose.

oycol527 · 2024-08-23 02:36

However, responsibilities as a Hardware Handover and Maintenance Worker， I think this is not a good idea, because when I need to configure, I will configure a separate route for each USB adapter（2 or more)（one adapter one network）, rather than letting the system decide , multiple gateways will cause routing conflicts, therefore, detailed routing is requiredand. The USB adapter may not be the same every time when I connect to the same network, so manually configuring the if parameter every time means that I need to check this every time when I use netsetman, this gets more complicated as I work on more projects.

NetSetMan Support

#1 2024-08-03 01:53

Router add bug.

#2 2024-08-03 01:57

Re: Router add bug.

#3 2024-08-08 08:33

Re: Router add bug.

#4 2024-08-19 03:14

Re: Router add bug.

#5 2024-08-19 03:19

Re: Router add bug.

#6 2024-08-19 14:32

Re: Router add bug.

#7 2024-08-21 14:16

Re: Router add bug.

#8 2024-08-21 16:33

Re: Router add bug.

#9 2024-08-23 02:36

Re: Router add bug.