Попробовал. Интернет есть, но пропали доступы к внутренним ресурсам. Кстати тоже пробую на прошивке 2.60, получил ее от D-Link'а
Вот как это выглядит без ключа "
-no_gateway" :
Таблица маршрутов перед подключением SSL VPN C:\Users\admin>route print
===========================================================================
Interface List
14...00 ff 31 3d f8 b1 ......SSL VPN TAP-Win32 Adapter V9
11...08 00 27 f7 2f 23 ......Intel(R) PRO/1000 MT Desktop Adapter
1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 172.30.30.1 172.30.30.118 10
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
172.30.30.0 255.255.255.0 On-link 172.30.30.118 266
172.30.30.118 255.255.255.255 On-link 172.30.30.118 266
172.30.30.255 255.255.255.255 On-link 172.30.30.118 266
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 172.30.30.118 266
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 172.30.30.118 266
===========================================================================
Persistent Routes:
None
Таблица маршрутов после подключения SSL VPNC:\Users\admin>route print
===========================================================================
Interface List
14...00 ff 31 3d f8 b1 ......SSL VPN TAP-Win32 Adapter V9
11...08 00 27 f7 2f 23 ......Intel(R) PRO/1000 MT Desktop Adapter
1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 172.30.30.1 172.30.30.118 10
0.0.0.0 0.0.0.0 172.17.101.7 172.17.101.14 2
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
172.17.101.0 255.255.255.0 On-link 172.17.101.14 256
172.17.101.14 255.255.255.255 On-link 172.17.101.14 256
172.17.101.255 255.255.255.255 On-link 172.17.101.14 256
172.30.30.0 255.255.255.0 On-link 172.30.30.118 266
172.30.30.118 255.255.255.255 On-link 172.30.30.118 266
172.30.30.255 255.255.255.255 On-link 172.30.30.118 266
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 172.30.30.118 266
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 172.30.30.118 266
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 172.17.101.7 2
===========================================================================
Пингуем внутренний ресурсC:\Users\admin>ping 172.16.54.100
Pinging 172.16.54.100 with 32 bytes of data:
Reply from 172.16.54.100: bytes=32 time=23ms TTL=63
Reply from 172.16.54.100: bytes=32 time=56ms TTL=63
Reply from 172.16.54.100: bytes=32 time=56ms TTL=63
Reply from 172.16.54.100: bytes=32 time=61ms TTL=63
Ping statistics for 172.16.54.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 61ms, Average = 49ms
Пингуем ИнтернетC:\Users\admin>ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Ping statistics for 8.8.8.8:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss)
===========================================================================
Вот как это выглядит с ключом "
-no_gateway" :
Таблица маршрутов перед подключением SSL VPN C:\Users\admin>route print
===========================================================================
Interface List
14...00 ff 31 3d f8 b1 ......SSL VPN TAP-Win32 Adapter V9
11...08 00 27 f7 2f 23 ......Intel(R) PRO/1000 MT Desktop Adapter
1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 172.30.30.1 172.30.30.118 10
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
172.30.30.0 255.255.255.0 On-link 172.30.30.118 266
172.30.30.118 255.255.255.255 On-link 172.30.30.118 266
172.30.30.255 255.255.255.255 On-link 172.30.30.118 266
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 172.30.30.118 266
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 172.30.30.118 266
===========================================================================
Persistent Routes:
None
Таблица маршрутов после подключения SSL VPNC:\Users\admin>route print
===========================================================================
Interface List
14...00 ff 31 3d f8 b1 ......SSL VPN TAP-Win32 Adapter V9
11...08 00 27 f7 2f 23 ......Intel(R) PRO/1000 MT Desktop Adapter
1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 172.30.30.1 172.30.30.118 10
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
172.17.101.0 255.255.255.0 On-link 172.17.101.15 256
172.17.101.15 255.255.255.255 On-link 172.17.101.15 256
172.17.101.255 255.255.255.255 On-link 172.17.101.15 256
172.30.30.0 255.255.255.0 On-link 172.30.30.118 266
172.30.30.118 255.255.255.255 On-link 172.30.30.118 266
172.30.30.255 255.255.255.255 On-link 172.30.30.118 266
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 172.30.30.118 266
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 172.30.30.118 266
===========================================================================
Persistent Routes:
None
Пингуем ИнтернетC:\Users\admin>ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=16ms TTL=48
Reply from 8.8.8.8: bytes=32 time=16ms TTL=48
Ping statistics for 8.8.8.8:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Пингуем внутренний ресурсC:\Users\admin>ping 172.16.54.100
Pinging 172.16.54.100 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 172.16.54.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
===========================================================================