re [KLUG Members] OpenVPN & DHCP

[Adam Tauno Williams]

> > In a normally routed network yes.  But client-VPNs vs. site-to-site VPNs are
> > usually setup in a bridged fashion so that the client operates as if it were
> > local.  This is because most brain-dead client operating systems don't support
> > any kind of routing protocol (OSPF, etc...).
> 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 wrong.  But you need to introduce the route(s) to the remote
networks into the routing table of the client;  how you'd do this on
Windows seems a mystery to me (hence most client-VPNs run bridged or
proxy-arp'd).

If you have

CLIENT(a.b.c.d)----VPN----(a.b.c.e)HOST(f.g.h.i)<---LAN[f.g.h.[j...z])

The client (even Windows!) can intuit that a.b.c.[d...z] lies on that
VPN interface.  But it doesn't know that f.g.h.[i...z] lies via gateway
a.b.c.e unless someone or something tells it so.

Does OpenVPN 2.x offer you an option to run a script (aka batch file)
when the connection comes up and goes down.  If so you might be able to
invoke the windows route command with the proper values;  but I don't
know if you can do this as a non-Administrator. (?)