|
|
James Yonan <jim <at> yonan.net> writes: > The failure to restart is probably because you are using --user and/or > --group so that the process no longer has sufficient privilege to open > the TUN/TAP device, though it doesn't explain where the SIGHUP came from. > > How difficult is this to reproduce? > > James Hi all, thx for your very helpful advices! Here is where I am so far after a half an hour internal test (not connecting from the internet) of the VPN connection: 1. Step: I disabled the group / user nobody features (on the server side) and and added the persist-tun persist-key features (on server and client side) --> Result: The connection kept restarting every minute or two but this time the connection didn't brake and the server didn't crash :) 2. Step: I additionally inserted the keepalive 10 60 option on both the server and the client --> Result: No more restarts :) --> I just don't know why the server kept crashing on me when I used this keepalive directive in beta11?? I guess now I can add the user / group nobody feature and disable the persist-tun persist-key feature since my connection isn't restarting all the time and I have a permanent IP address for the server so the client won't need to "follow" new IP address of a DNS name??? Still open to verify: long time testing. Thx to all that helped, Kurt Thx again for all your help ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |