|
|
Thanks to both Dick and Scott (and of course James), I've finally got this working with a minimum amount of headache! For the record, here's how I do it: Tunnel Server is 192.168.230.204 Tunnel's LAN subnet is 192.168.230.0/24 Tunnel's server endpoint IP is 192.168.230.225/28 <-- * Tunnel's client endpoint IP is 192.168.230.238/28 <-- * * The use of a different subnet mask makes proxy ARP work automagically under the 2.4 kernel. Just make sure there are no physical machines on the subnet using this part of the address space! On the server, I enable ip_forward, as well as proxy_arp for both eth0 and the tunnel interface: # These two are done in rc.local: echo 1 > /proc/sys/net/ipv4/ip_forward echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp # This one is done in the tunnel's up script, using $1 # for the device: echo 1 > /proc/sys/net/ipv4/conf/tap0/proxy_arp On the client, after the connection is opened, I simply route add 192.168.230.0 mask 255.255.255.0 192.168.230.225 And I'm in! What a productive beginning to August. :) Thanks again, Michael P.S. James: FWIW, I'm working on a setup script and GUI front-end to make installation and control of OpenVPN easier for Windows end users. I'll be happy to share my results with you if you're interested. Thanks a million for OpenVPN! ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |