|
From: Jan J. K. <ja...@ni...> - 2008-02-12 13:37:33
|
Paul Waring wrote: > On Tue, Feb 12, 2008 at 02:24:23PM +0100, Jan Just Keijser wrote: > >> it is very well possible to "make external clients appear to be part of >> a local network": using a bridging setup and you can use an external >> DHCP server to assign addresses to your openvpn clients. >> It does not matter if the assigned addreses are local/private addresses >> or public ones. >> > > Err, I'm not entirely sure what you mean by that - how would a remote > client (say based in the US) get assigned a public IP address for the > lab network? > > when the openvpn client connects to a "brdiged" server it will request an IP address from the DHCP server in the lab; the client's openvpn interface (tun0, tun1, the appropriate TAP-Win32 device , etc) will be assigned a public address from the pool of IP addresses from the DHCP server. All traffic for the subnet of this public IP address will be sent through the tunnel. You can add your own network routes if you need access to other subnets as well. It is not a problem if the "normal" interface of the client also has a public IP address: the system will know which stuff to route through which interface using its routing tables. HTH, JJK |