Menu
▾
▴
Re: [Openvpn-users] Limited Access to Subnet
|
From: John A. S. I. <jsu...@op...> - 2010-08-30 07:11:30
|
On Sun, 2010-08-29 at 10:34 -0400, Richard Munger wrote: > John, > I do not believe that the packets are getting lost. > I started the server and client. I received a successful VPN connection. > Here is what I am seeing when I do a route print from the client side: > =========================================================================== > Active Routes: > Network Destination Netmask Gateway Interface Metric > 0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.69 30 > 10.10.3.0 255.255.255.0 10.10.3.5 10.10.3.6 30 > 10.10.3.4 255.255.255.252 On-link 10.10.3.6 286 > 10.10.3.6 255.255.255.255 On-link 10.10.3.6 286 > 10.10.3.7 255.255.255.255 On-link 10.10.3.6 286 > 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 > 192.168.1.0 255.255.255.0 On-link 192.168.1.69 286 > 192.168.1.69 255.255.255.255 On-link 192.168.1.69 286 > 192.168.1.255 255.255.255.255 On-link 192.168.1.69 286 > 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 10.10.3.6 286 > 224.0.0.0 240.0.0.0 On-link 192.168.1.69 286 > 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 10.10.3.6 286 > 255.255.255.255 255.255.255.255 On-link 192.168.1.69 286 > =========================================================================== > > OpenVPN had established 10.10.3.5 as the client gateway to the server. All that was missing was the 10.10.1.x routing. Now I manually added the following from a Windows Command prompt: > Route ADD 10.10.1.0 MASK 255.255.255.0 10.10.3.5 > > I did another route print: > =========================================================================== > Active Routes: > Network Destination Netmask Gateway Interface Metric > 0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.69 30 > 10.10.1.0 255.255.255.0 10.10.3.5 10.10.3.6 31 > 10.10.3.0 255.255.255.0 10.10.3.5 10.10.3.6 30 > 10.10.3.4 255.255.255.252 On-link 10.10.3.6 286 > 10.10.3.6 255.255.255.255 On-link 10.10.3.6 286 > 10.10.3.7 255.255.255.255 On-link 10.10.3.6 286 > 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 > 192.168.1.0 255.255.255.0 On-link 192.168.1.69 286 > 192.168.1.69 255.255.255.255 On-link 192.168.1.69 286 > 192.168.1.255 255.255.255.255 On-link 192.168.1.69 286 > 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 10.10.3.6 286 > 224.0.0.0 240.0.0.0 On-link 192.168.1.69 286 > 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 10.10.3.6 286 > 255.255.255.255 255.255.255.255 On-link 192.168.1.69 286 > =========================================================================== > > I am now able to "Ping" any address on the 10.10.1.x subnet. > Two issues remain: > 1) How do I get the OpenVPN client to add/delete the IP Route dynamically? > 2) Now that I am able to Ping, I would like to be able to telnet to specific 10.10.1.x addresses, but I am not able to do so. Any suggestions? > <snip> Jan's response is right on. The route should have been added. It sounds like something is preventing it on the Windows side. The same may be true of telnet as OVPN itself is not restricting protocols - it's more of an on/off switch. Good luck - John |