http://defect.opensolaris.org/bz/show_bug.cgi?id=13487
Summary: RFE: API call to get the overall connected state of
the network
Classification: Development
Product: nwam
Version: unspecified
Platform: ANY/Generic
OS/Version: OpenSolaris
Status: NEW
Keywords: ue
Severity: enhancement
Priority: P4
Component: ON daemon
AssignedTo: nwam-dev at opensolaris.org
ReportedBy: calum.benson at sun.com
QAContact: nwam-dev at opensolaris.org
--- Comment #0 from Calum Benson <calum.benson at sun.com> 2009-12-18 14:59:11
UTC ---
Filed after a brief discussion with Darren and Lin...
On Linux, NetworkManager, which performs many of the same functions as NWAM,
has the ability (via dbus) to inform other applications about changes in
network connectivity. Other desktop applications, such as web browsers, mail
clients, RSS readers and package managers, can (and do) use this information to
switch automatically between their online/offline modes, for example.
I think it would be desirable for NWAM to provide this information to other
applications, too.
Being of limited knowledge about how NetworkManager does this, and how NWAM
might do it, it's probably easier for me to quote Darren's email from here on
in :)
"As I understand it we would have to, at least now, add support for the
NM_STATE settings which consist of:
NM_STATE_UNKNOWN = 0
The NetworkManager daemon is in an unknown state.
NM_STATE_ASLEEP = 1
The NetworkManager daemon is asleep and all interfaces managed by it are
inactive.
NM_STATE_CONNECTING = 2
The NetworkManager daemon is connecting a device. FIXME: What does this mean
when one device is active and another is connecting?
NM_STATE_CONNECTED = 3
The NetworkManager daemon is connected.
NM_STATE_DISCONNECTED = 4
The NetworkManager daemon is disconnected.
This would as part of support for the NetworkManager DBus API (limited to this
only).
So a system-level daemon would be required - HAL is one option, but I believe
that it only runs it's backends when a new device is seen - so this really
doesn't fit with the state changes on the fly.
So we have a choice, do we simply implement the same D-Bus API as
NetworkManager as a daemon somewhere, or do we just use a different mechanism
altogether, and have NWAM provide a "connected/disconnected" overall state
which apps can use.
I think I would prefer if it was something that could be scripted (e.g. nwamadm
getstate), and also in the libnwam API - that way NWAM controls the decision
-and also then we would be free to do anything we want like adding a new daemon
or use the libnwam API to getting the information which we patch for."
--
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.
