[Bug 206876] ifconfig(8): Inconsistent behavior when creating and giving custom name to interface at the same time
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Feb 3 07:53:58 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206876
Bug ID: 206876
Summary: ifconfig(8): Inconsistent behavior when creating and
giving custom name to interface at the same time
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: bin
Assignee: freebsd-bugs at FreeBSD.org
Reporter: marieheleneka at gmail.com
# uname -a
FreeBSD venus 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r295136: Tue Feb 2 09:27:29
CET 2016 root at venus:/usr/obj/usr/src/sys/GENERIC amd64
How to reproduce:
# ifconfig tap create name teststuff
tap0
ifconfig: ioctl SIOCSIFNAME (set name): Device not configured
Expected behaviour:
1: ifconfig(8) should know the name of the newly created interface (tap0) and
change its name according to the 'name' parameter (teststuff).
2: It should echo the name provided in 'name' parameter (example: teststuff),
unless it failed to change the name, in which case it should echo the
automatically numbered name. (example: tap0)
It currently does expected behavior 2, but not expected behavior 1.
Workaround: (thanks to thoht on Freenode. Below syntax is for /bin/sh)
# ifconfig $( ifconfig tap create ) name teststuff
It works as expected when using the syntax:
# ifconfig tap0 create name teststuff
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list