On Sat 13 Oct 2012 13:01:28 NZDT +1300, Steve Holdoway wrote: > Openvpn is started automagically at bootup. I'm still in the land > of /etc/init.d/ wherever possible myself. > > Routing tables are modified from the server config on startup of that > connection. > > look at the (eg) > server 10.12.14.0 255.255.255.0 > > and (eg) > push "route 192.168.10.0 255.255.255.0" > > config settings to enable access to remote subnets as well. Some > iptables forwarding on server may be necessary ( tun0 <-> eth0 or > similar ), and static routing on ultimate servers on remote subnets if > the OpenVPN server if it isn't the default route. > > ( or you can cheat and just masquerade all incoming connections over > tun0 ). > > For DNS resolution, a google on /usr/share/openvpn/update-resolv-conf > should provide you with all of the information necessary. > > (and not a clickety-click in sight (: ).
Are you talking about the vpn server or client here? I was talking about the client. Thanks for the tips, I'll have another look. However init.d isn't an option - sometimes I neither need nor want the vpn. Volker -- Volker Kuhlmann http://volker.dnsalias.net/ Please do not CC list postings to me. _______________________________________________ Linux-users mailing list Linux-users@lists.canterbury.ac.nz http://lists.canterbury.ac.nz/mailman/listinfo/linux-users