re [KLUG Members] OpenVPN & DHCP

[Adam Tauno Williams]

> > > >I already had a WINS server on the remote (server) LAN along with a
> > > >Samba Server.  So, I figured TUNneling (routing) would be o.k.  Am I
> > > >amiss here?
> > You're not amiss, but for this to work you have to introduce the route.
> > Run "route print" before you start the VPN, then run "route print" again
> > afterwards.  You will see a route to the adjacent network appear, but
> > not to the next hop.  If you introduce it manually then I'd wager you
> > will be able to connect.
> I'll try the route print command.
> There is a spot I'm using in server.conf to "push" the WINS route.

I think this SETS the clients WINS address via a Win32 call.  I don't
think it really refers to 'routing' at all,  just where the WINS server
is (IP).

> Is that what you mean by introducing it manually?  

Something like -
route add -net 192.168.0.0 netmask 255.255.255.0 gw 192.168.1.1
- at least that would be the format in LINUX.  The Windows route
command, as I recall, is much more annoying;  I'd have to lookup what
the syntax was.

This inserts into the routing table the knowledge that the
192.168.0.0/24 network is beyond the 192.168.1.1 host (gateway).

> Or do you mean introducing the route between the two server IPs? (that's
> where I'm stopped now, client can ping 192.168.1.1 [tunnel] but not
> 192.168.0.104 [server LAN]).