Date: Tue, 23 Dec 2025 17:56:54 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 291901] routed(8) looks to be confused when an interface is renamed Message-ID: <bug-291901-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291901 Bug ID: 291901 Summary: routed(8) looks to be confused when an interface is renamed Product: Base System Version: 14.3-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: bsdpr@phoe.frmug.org On 14.2-RELEASE (also probably present in subsequent revisions), routed(8) running in quiet mode (-q) issues an unjustified error message when an interface is renamed: Dec 23 18:15:49 hox routed[1127]: wan0 (192.168.4.253/24) is duplicated by ue1 (192.168.4.253/24) wan0 and ue1 are the same interface: this message is issued after the USB interface is plugged-in and the following actions are performed by a script run by devd: Dec 23 18:10:48 hox netifsetup[23995]: warning: executing 'ifconfig ue1 inet alias 192.168.4.253/24' Dec 23 18:10:49 hox netifsetup[24085]: warning: executing 'ifconfig bridge0 addm ue1 -stp ue1' Dec 23 18:10:49 hox netifsetup[24098]: warning: executing 'ifconfig ue1 name wan0' I suspect that routed receive, in sequence, RTM_ADD(wan0) and RTM_DELETE(ue1) messages through its routing socket. It probably emit the error immediately after RTM_ADD. It should instead wait a (very) little while until it receives RTM_DELETE, at which point no message is required. If and only if after the (very) little while duration RTM_DELETE still wasn't received, then issue the error message which would then signal a genuine error. Alternatively, the kernel could inverse the messages sequence order (delete before add) which would make more sense IMHO. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-291901-227>