Cathy Zhou wrote:
> The rename-link operation should be the same regardless of the media type of 
> the link.
> 
> I did the same test on my laptop before and didn't see this problem. Is this 
> reproducible? 
> I will try to reproduce this problem on my laptop when I get back home.
> 
> - Cathy

Just FYI - since I don't have laptop with me right now. I only tested "dladm 
rename-link 
bge0 net0" after I force the bge driver to be unloaded.

rename-link works fine in that case.

- Cathy

> 
>> In the spirit of real-world testing and as suggested during last week's 
>> meeting, I bfu'ed my laptop to the latest UV archives and attempted to 
>> rename my WiFi link.  A strange thing happened:
>>
>> seb# svcadm disable nwam
>> seb# ifconfig ath0 unplumb
>> seb# ifconfig bge0 unplumb
>> seb# dladm rename-link ath0 wlan0
>> dladm: rename operation failed: object not found
>> seb# dladm rename-link ath0 wlan0
>> seb(/)# dladm show-link
>> LINK        CLASS      MTU  STATE    OVER
>> wlan0       phys      1500  down     --
>> eth0        phys      1500  down     --
>> seb(/)# dladm show-phys
>> LINK        MEDIA               STATE      SPEED  DUPLEX   DEVICE
>> wlan0       WiFi                down         0Mb  unknown  ath0
>> eth0        Ethernet            down         0Mb  unknown  bge0
>>
>> As you see, the first rename-link operation failed, but the second (typed 
>> immediately following the failed attempt) succeeded.  I had no such 
>> problem renaming my bge0 link to eth0.  Is this perhaps because the ath0 
>> driver unloads in the middle of the operation?
>>
>> The good news is:
>>
>> seb(/)# svcadm enable nwam
>> seb(/)# dladm show-link
>> LINK        CLASS      MTU  STATE    OVER
>> wlan0       phys      1500  up       --
>> eth0        phys      1500  down     --
>> seb(/)# ifconfig -a
>> lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 
>> 8232 index 1
>>          inet 127.0.0.1 netmask ff000000
>> wlan0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 
>> 1500 index 13
>>          inet 10.0.245.248 netmask ffff0000 broadcast 10.0.255.255
>>          ether 0:b:6b:4e:8f:87
>> eth0: flags=201000803<UP,BROADCAST,MULTICAST,IPv4,CoS> mtu 1500 index 14
>>          inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255
>>          ether 0:c0:9f:87:c3:3e
>> lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 
>> 8252 index 1
>>          inet6 ::1/128
>>
>> ... It just works with NWAM.
>>
>> -Seb
>>
>>
>> _________________________________
>> clearview-discuss mailing list
>> clearview-discuss at opensolaris.org
> 
> 
> _________________________________
> clearview-discuss mailing list
> clearview-discuss at opensolaris.org


Reply via email to