> > wrote:
> > > so add
> > >
> > > # openvpn --mktun --dev tun
> > >
> > > to the client config?
> > No, you run that as root ahead of time to create a persistent tun
> > device.
> > You should see something like this:
> > [J:0-H:3888-L:3] # openvpn --mktun --dev tun
> > Sun Jan 17 21:18:07 2010 TUN/TAP device tun2 opened
> > Sun Jan 17 21:18:07 2010 Persist state set to: ON
> > And to remove:
> > [J:0-H:3889-L:3] # openvpn --rmtun --dev tun2
> > Sun Jan 17 21:18:34 2010 TUN/TAP device tun2 opened
> > Sun Jan 17 21:18:34 2010 Persist state set to: OFF
> > Once you have a persistent device, you can just tell the client
> > to use that specific device instead of creating a new tun device on
> > fly. It's sub-optimal because you have extraneous devices floating
> > around that you may not want/need when openvpn is not running.
> > -------
> > How are you invoking openvpn? Are you using some sort of init.d
> > with start-stop-daemon or the equivalent? Are you simply using
> > --config client.conf?
> > Ben
> > --
> > Ben Love
> > blove+signature (at) kylimar.com
|| ASCII ribbon campaign - ()
> > http://www.kylimar.com/
|| against HTML e-mail - /\