On 2006/12/28 11:04, Pontus Stenetorp wrote: > and bridgename.bridge0 to > add 'int_iface' > add 'tun_iface' > up
Do you mean that you literally have 'int_iface' and 'tun_iface' in the file? Or do you have something like: /etc$ grep . hostname.tun0 bridgename.bridge0 hostname.tun0:link0 up bridgename.bridge0:add vlan42 bridgename.bridge0:add tun0 bridgename.bridge0:up > I did a reboot in order to activate the bridge, this was stated at the > networking howto at openbsd.org. I haven't been able to launch OpenVPN > on boot however. This shouldn't be the issue, right? Add it to rc.local: something like /usr/local/sbin/openvpn --config /etc/openvpn/server.ovpn > Now I don't know how to proceed. How should I manage to force all > internet traffic oven the tunnel You can't route *all* internet traffic over the tunnel; how else would you reach the OpenVPN endpoint? You should be able to do what you're after by adding static routes for the VPN endpoint and for anything you need to locate that (e.g. DNS servers if you need them) over your normal internet connection, and then changing the default route to the IP address of a router on the remote network. > and do you agree with the OpenVPN Server supplier that using tun > screws this up(in my opinion tun should work just as well when used > properly)? tun-in-ethernet-emulating-mode (i.e. with link0 so it behaves like a tap on other OS) should work fine.
