NetworkManager uses ofono GPRS contexts for wrong SIM

Bug #1431471 reported by Tony Espy on 2015-03-12
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Undecided
Unassigned
network-manager (Ubuntu)
High
Mathieu Trudel-Lapierre

Bug Description

NetworkManager incorrectly uses GPRS contexts from any SIM directory instead of limiting the GPRS contexts used to those the currently active SIM.

This bug was discovered on krillin while trying to determine whether bug #1425987 was a duplicate of bug #1418077.

I've attached the NetworkManager log messages extracted from the syslog contained in the network-test-session tarball attached to bug #1425987.

If you look at the attached netlog, after '/208150102671184/context1' is disabled, you'll see NM try a 'context3', 'context5', and 'context1' again. The odd thing is that the related IMSI is not '208150102671184' it's '208103698221268'. Looking at network-test-session.log ( also attached ), you'll see that '208150102671184' is the IMSI for ril_0, and that ril_1 is PIN-locked.

This bug was discovered on krillin running vivid-proposed #122.

The version of NetworkManager on this image is: 0.9.10.0-4ubuntu6

Tony Espy (awe) on 2015-03-12
Changed in network-manager (Ubuntu):
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
Changed in network-manager (Ubuntu):
status: Confirmed → In Progress
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package network-manager - 0.9.10.0-4ubuntu13

---------------
network-manager (0.9.10.0-4ubuntu13) vivid; urgency=medium

  * d/p/0001-wwan-add-support-for-using-oFono-as-a-modem-manager.patch:
    Check that a connection matches the current modem IMSI when deciding
    whether it should be deemed "compatible" to use to connect to a data
    network. (LP: #1431471)
  * d/p/0002-wifi-cull-the-scan-list-before-signalling-ScanDone-b.patch:
    Update the last seen timestamp in cull_scan_list() using the new
    nm_ap_update_last_seen() function rather than setting it to time(NULL),
    otherwise the timestamp will appear too far in the future and break the
    removals on last_seen value comparison. (LP: #1427205)
 -- Mathieu Trudel-Lapierre <email address hidden> Tue, 31 Mar 2015 23:00:31 -0400

Changed in network-manager (Ubuntu):
status: In Progress → Fix Released
Changed in canonical-devices-system-image:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers