NetSetMan Support
You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2021-03-11 16:35
- -JustMe-
- Member
- Registered: 2017-02-14
- Posts: 10
Routing Tables are not applied
I've a profile which needs to have routing tables for private IP's set
10.0.0.0 mask 255.0.0.0 Gateway 10.10.10.1
I've configured this in advanced TCP-IP Settings section in NetsetMan-Pro.
In GUI I see Routeing-table activation, but when I check the result afterwards using route print, the routes are not there.
If I configure this as a script to be run after Profile activation with elevated rights
"route add 10.0.0.0 mask 255.0.0.0 10.10.10.1"
it works.
Is this a misunderstanding of the functionality from my side or a bug of the software?
Offline
#2 2021-03-11 16:50
- NetSetMan Support
- Administrator
- Registered: 2005-08-06
- Posts: 1,878
Re: Routing Tables are not applied
Please provide the basic details, like the version you are using and the activation log.
Offline
#3 2021-03-16 11:22
- -JustMe-
- Member
- Registered: 2017-02-14
- Posts: 10
Re: Routing Tables are not applied
I'm running current version 5.0.5
Not working:
Erweiterte TCP/IP-Einstellungen - Routentabelle
I see settings being applied, but they are not in OS afterwards. Route print does not show them.
Working:
Scripte & Programme - Danach
route add 10.0.0.0 mask 255.0.0.0 10.128.2.254
Option: Mit erhöhten Rechten ausführen aktiviert.
Route print shows setting being active.
Offline
#4 2021-03-16 13:16
- NetSetMan Support
- Administrator
- Registered: 2005-08-06
- Posts: 1,878
Re: Routing Tables are not applied
Please provide the activation log as already requested.
You can find it at the bottom of the activation dialog.
Offline
#5 2021-03-23 08:04
- -JustMe-
- Member
- Registered: 2017-02-14
- Posts: 10
Re: Routing Tables are not applied
Here's the log - using routing tables (Routingtabelle)
[0:00] NetSetMan Pro 5.0.5
[0:00] Start: Bonn (2021-03-23 08:01:52)
[0:00] Start: Ethernet
[0:00] Adapter gefunden
[0:00] IP: Start
10.128.3.201 : 255.255.252.0
[0:00] IP-Adresse: OK
[0:00] Subnetzmaske: OK
[0:00] IP: OK
[0:00] Gateway: Start
-
[0:00] Gateway: OK
[0:00] DNS: Start
10.128.2.17
172.16.208.11
[0:00] DNS: OK
[0:00] Schnittstellenmetrik: Start
Auto
[0:00] Schnittstellenmetrik: OK
[0:00] Adapter - Aktualisieren...
[0:02] Warten auf Netzwerk...
[0:02] Adapter - Aktualisieren: OK
[0:02] Adapter-Status: Start
Aktivieren
[0:02] Adapter-Status: OK
[0:02] Routentabelle: Start
+ 10.0.0.0 255.0.0.0 10.128.2.254/1
+ 172.16.0.0 255.240.0.0 10.128.2.254/1
+ 192.168.0.0 255.255.0.0 10.128.2.254/500
[0:02] route add 10.0.0.0 mask 255.0.0.0 10.128.2.254 metric 1
[0:02] OK!
[0:02] route add 172.16.0.0 mask 255.240.0.0 10.128.2.254 metric 1
[0:03] OK!
[0:03] route add 192.168.0.0 mask 255.255.0.0 10.128.2.254 metric 500
[0:03] OK!
[0:03] Routentabelle: OK
[0:03] System-Einstellungen: Start
[0:03] Windows Update: Start
Aktivieren
[0:03] Windows Update: OK
[0:03] Start: WLAN
[0:03] Adapter gefunden
[0:03] IP: Start
192.168.2.201 : 255.255.255.0
[0:03] IP-Adresse: OK
[0:03] Subnetzmaske: OK
[0:03] IP: OK
[0:03] Gateway: Start
192.168.2.1
[0:03] Gateway: OK
[0:03] DNS: Start
-
[0:03] DNS: OK
[0:03] Schnittstellenmetrik: Start
Auto
[0:03] Schnittstellenmetrik: OK
[0:03] Adapter - Aktualisieren...
[0:06] Warten auf Netzwerk...
[0:06] Adapter - Aktualisieren: OK
[0:06] Adapter-Status: Start
Aktivieren
[0:06] Adapter-Status: OK
[0:06] WLAN: Start
ap4Mobile
[0:06] Warten auf Netzwerk (E5023) - Wiederholen: 1
[0:07] Warten auf Netzwerk (E5023) - Wiederholen: 2
[0:08] Warten auf Netzwerk (E5023) - Wiederholen: 3
[0:12] WLAN: OK
[0:12] Ende (08:02:04)
Offline
#6 2021-03-23 08:05
- -JustMe-
- Member
- Registered: 2017-02-14
- Posts: 10
Re: Routing Tables are not applied
Routing tables are not added.
Offline
#7 2021-03-23 08:21
- -JustMe-
- Member
- Registered: 2017-02-14
- Posts: 10
Re: Routing Tables are not applied
Log with using Script exdecution
[0:00] NetSetMan Pro 5.0.5
[0:00] Start: Bonn (2021-03-23 08:18:39)
[0:00] Start: Ethernet
[0:00] Adapter gefunden
[0:00] IP: Start
10.128.3.201 : 255.255.252.0
[0:00] IP-Adresse: OK
[0:00] Subnetzmaske: OK
[0:00] IP: OK
[0:00] Gateway: Start
-
[0:00] Gateway: OK
[0:00] DNS: Start
10.128.2.17
172.16.208.11
[0:00] DNS: OK
[0:00] Schnittstellenmetrik: Start
Auto
[0:00] Schnittstellenmetrik: OK
[0:00] Adapter - Aktualisieren...
[0:02] Warten auf Netzwerk...
[0:02] Adapter - Aktualisieren: OK
[0:02] Adapter-Status: Start
Aktivieren
[0:02] Adapter-Status: OK
[0:02] System-Einstellungen: Start
[0:02] Windows Update: Start
Aktivieren
[0:03] Windows Update: OK
[0:03] Start: WLAN
[0:03] Adapter gefunden
[0:03] IP: Start
192.168.2.201 : 255.255.255.0
[0:03] IP-Adresse: OK
[0:03] Subnetzmaske: OK
[0:03] IP: OK
[0:03] Gateway: Start
192.168.2.1
[0:03] Gateway: OK
[0:03] DNS: Start
-
[0:03] DNS: OK
[0:03] Schnittstellenmetrik: Start
Auto
[0:03] Schnittstellenmetrik: OK
[0:03] Adapter - Aktualisieren...
[0:07] Warten auf Netzwerk...
[0:07] Adapter - Aktualisieren: OK
[0:07] Adapter-Status: Start
Aktivieren
[0:07] Adapter-Status: OK
[0:07] WLAN: Start
ap4Mobile
[0:07] Warten auf Netzwerk (E5023) - Wiederholen: 1
[0:08] Warten auf Netzwerk (E5023) - Wiederholen: 2
[0:09] Warten auf Netzwerk (E5023) - Wiederholen: 3
[0:12] WLAN: OK
[0:12] Warte: 3 s
[0:16] Skript (Danach): Start
StaticRoutesBonn.cmd
[0:16] Skript (Danach): Warte
[0:16] Skript (Danach): OK
[0:17] Ende (08:18:57)
Offline
#8 2021-03-23 08:23
- -JustMe-
- Member
- Registered: 2017-02-14
- Posts: 10
Re: Routing Tables are not applied
With script execution Routes are added successfully.
Offline
#9 2021-03-23 08:27
- -JustMe-
- Member
- Registered: 2017-02-14
- Posts: 10
Re: Routing Tables are not applied
Image from script added
Offline
#10 2021-03-25 19:56
- NetSetMan Support
- Administrator
- Registered: 2005-08-06
- Posts: 1,878
Re: Routing Tables are not applied
We tried to reproduce your the described problem with the exact same route table settings, but "unfortunately" it worked as expected.
Here's the starting point on one of our test systems:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.199.2 192.168.199.131 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
169.254.0.0 255.255.0.0 On-link 169.254.136.0 276
169.254.136.0 255.255.255.255 On-link 169.254.136.0 276
169.254.255.255 255.255.255.255 On-link 169.254.136.0 276
192.168.199.0 255.255.255.0 On-link 192.168.199.131 281
192.168.199.131 255.255.255.255 On-link 192.168.199.131 281
192.168.199.255 255.255.255.255 On-link 192.168.199.131 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.199.131 281
224.0.0.0 240.0.0.0 On-link 169.254.136.0 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.199.131 281
255.255.255.255 255.255.255.255 On-link 169.254.136.0 276
===========================================================================
Based on your logs, we configured these settings:
This is the activation log:
[0:00] Route Table: Start
+ 10.0.0.0 255.0.0.0 10.128.2.254/1
+ 172.16.0.0 255.240.0.0 10.128.2.254/1
+ 192.168.0.0 255.255.0.0 10.128.2.254/500
[0:00] route add 10.0.0.0 mask 255.0.0.0 10.128.2.254 metric 1
[0:00] OK!
[0:00] route add 172.16.0.0 mask 255.240.0.0 10.128.2.254 metric 1
[0:00] OK!
[0:00] route add 192.168.0.0 mask 255.255.0.0 10.128.2.254 metric 500
[0:01] OK!
[0:01] Route Table: OK
This is the result. Notice the added lines 2, 9 and 10:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.199.2 192.168.199.131 25
10.0.0.0 255.0.0.0 10.128.2.254 192.168.199.131 26
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
169.254.0.0 255.255.0.0 On-link 169.254.136.0 276
169.254.136.0 255.255.255.255 On-link 169.254.136.0 276
169.254.255.255 255.255.255.255 On-link 169.254.136.0 276
172.16.0.0 255.240.0.0 10.128.2.254 192.168.199.131 26
192.168.0.0 255.255.0.0 10.128.2.254 192.168.199.131 525
192.168.199.0 255.255.255.0 On-link 192.168.199.131 281
192.168.199.131 255.255.255.255 On-link 192.168.199.131 281
192.168.199.255 255.255.255.255 On-link 192.168.199.131 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.199.131 281
224.0.0.0 240.0.0.0 On-link 169.254.136.0 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.199.131 281
255.255.255.255 255.255.255.255 On-link 169.254.136.0 276
===========================================================================
We also would like to point out one thing:
For the routing functionality, we are not using any special API, but simply the command lines that are displayed in the activation log:
"route add 10.0.0.0 mask 255.0.0.0 10.128.2.254 metric 1"
And the next line is streamed from the command line result directly into the activation log:
"OK!"
If there as a problem with that command, there would be some error instead of "OK!".
In your activation log we can see the "OK!" results as well, so they must be successful.
As far as we know, the routing table is the same for all users, so there cannot be any account mixup either.
We are simply out of ideas why this might be failing in your case.
Could you please create a detailed screencapture video showing the whole process from start to finish and where you check for the results? Maybe that way we will notice some important detail that is currently missing.
Also please try to break this problem down. Create a profile with just the Route settings without any other settings. See if this makes any difference. Maybe one of the following settings is resetting the configuration or something like this.
Offline
Pages: 1