re [KLUG Members] OpenVPN & DHCP

[bill]

On Tue, 2005-06-21 at 14:45, Adam Tauno Williams wrote:

> > 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).

I think so too.

> > 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).

We're talking about doing something on the win machine (the client)
right?

I saw this on the FAQ

Can an OpenVPN server be set up on a machine with a single NIC?
Absolutely, as long as you make sure that:

      * The NAT gateway on the server's network has a port forward rule
        for TCP/UDP 1194 to the internal address of the OpenVPN server
        machine.
      * If you are using routing rather than ethernet bridging mode and
        would like connecting clients to see the whole LAN rather than
        only the server machine itself, you need to add an internal LAN
        route to the LAN gateway so that the private OpenVPN subnet
        (declared in the server, ifconfig, or ifconfig-pool directives)
        is routed to the OpenVPN server machine (i.e. its internal
        address).

But I can't figure out where the second bullet refers to, the client or
the server.

kind regards,

bill