After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 730918 - Sync with NM to decide whether a WWAN port is really modem-controlled
Sync with NM to decide whether a WWAN port is really modem-controlled
Status: RESOLVED NOTGNOME
Product: NetworkManager
Classification: Platform
Component: ModemManager
git master
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-05-29 08:06 UTC by Aleksander Morgado
Modified: 2014-10-15 09:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Aleksander Morgado 2014-05-29 08:06:05 UTC 
There are devices out there (e.g. Huawei E355) which expose a WWAN port, flagged as WWAN by the kernel, but which doesn't require any further setup via any control protocol.

MM could have a new 'probing' property to let users know that a device is being probed, and if the probing ends without MM creating a modem for a given WWAN port, NM could take over the control of the port and try IP setup on it directly as if it were an Ethernet interface.

More context in the mailing list:
http://lists.freedesktop.org/archives/modemmanager-devel/2014-April/001062.html
Comment 1 Aleksander Morgado 2014-10-15 09:26:28 UTC 
Moving bugreport to the new ModemManager bugzilla in fd.o; summarized the issue
there as well. Please subscribe to the new bugreport to get new updates.

https://bugs.freedesktop.org/show_bug.cgi?id=85041

Closing this report as NOTGNOME.