Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Apr 2023 06:51:40 +0000
From:      bugzilla-noreply@freebsd.org
To:        net@FreeBSD.org
Subject:   [Bug 235920] ifconfig: unable to create another interface after renaming the previous one with the same name
Message-ID:  <bug-235920-7501-PALwWT38tb@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-235920-7501@https.bugs.freebsd.org/bugzilla/>
References:  <bug-235920-7501@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=3D235920

Franco Fichtner <franco@opnsense.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |franco@opnsense.org

--- Comment #6 from Franco Fichtner <franco@opnsense.org> ---
Speaking for pf/OPNsense scope the management of this limitation is a non-i=
ssue
since you have to manage manage the target device names as unique anyway so=
 you
never end up creating something with an intermediate name twice (or just om=
it
the index and it's fine you will even get the device name back).

And tun/tap is a little tricky in its own regard here since the device nodes
that may be required by the service are never being renamed (/dev/tunX etc.=
).

--=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-235920-7501-PALwWT38tb>