| Ben Love on 17 Jan 2010 18:25:03 -0800 |
|
> 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 config to use that specific device instead of creating a new tun device on the 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 script with start-stop-daemon or the equivalent? Are you simply using openvpn --config client.conf? Ben -- Ben Love blove+signature (at) kylimar.com || ASCII ribbon campaign - () http://www.kylimar.com/ || against HTML e-mail - /\ Attachment:
signature.asc ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|