Hi to all!!
I have an issue with the SSL vpn client configuration.. The client is able to connect but I can see in the log the next lines (is not a complete log):
Tue Jan 10 15:57:20 2017 MANAGEMENT: >STATE:1484060240,ASSIGN_IP,,10.3.33.101,,,,
Tue Jan 10 15:57:24 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:24 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:28 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:28 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:29 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:29 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:30 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:30 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:31 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:31 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:33 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:33 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:34 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:34 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:35 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:35 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:36 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:36 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:37 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:37 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:39 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:39 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:40 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:40 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:41 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:41 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:42 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:42 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:43 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:43 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:44 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:44 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:45 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:45 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:46 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:46 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:47 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:47 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:48 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:48 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:49 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:49 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:50 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:50 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:51 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:51 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:52 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:52 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 10 15:57:54 2017 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 10 15:57:54 2017 C:\Windows\system32\route.exe ADD 172.20.35.193 MASK 255.255.255.255 192.168.1.1
Tue Jan 10 15:57:54 2017 Route addition via service succeeded
Tue Jan 10 15:57:54 2017 C:\Windows\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.3.33.100
Tue Jan 10 15:57:54 2017 Warning: route gateway is not reachable on any active network adapters: 10.3.33.100
Tue Jan 10 15:57:54 2017 Route addition via service failed
Tue Jan 10 15:57:54 2017 C:\Windows\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.3.33.100
Tue Jan 10 15:57:54 2017 Warning: route gateway is not reachable on any active network adapters: 10.3.33.100
Tue Jan 10 15:57:54 2017 Route addition via service failed
Tue Jan 10 15:57:54 2017 MANAGEMENT: >STATE:1484060274,ADD_ROUTES,,,,,,
Tue Jan 10 15:57:54 2017 C:\Windows\system32\route.exe ADD 172.20.35.193 MASK 255.255.255.255 192.168.1.1
Tue Jan 10 15:57:54 2017 ROUTE: route addition failed using service: El objeto ya existe. [status=5010 if_index=10]
Tue Jan 10 15:57:54 2017 Route addition via service failed
Tue Jan 10 15:57:54 2017 C:\Windows\system32\route.exe ADD 172.20.35.193 MASK 255.255.255.255 192.168.1.1
Tue Jan 10 15:57:54 2017 ROUTE: route addition failed using service: El objeto ya existe. [status=5010 if_index=10]
Tue Jan 10 15:57:54 2017 Route addition via service failed
Then, the system is not adding the network interface in the client laptop and the routes isn't appear anywhere... So, when I try to reach the internal LAN, the traffic goes to the client's default gateway instead going throught the SSL-VPN and the traffic is not reaching the LAN...
Any idea???
Thanks in advance!!!
Regards
David.
This thread was automatically locked due to age.