http://defect.opensolaris.org/bz/show_bug.cgi?id=12883
Summary: need a way to tell NWAM to give up on initially
plugged-in, but unplugged after address assignment
wired devices using drivers that do not support
DL_NOTE_LINK_UP/DOWN
Classification: Development
Product: nwam
Version: RC6
Platform: ANY/Generic
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: ON daemon
AssignedTo: nwam-dev at opensolaris.org
ReportedBy: alan.maguire at sun.com
QAContact: nwam-dev at opensolaris.org
CC: carlsonj at workingcode.com
--- Comment #0 from amaguire <alan.maguire at sun.com> 2009-11-25 14:51:07 UTC
---
We have a problem with wired drivers that do not support DL_NOTE_LINK_UP/DOWN.
If a device using such a driver has a cable plugged in but later removed (after
the address has already been assigned), NWAM has no way to detect the change
and switch over to wireless.
To solve this, we could use refresh of the NCU as a way to tell NWAM to attempt
to reacquire DHCP lease for drivers - a refresh request will do the job, since
a refresh will do a DHCP release, unplumb and replumb and kick off DHCP again,
and when this times out, we fall back to wireless. However this whole cycle
requires user intervention and is time-consuming. This would involve exposing
refresh actions to libnwam consumers as an nwam_ncu_refresh() function and
adding a button to the GUI to do this.
A better approach might be to periodically monitor the "ipackets" kstat value -
if it does not increase in a long period, we give up on the interface. That
would have the virtue of being automatic at least, and would work for static IP
scenarios too. Needs further investigation as we don't want false-positive
diagnosis of unplugging leading to unconfiguring of interfaces.
--
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.
