https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289303
--- Comment #10 from Kristof Provost <[email protected]> --- (In reply to Gert Doering from comment #2) > I'm not sure why you would see this by making the client reconnect - every > new connect should receive a new peer-id and thus not trigger a float event. That's what I'm confused by as well. It ought to be fine for userspace to not understand the float notification. Traffic should just keep flowing, although userspace will show the wrong peer IP. The kernel only sends a float notification for traffic that's been successfully decrypted, so this shouldn't happen on reconnect (assuming openvpn doesn't re-use keys for different connections, which seems like a pretty safe assumption). The only caveat there is that we don't check encryption if there isn't any, so I could maybe see this happening if openvpn is configured to not encrypt at all. Is that the case here? -- You are receiving this mail because: You are the assignee for the bug.
