What helps me with this issue is the section in the appendix in my
config files on server and client side.
For all options used, [1] is my reference.
With the settings, I can keep the connection alive with server's NAT
machine IP floating around in IP space for days without any problem.
It'll reconnect on ISP interrupt.
> That said, your suggestion is a good one and you now have me thinking about
> it.
Although it can be solved on the OpenVPN layer directly, I see that
this might be too complicated for unexperienced users in the
beginning.
Would it be possible to put the OpenVPN layer remedy, maybe
additionally, on http://code.google.com/p/tunnelblick/wiki/wConfigO?
The --ping option is IMO neither necessary nor sufficient to trigger a
restart. In fact, it only triggers ping packets.
To the developer: How are you planning to implement the restart
mechanism? (Maybe one could place the necessary OpenVPN options on
the command line starting OpenVPN?)
Friedrich
[1] http://www.openvpn.net/index.php/open-source/documentation/manuals/69-openvpn-21.html
Appendix:
On client side:
# Allow changes in remote IP address
float
# Retry to resolve the --remote infinitely
resolv-retry infinite
# Useful if dropping privileges (what might
# cause trouble if routing is desired)
persist-tun
persist-key
On server side I specify:
# 10 second interval pings and push a
# --ping-restart of 120 s (the 120 s timeout
# is the default, too). See also the --keepalive
# key in [1].
keepalive 10 120
Hi there,Was there any progress on implementing auto-reconnect. It'd be immensely useful.Thank you.
--To unsubscribe from this group and stop receiving emails from it, send an email to tunnelblick-dis...@googlegroups.com.
You received this message because you are subscribed to the Google Groups "tunnelblick-discuss" group.Visit this group at http://groups.google.com/group/tunnelblick-discuss?hl=en.For more options, visit https://groups.google.com/groups/opt_out.