[Bug 218895] ifconfig name with same group name will crash the system

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218895

Kristof Provost <kp at freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kp at freebsd.org

--- Comment #1 from Kristof Provost <kp at 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 panic
the system.

It's a nontrivial fix, because the best way (in my view at least) to fix this
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 names
may not end in a digit").

-- 
You are receiving this mail because:
You are the assignee for the bug.