|
|
Brian Ericson <bericson@xxxxxxx> said: > Does the "--ping" option work in 1.5_beta14 using the TCP protocol (or > is it "just me")? > > I'm using 1.5_beta14 with the TCP protocol because my company's firewall > drops all UDP packets. I have no problems establishing a connection > between my work and home machines, however my company's firewall will > eventually timeout the connection. When this happens, my work box > (acting as the tcp-client) is unaware that the connection has dropped > and, therefore, doesn't attempt to re-establish a connection -- there's > nothing I can do save go back to work to re-start the connection. > > The solution is trivial -- send data through the tunnel at intervals > lower than the timeout, which is just what the --ping option is for. > However, for whatever reason, this option doesn't do anything: if I do > a --ping 10 and --ping-restart 60, the logs show "Inactivity timeout > (--ping-restart), restarting" every 60 seconds. I don't really want use > --ping-restart as a poor-man's --ping because it literally restarts the > connection (maybe that's not a big deal, especially with --persist-tun?)... > > Anyone else seen this? I just tried --ping over tcp (beta14) and it seems to work fine. At --verb 6 I get lots of Thu Nov 20 10:29:40 2003 157[0]: TCPv4_SERVER READ [16] from 10.0.0.10:32881: DATA len=16 Thu Nov 20 10:29:40 2003 158[0]: TCPv4_SERVER WRITE [16] to 10.0.0.10:32881: DATA len=16 Thu Nov 20 10:29:41 2003 159[0]: TCPv4_SERVER WRITE [16] to 10.0.0.10:32881: DATA len=16 Thu Nov 20 10:29:41 2003 160[0]: TCPv4_SERVER READ [16] from 10.0.0.10:32881: DATA len=16 Make sure to use --ping on both sides of the connection, as OpenVPN pings are not echoed. James ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |