http://defect.opensolaris.org/bz/show_bug.cgi?id=8475
Summary: Automatic brought up wired and wireless - sort of
Classification: Development
Product: nwam
Version: unspecified
Platform: ANY/Generic
OS/Version: All
Status: NEW
Status Whiteboard: nwam1-build:2009-04-23
Severity: normal
Priority: P3
Component: ON daemon
AssignedTo: nwam-dev at opensolaris.org
ReportedBy: dkenny at opensolaris.org
QAContact: nwam-dev at opensolaris.org
I just noticed that my machine "appears" to have two network interfaces up when
using the Automatic NCP:
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
inet 127.0.0.1 netmask ff000000
myk0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2
inet 129.156.226.199 netmask ffffff00 broadcast 129.156.226.255
ath0: flags=1004803<UP,BROADCAST,MULTICAST,DHCP,IPv4> mtu 1500 index 3
inet 192.168.1.7 netmask ffffff00 broadcast 192.168.1.255
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
inet6 ::1/128
myk0: flags=2000840<RUNNING,MULTICAST,IPv6> mtu 1500 index 2
inet6 fe80::21e:c2ff:fe19:2f37/10
ath0: flags=2000800<MULTICAST,IPv6> mtu 1500 index 3
inet6 fe80::217:f2ff:fefc:ebe0/10
What's specifically strange about this is that I have a cable connected to
myk0, and ath0 isn't connected to a wireless AP at all:
# dladm show-wifi
LINK STATUS ESSID SEC STRENGTH MODE SPEED
ath0 disconnected -- -- -- -- --
The address assigned to ath0 is what it would have had when I was at home
yesterday - so it looks like DHCP has picked this up and assigned it.
I would have expected that if the wired i/f was up. then the wireless would be
marked down and not have DHCP running on it.Since the wired i/f is at
priority-group 0 while the wireless is at priority-group 1.
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
