Date: Thu, 14 Dec 2023 16:02:04 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 275765] Automatically add carp(4) interfaces to interface group "carp" Message-ID: <bug-275765-227-yNjRdWFx5T@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275765-227@https.bugs.freebsd.org/bugzilla/> References: <bug-275765-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275765 Kristof Provost <kp@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kp@freebsd.org --- Comment #1 from Kristof Provost <kp@freebsd.org> --- vlan and bridge interfaces are automagically added to their respective grou= ps because they're cloned interfaces. (See ifc_link_ifp() in sys/net/if_clone.= c). There's no such thing as a carp interface. There are carp addresses on other interfaces, but it'd be surprising for a new address to cause an interface = to be added to an interface group. It may be possible to emulate this in userspace using the CARP notification= s in devd.=20 I'm not convinced that it'd be a good idea to try to do this from the kerne= l, but for those who want to try, ifc_link_ifp() and carp_alloc()/carp_destroy= () are the places to start looking, --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275765-227-yNjRdWFx5T>