Date: Sat, 03 Jun 2017 06:17:51 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 219746] Renaming (ifconfig(8)) tap(4) misses its character special device name Message-ID: <bug-219746-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219746 Bug ID: 219746 Summary: Renaming (ifconfig(8)) tap(4) misses its character special device name Product: Base System Version: 11.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: bugzilla.freebsd@omnilan.de Not sure if it's kern/ or bin/, both are involved I guess. Renaming vmnet/tap(4) interfaces, defined in rc.conf(5) via "cloned_interfaces" e.g, isn't prohibited by rc(8)-network.subr nor by ifconfig(8). If such a interface is renamed, the Ethernet device shows up correctly, with the new name and ifconfig(8) also reports the new name if it's created and renamed in the same invocation. Problem is, the control device isn't renamed, it will keep it's initial creation name like tap0 and I found no userland way to determine the corresponding Ethernet IF name. -harry --=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-219746-8>