https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289303
--- Comment #15 from Gert Doering <[email protected]> --- OK, so for the record, I can reproduce this with 14.3 + kernel float patch and 2.6.14. Connect to UDP server, then unplug LAN on the laptop (-> float to wifi), with --verb 7 2025-09-05 19:25:40 us=263268 Unknown kernel notification 2 2025-09-05 19:25:40 us=263273 cron2-freebsd-tc-amd64/193.149.48.172:52181 peer-id=0 SIGTERM[soft,ovpn-dco: ping expired] received, client-instance exiting 2025-09-05 19:25:40 us=263276 MULTI: multi_close_instance called 2025-09-05 19:25:40 us=263296 dco_update_peer_stat: invalid peer ID 0 returned by kernel 2025-09-05 19:25:40 us=263305 PID packet_id_free reconnect (new connection!) 2025-09-05 19:26:00 us=154492 Reset packet from client, sending HMAC based reset challenge 2025-09-05 19:26:00 us=154502 GET INST BY REAL: 193.149.48.172:56519 [failed] ... 2025-09-05 19:26:00 us=173624 193.149.48.172:56519 [cron2-freebsd-tc-amd64] Peer Connection Initiated with [AF_INET6]::ffff:193.149.48.172:56519 2025-09-05 19:26:00 us=173646 cron2-freebsd-tc-amd64/193.149.48.172:56519 peer-id=0 MULTI_sva: pool returned IPv4=10.114.3.3, IPv6=(Not enabled) 2025-09-05 19:26:00 us=173682 cron2-freebsd-tc-amd64/193.149.48.172:56519 peer-id=0 MULTI: Learn: 10.114.3.3 -> cron2-freebsd-tc-amd64/193.149.48.172:56519 peer-id=0 2025-09-05 19:26:00 us=173694 cron2-freebsd-tc-amd64/193.149.48.172:56519 peer-id=0 MULTI: primary virtual IP for cron2-freebsd-tc-amd64/193.149.48.172:56519 peer-id=0: 10.114.3.3 2025-09-05 19:26:00 us=173704 cron2-freebsd-tc-amd64/193.149.48.172:56519 peer-id=0 dco_new_peer: peer-id 0, fd 8 2025-09-05 19:26:00 us=173803 cron2-freebsd-tc-amd64/193.149.48.172:56519 peer-id=0 Failed to create new peer: File exists (errno=17) 2025-09-05 19:26:00 us=173821 cron2-freebsd-tc-amd64/193.149.48.172:56519 peer-id=0 Exiting due to fatal error 2025-09-05 19:26:00 us=173833 cron2-freebsd-tc-amd64/193.149.48.172:56519 peer-id=0 Closing DCO interface 2025-09-05 19:26:00 us=173842 cron2-freebsd-tc-amd64/193.149.48.172:56519 peer-id=0 /sbin/ifconfig tun0 10.114.3.1 -alias 2025-09-05 19:26:00 us=175522 cron2-freebsd-tc-amd64/193.149.48.172:56519 peer-id=0 /sbin/ifconfig tun0 destroy ... and on installation of "peer-id 0" to kernel, kernel says "File exists". So the part about "killing the client instance" does not seem to propage to the kernel -> kernel still has a "peer-id 0", and when OpenVPN tries to instantiate a new one, kernel refuses. This is something we need to sort out. Maybe userland just fails to send the "del peer" message - it looks like it, or not. dco_freebsd.c is less verbose than dco_linux.c... -- You are receiving this mail because: You are the assignee for the bug.
