Date: Thu, 20 Apr 2023 01:40:51 +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-e6fmkilC1y@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 --- Comment #7 from Zhenlei Huang <zlei@FreeBSD.org> --- (In reply to Franco Fichtner from comment #6) > And tun/tap is a little tricky in its own regard here since the device no= des that > may be required by the service are never being renamed (/dev/tunX etc.). Yes, you are right. For tap(4), even its unit number is freed the original controller device sh= ould still exist so that the applications (which have opened the /dev/tap) will = not be disturbed. I'm proposing UUID naming to fix that. Please see https://reviews.freebsd.org/D39689 . For the design of tap(4), why not create `/dev/tap/some-uuid-name` and an a= lias `/dev/tap0 -> /dev/tap/some-uuid-name` ? --=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-e6fmkilC1y>