Date: Wed, 26 Apr 2017 18:13:38 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 218895] ifconfig name with same group name will crash the system Message-ID: <bug-218895-8-36k23clgd5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-218895-8@https.bugs.freebsd.org/bugzilla/> References: <bug-218895-8@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=3D218895 Kristof Provost <kp@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kp@freebsd.org --- Comment #1 from Kristof Provost <kp@freebsd.org> --- I can't reproduce this on current. Do you happen to have pf loaded? I'm aware that pf doesn't handle this. The basic problem is that pf assumes that interfaces and groups live in the same namespace. That's not the case, and this mistaken assumption causes pf to p= anic the system. It's a nontrivial fix, because the best way (in my view at least) to fix th= is is to actually make groups and interfaces share a namespace. It's downright silly to have a group foo and an interface foo at the same time, especially because there's no obligation for interface foo to be a member of group foo. I suspect this became a problem when the ability to change interface names = was introduced. It used to be the case that interfaces were always foo0 or bar1= . In fact, groups still refuse to be named baz3 ("ifconfig: setifgroup: group na= mes may not end in a digit"). --=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-218895-8-36k23clgd5>