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.

> If you point the clients' WINS server at the one that's already on the 
> LAN, you should be OK as long as the tunnel is up.  I'm trying to have a 
> WINS server at each side that update each other, as well as a couple of 
> BINDs doing the same.  And ddns with dhcpd.  (so far, none of it works 
> reliably)

Constructing a distributed naming service is 'simple' if you backend it
with LDAP which understands replication and partitioning.  The DDNS
support in dhcpd is tough to make work reliably, we just propagate WINS
updates into LDAP via the WINS server (Samba).  The DNS server lays over
the top of LDAP (no more zonefiles,  zones are in the LDAP Dit).  This
has been wonderfully solid.