[mako/flipped] rmnet_usb devices are visible to NM, which tries to configure them
Bug #1194547 reported by
Tony Espy
This bug report is a duplicate of:
Bug #1193161: [mako/flipped] 3g Data Connections Fail.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
touch-preview-images |
In Progress
|
High
|
Mathieu Trudel-Lapierre |
Bug Description
On the non-flipped image, running the command 'nmcli dev' shows two devices:
/ril_0 gsm disconnected
wlan0 802-11-wireless disconnected
Whereas on the flipped image, an additional four ethernet devices are shown:
rmnet_usb3 802-3-ethernet unavailable
rmnet_usb0 802-3-ethernet unavailable
rmnet_usb2 802-3-ethernet unavailable
rmnet_usb1 802-3-ethernet unavailable
This related to LP: #1193161, which *may* now be resolved.
NetworkManager actually tries to configure these devices, which is incorrect as they're owned by RILD.
So, we need to figure out some way to prevent NM from doing anything with these devices until ofono gives the OK.
Changed in touch-preview-images: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Mathieu Trudel-Lapierre (mathieu-tl) |
summary: |
- [mako/flipped] 3G Devices are visible to NM, which tries to configure - them + [mako/flipped] rmnet_usb devices are visible to NM, which tries to + configure them |
Changed in touch-preview-images: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
This would go substancially better with debug logs, but since we pretty much know what's going on...
The issue is that when non-flipped (Ubuntu in a container), NM is unable to figure out the driver and just ignores the interface altogether.
In flipped, it sees the device and correctly identifies the driver, which causes the device to be managed. Then carrier detection appears to cause automatic connections to get started.
Two options: make the device ignored altogether and carry on as before, or perhaps a bit nicer (because then you can ask NM about connection states and stuff), have it not do carrier detection.
I'll test the latter, and go with the former if testing fails.