On 03/09/14 10:56, Mathias Jeschke wrote: > If you use the "hammer", the machine is not able to send a TCP FIN, I don't think that's the case. "Hammering" a user process does not influence how the TCP stack operates (kernel space vs user space) - it would generate a TCP reset.
Of course, unplugging the Ethernet cable would do what you're saying. No matter what way you look at it, you need to rely on "ping-restart" to pick up the corner-cases :-) I'm just dealing with another corner case. Clients who disconnect and reconnect before the server realises the first disconnect happened. So even "--client-connect" "--client-disconnect" cannot save you from seeing things out of order, eg 1. client connects, server triggers --client-connect 2. client disconnects harshly (not triggering --explicit-exit-notify) 3. client connects, server triggers --client-connect 4. server realizes client has disconnected I had some "cleanup" code in "4" which meant the server turned around and killed the "3" instead of the "1" - not what I wanted ;-). Still - all fixable thanks to the wondrous scripting options openvpn gives us :-) -- Cheers Jason Haar Corporate Information Security Manager, Trimble Navigation Ltd. Phone: +1 408 481 8171 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
