|
|
Hi So here is my serverside config #start hand-window 2000 dev tun up .. dh .. ca .. cert .. key .. comp-lzo ping 3600 ping-restart 3800 reneg-sec 84600 tran-window 84600 ping-timer-rem verb 6 float #end Here is my client side config #start dev tun hand-window 200 remote .. up .. down .. tls-client ca .. cert .. key .. comp-lzo float ping 1100 ping-exit 3650 reneg-sec 84600 tran-window 84600 ping-timer-rem verb 3 proto tcp-client #end Greetings Roland -----Ursprüngliche Nachricht----- Von: openvpn-users-bounces@xxxxxxxxxxxxxxxxxxxxx [mailto:openvpn-users-bounces@xxxxxxxxxxxxxxxxxxxxx] Im Auftrag von Alexandros Papadopoulos Gesendet: Donnerstag, 5. April 2007 08:16 An: openvpn-users@xxxxxxxxxxxxxxxxxxxxx Betreff: Re: [Openvpn-users] problem with the tun/tap device On Thursday 05 April 2007 09:03, Roland Pontes wrote: <snip> > Tue Mar 20 18:59:24 2007 5476: Note: Cannot ioctl TUNSETIFF tun: File > exists (errno=17) Tue Mar 20 18:59:24 2007 5477: Note: Attempting > fallback to kernel 2.2 TUN/TAP interface > Tue Mar 20 18:59:24 2007 5478: Cannot allocate TUN/TAP dev dynamically > Tue Mar 20 18:59:24 2007 5479: Exiting > > The failure happens from time to time. when i start the process again > it works normally. Are you dropping privileges thus disallowing the tunnel to recreate the TUN device? Try using the --persist-tun option. For so many clients it would work a lot cleaner to have a 2.0-style VPN server (one daemon only) and connect all clients to that. It would also help to send us the configuration files of the tunnels that present the problem. HTH -A ______________________ OpenVPN mailing lists https://lists.sourceforge.net/lists/listinfo/openvpn-users ______________________ OpenVPN mailing lists https://lists.sourceforge.net/lists/listinfo/openvpn-users |