Date: Fri, 19 Feb 2016 01:47:19 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 206876] ifconfig(8): Inconsistent behavior when creating and giving custom name to interface at the same time Message-ID: <bug-206876-2472-jioPLe4bof@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206876-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-206876-2472@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=3D206876 --- Comment #1 from Marie Helene Kvello-Aune <marieheleneka@gmail.com> --- I've made a patch to fix this problem. I'll submit it once I find a way of making ifconfig echo the name of the interface AFTER the 'name' command, instead of the name of the interface during 'create' command. Example: "ifconfig tap create name blah" would echo "tap0" but should echo "blah". I found the same bug appeared with the 'description' command as well (ifcon= fig tap create description "some description"). The bug is that setifdescr(...) and setifname(...) doesn't copy the 'global namespace' member 'name' onto the 'ifr.ifr_name' member before doing operations. This made me realize a workaround exist. If you manage to run a command which initializes 'ifr.ifr_name' properly before the 'name' or 'description' commands, these would work as expected. Example: 'ifconfig tap create mtu 9000 name mysupertap' I'll keep digging into the source to figure out how to echo the proper interface name now. --=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-206876-2472-jioPLe4bof>