|
|
Darren (and others), With your help, I was able to isolate the issue OpenVPN was not sending traffic back to the client. The doctor's network file share (10.0.0.1) and the veterinary application (10.0.0.2) needed to be told that the OpenVPN traffic (10.8.x.x) can be found via 10.0.0.40 (the internal IP for the OpenVPN server). So, I added: route add -net 10.8.0.0 netmask 255.255.255.0 gw 10.0.0.40 I realize my novice understanding of networking preventing me from seeing this sooner, but I appreciate the help in figuring out what OpenVPN was looking for. Steve On Thu, 2007-01-04 at 16:16 -0700, Darren Spruell wrote: > On 1/4/07, Steve Poe <steve.poe@xxxxxxxxx> wrote: > > So, I need to add 10.0.0.40 as a routing destination to the servers I am > > trying to access via OpenVPN? Then, if it can find 10.0.0.40, then it will > > find 10.8.x.x ? > > That's the idea. You can test this with some traceroutes and packet > captures at various points along the path once you get it in. > ______________________ OpenVPN mailing lists https://lists.sourceforge.net/lists/listinfo/openvpn-users |