Public bug reported: OpenVPN unjustly blocks a source IP switch immediately after connection setup.
We're using a (different) VPN (main) with a default gateway; we connect to the target VPN (3.3.3.3) with source IP 2.2.2.2; once connected to targetVPN, targetVPN pushes its own IP 3.3.3.3 with net_gateway so we don't get VPN-in-VPN; this is detected as a floating IP by openvpn. With openvpn 2.5, this works flawlessly. But with openvpn 2.6, it's counted as a second connection, and we get "Disallow float to an address taken by another client 1.1.1.1:sourcePort". This lasts for 60 seconds until "client-instance restarting", after which the second connection is finally allowed. During these 60 seconds, all traffic to/through targetVPN is disallowed. ---- Upstream bug report: https://github.com/openvpn/openvpn/issues/704 Upstream patch: https://www.mail-archive.com/openvpn- de...@lists.sourceforge.net/msg31495.html Patch against 2.6.12 (for Noble) attached. ---- Walter Doekes OSSO B.V. ** Affects: openvpn (Ubuntu) Importance: Undecided Status: New ** Patch added: "floating_ip.patch" https://bugs.launchpad.net/bugs/2108860/+attachment/5873820/+files/floating_ip.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2108860 Title: floating IP due to "route VPN_IP net_gateway" causes 60 second "Disallow float" in openvpn 2.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/2108860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
