Bug 1012309 - Specific object property in Active connection is not updated
Specific object property in Active connection is not updated
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-09-26 05:06 EDT by Jan Grulich
Modified: 2013-10-01 12:13 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-09-26 13:13:28 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Grulich 2013-09-26 05:06:44 EDT
Description of problem:
When I'm connected to a wireless network which is provided by more APs, then specific object property in active connection is set to the one which was used during activation, but when this AP disappears and I'm connected to another one, this property is not updated and points to AP which doesn't exist. I checked it on dbus, where my active connection points to AP number 16, but wireless device points to active AP number 17 so specific object property in my active connection should be updated to AP number 17.

Version-Release number of selected component (if applicable):
[root@fedora jgrulich]# rpm -q NetworkManager

Actual results:
Specific object property points to previous AP.

Expected results:
Specific object property is updated and points to actually used AP.
Comment 1 Dan Williams 2013-09-26 13:13:28 EDT
While the documentation is somewhat unclear here, the specific object is always the one passed to NetworkManager when the connection was activated, via the ActivateConnection or AddAndActivateConnection dbus methods, and does not change over the lifetime of the connection unless it originally was "/", in which case it is updated to the access point actually used to connect with during activation.

You probably want the "org.freedesktop.NetworkManager.Device.Wireless" interface's "ActiveAccessPoint" property, which will be changed to match the currently associated access point whenever the device roams.


API documentation clarified upstream in commit a045c296385ca4937d34c47dcb308e00b8bed983.
Comment 2 Fedora Update System 2013-10-01 12:13:07 EDT
NetworkManager- has been submitted as an update for Fedora 20.

Note You need to log in before you can comment on or make changes to this bug.