Hi, On Thu, Jun 25, 2015 at 06:01:20PM +0200, Holger Kummert wrote: > When a linux tun interface is closed (e.g. on disconnect) > an optional ipv6 addr that was previously set is deleted now. > Without this patch a later reconnect would fail with > 'Linux ip -6 addr add failed: external program exited with error status: 2' > and openvpn would exit.
There is a trac ticket to that extent already (trac #141, http://community.openvpn.net/openvpn/ticket/141) - so thanks for the patch :-) I'm not sure I fully understand that usage scenario - which is one of the reasons why that ticket did not proceed. If you use normal nonpersistant tun interfaces, openvpn will destroy the tun interface at exit, removing the IPv6 address in the process. If you use *persistant* tun interfaces, this is usually done for a reason, like "bind (nameserver) cannot bind to new interface addresses because it is running without privileges" - but in this case, we should not remove the address (because then it's gone...) - and arguably not add it either, because it should already be there - because if not, the argument with "other software needs this address" is moot. So - help me understand the scenario. Why are you using persistant tun interfaces but want dynamically added and removed addresses? (I can see that OpenVPN misbehaves but I'm not sure I understand what "the best" solution should be - maybe go for "if that address is already there, do not touch it, otherwise, remove existing address and add new one" instead?) gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgptLQd3l8O8z.pgp
Description: PGP signature
