I have upgraded to firmware 3.0.0.4.260 and everything is fine, rock solid. I now want to try the VPN server so that I can get an RDP session from the Internet into a Windows 7 host on the local network. The VPN setup was quick and painless and my remote system (also Windows 7) has successfully made an encrypted connection to the VPN server.
I cannot see the local network hosts from the remote and pings fail to route. My routing table on the remote host looks like this when the VPN is active (edited):
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.34 4245
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.33 4250
0.0.0.0 0.0.0.0 On-link 192.168.10.2 21
127.0.0.0 255.0.0.0 On-link 127.0.0.1 4531
127.0.0.1 255.255.255.255 On-link 127.0.0.1 4531
127.255.255.255 255.255.255.255 On-link 127.0.0.1 4531
192.168.1.0 255.255.255.0 On-link 192.168.1.34 4501
192.168.1.0 255.255.255.0 On-link 192.168.1.33 4506
192.168.1.33 255.255.255.255 On-link 192.168.1.33 4506
192.168.1.34 255.255.255.255 On-link 192.168.1.34 4501
192.168.1.255 255.255.255.255 On-link 192.168.1.34 4501
192.168.1.255 255.255.255.255 On-link 192.168.1.33 4506
192.168.10.2 255.255.255.255 On-link 192.168.10.2 276
192.168.47.0 255.255.255.0 On-link 192.168.47.1 4501
192.168.47.1 255.255.255.255 On-link 192.168.47.1 4501
192.168.47.255 255.255.255.255 On-link 192.168.47.1 4501
192.168.56.0 255.255.255.0 On-link 192.168.56.1 4501
192.168.56.1 255.255.255.255 On-link 192.168.56.1 4501
192.168.56.255 255.255.255.255 On-link 192.168.56.1 4501
192.168.74.0 255.255.255.0 On-link 192.168.74.1 4501
192.168.74.1 255.255.255.255 On-link 192.168.74.1 4501
192.168.74.255 255.255.255.255 On-link 192.168.74.1 4501
192.168.86.0 255.255.255.0 On-link 192.168.86.1 4501
192.168.86.1 255.255.255.255 On-link 192.168.86.1 4501
192.168.86.255 255.255.255.255 On-link 192.168.86.1 4501
[X.X.Y.Y] 255.255.255.255 192.168.1.1 192.168.1.34 4246
224.0.0.0 240.0.0.0 On-link 127.0.0.1 4531
224.0.0.0 240.0.0.0 On-link 192.168.47.1 4502
224.0.0.0 240.0.0.0 On-link 192.168.86.1 4502
224.0.0.0 240.0.0.0 On-link 192.168.74.1 4502
224.0.0.0 240.0.0.0 On-link 192.168.1.33 4507
224.0.0.0 240.0.0.0 On-link 192.168.56.1 4502
224.0.0.0 240.0.0.0 On-link 192.168.1.34 4502
224.0.0.0 240.0.0.0 On-link 192.168.10.2 21
255.255.255.255 255.255.255.255 On-link 127.0.0.1 4531
255.255.255.255 255.255.255.255 On-link 192.168.47.1 4501
255.255.255.255 255.255.255.255 On-link 192.168.86.1 4501
255.255.255.255 255.255.255.255 On-link 192.168.74.1 4501
255.255.255.255 255.255.255.255 On-link 192.168.1.33 4506
255.255.255.255 255.255.255.255 On-link 192.168.56.1 4501
255.255.255.255 255.255.255.255 On-link 192.168.1.34 4501
255.255.255.255 255.255.255.255 On-link 192.168.10.2 276
===========================================================================
Both remote and local hosts have VMWare and VirtualBox installed that provide additional network segments, that's why there are "extra" local network segments there.
The VPN adapter Network Connection Details panel (General>Details):
Connection-specific DNS Suffix:
Description: HomeVPN
Physical Address:
DHCP Enabled: No
IPv4 Address: 192.168.10.2
IPv4 Subnet Mask: 255.255.255.255
IPv4 Default Gateway:
IPv4 DNS Server: 192.168.1.1
IPv4 WINS Server:
NetBIOS over Tcpip Enabled: Yes
This looks odd, shouldn't the default gateway be the WAN address of the VPN Server? the Details tab for the VPN adapter does show that WAN address as the Destination address, however. Which settings can I adjust to get the routing correct so that I can connect to the local hosts?
I have seen oblique references in other (and older) threads to set up static routes but weren't much more specific. There's routing on the local host, the VPN Server/router, and the remote host. Which device gets the static routes? Should it be not necessary for this firmware release?
Any pointers appreciated.
I cannot see the local network hosts from the remote and pings fail to route. My routing table on the remote host looks like this when the VPN is active (edited):
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.34 4245
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.33 4250
0.0.0.0 0.0.0.0 On-link 192.168.10.2 21
127.0.0.0 255.0.0.0 On-link 127.0.0.1 4531
127.0.0.1 255.255.255.255 On-link 127.0.0.1 4531
127.255.255.255 255.255.255.255 On-link 127.0.0.1 4531
192.168.1.0 255.255.255.0 On-link 192.168.1.34 4501
192.168.1.0 255.255.255.0 On-link 192.168.1.33 4506
192.168.1.33 255.255.255.255 On-link 192.168.1.33 4506
192.168.1.34 255.255.255.255 On-link 192.168.1.34 4501
192.168.1.255 255.255.255.255 On-link 192.168.1.34 4501
192.168.1.255 255.255.255.255 On-link 192.168.1.33 4506
192.168.10.2 255.255.255.255 On-link 192.168.10.2 276
192.168.47.0 255.255.255.0 On-link 192.168.47.1 4501
192.168.47.1 255.255.255.255 On-link 192.168.47.1 4501
192.168.47.255 255.255.255.255 On-link 192.168.47.1 4501
192.168.56.0 255.255.255.0 On-link 192.168.56.1 4501
192.168.56.1 255.255.255.255 On-link 192.168.56.1 4501
192.168.56.255 255.255.255.255 On-link 192.168.56.1 4501
192.168.74.0 255.255.255.0 On-link 192.168.74.1 4501
192.168.74.1 255.255.255.255 On-link 192.168.74.1 4501
192.168.74.255 255.255.255.255 On-link 192.168.74.1 4501
192.168.86.0 255.255.255.0 On-link 192.168.86.1 4501
192.168.86.1 255.255.255.255 On-link 192.168.86.1 4501
192.168.86.255 255.255.255.255 On-link 192.168.86.1 4501
[X.X.Y.Y] 255.255.255.255 192.168.1.1 192.168.1.34 4246
224.0.0.0 240.0.0.0 On-link 127.0.0.1 4531
224.0.0.0 240.0.0.0 On-link 192.168.47.1 4502
224.0.0.0 240.0.0.0 On-link 192.168.86.1 4502
224.0.0.0 240.0.0.0 On-link 192.168.74.1 4502
224.0.0.0 240.0.0.0 On-link 192.168.1.33 4507
224.0.0.0 240.0.0.0 On-link 192.168.56.1 4502
224.0.0.0 240.0.0.0 On-link 192.168.1.34 4502
224.0.0.0 240.0.0.0 On-link 192.168.10.2 21
255.255.255.255 255.255.255.255 On-link 127.0.0.1 4531
255.255.255.255 255.255.255.255 On-link 192.168.47.1 4501
255.255.255.255 255.255.255.255 On-link 192.168.86.1 4501
255.255.255.255 255.255.255.255 On-link 192.168.74.1 4501
255.255.255.255 255.255.255.255 On-link 192.168.1.33 4506
255.255.255.255 255.255.255.255 On-link 192.168.56.1 4501
255.255.255.255 255.255.255.255 On-link 192.168.1.34 4501
255.255.255.255 255.255.255.255 On-link 192.168.10.2 276
===========================================================================
Both remote and local hosts have VMWare and VirtualBox installed that provide additional network segments, that's why there are "extra" local network segments there.
The VPN adapter Network Connection Details panel (General>Details):
Connection-specific DNS Suffix:
Description: HomeVPN
Physical Address:
DHCP Enabled: No
IPv4 Address: 192.168.10.2
IPv4 Subnet Mask: 255.255.255.255
IPv4 Default Gateway:
IPv4 DNS Server: 192.168.1.1
IPv4 WINS Server:
NetBIOS over Tcpip Enabled: Yes
This looks odd, shouldn't the default gateway be the WAN address of the VPN Server? the Details tab for the VPN adapter does show that WAN address as the Destination address, however. Which settings can I adjust to get the routing correct so that I can connect to the local hosts?
I have seen oblique references in other (and older) threads to set up static routes but weren't much more specific. There's routing on the local host, the VPN Server/router, and the remote host. Which device gets the static routes? Should it be not necessary for this firmware release?
Any pointers appreciated.