Actions
Bug #599
closedSIOCSLIFNAME Err#22 EINVAL
Status:
Resolved
Priority:
Low
Assignee:
-
Category:
kernel
Start date:
2011-01-03
Due date:
% Done:
0%
Estimated time:
Difficulty:
Tags:
Gerrit CR:
External Bug:
Description
It seems ifconfig (SIOCSLIFNAME) does not like VNIC names like 'il01', 'vnic02'
root@il01:~# uname -a SunOS il01 5.11 oi_148 i86pc i386 i86pc root@il01:~# dladm show-link LINK CLASS MTU STATE BRIDGE OVER il01 vnic 1500 up -- ? vnic0 vnic 1500 up -- ? il1 vnic 1500 up -- ? root@il01:~# ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1 inet6 ::1/128 root@il01:~# ifconfig vnic0 plumb root@il01:~# ifconfig il1 plumb root@il01:~# ifconfig il01 plumb ifconfig: cannot plumb il01: Invalid argument provided
truss says why:
ioctl(12, I_PUSH, "ip") = 0 ioctl(7, SIOCGLIFGROUPNAME, 0x08047050) Err#6 ENXIO ioctl(12, SIOCSLIFNAME, 0x080472E0) Err#22 EINVAL
The same on Illumos based system revision 13256 debug build:
# uname -srv SunOS 5.11 il_101214_01_r13256-d # dladm show-link LINK CLASS MTU STATE BRIDGE OVER nge0 phys 1500 up -- -- rtls1 phys 1500 unknown -- -- rtls2 phys 1500 unknown -- -- # dladm create-vnic -l nge0 vnic02 # ifconfig vnic02 plumb ifconfig: cannot plumb vnic02: Invalid argument provided # dladm create-vnic -l nge0 vnic2 # ifconfig vnic2 plumb # truss -t ioctl ifconfig vnic02 plumb ioctl(6, SIOCGLIFFLAGS, 0x08047320) Err#6 ENXIO ioctl(11, I_PUSH, "ip") = 0 ioctl(7, SIOCGLIFGROUPNAME, 0x080469A0) Err#6 ENXIO ioctl(11, SIOCSLIFNAME, 0x08046C30) Err#22 EINVAL ifconfig: cannot plumb vnic02: Invalid argument provided
Related issues
Updated by Yuri Pankov over 6 years ago
- Status changed from New to Resolved
dladm (via libdladm) was made to reject such names in #7667, closing this as "fixed".
Updated by Yuri Pankov over 6 years ago
- Related to Bug #7667: libdladm/dlmgmtd should do a better link name validation added
Actions