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 748032 - NetworkManager should allow marking wireless connection as mobile
NetworkManager should allow marking wireless connection as mobile
Status: RESOLVED DUPLICATE of bug 741725
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
http://comments.gmane.org/gmane.linux...
Depends on:
Blocks:
 
 
Reported: 2015-04-17 08:42 UTC by Robert Buchholz
Modified: 2015-04-17 08:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Robert Buchholz 2015-04-17 08:42:15 UTC 
Quoting myself from 1 year ago:

I regularly use mobile a hotspot provided by an Android phone or a Router with a  SIM card. In my country, data transfer through mobile networks (UMTS, LTE) is expensive and highly limited.
Some applications (notably PackageKit) already support disabling background data transfer when on mobile networks, but this is useless when NetworkManager reports a low-cost network.
I understand it is unreasonable to determine low-cost/high-cost automatically, so I propose a setting in the wireless connection settings to mark a wireless connection as mobile.

Currently, whenever I forget to disable PackageKit, it downloads 70 MB of data at least once a day (just the file lists!), which is a significant portion of my plan.

There have been numerous questions on fedora-users regarding this issue (disabling packagekit due to a mobile hotspot), but I found no open bug report.

----

I just had PackageKit/dnf download 270 MB of file lists over my tethered mobile connection, reducing my transfer speeds to the year 1992.
Comment 1 Thomas Haller 2015-04-17 08:52:11 UTC 
Thank you for the bug report.

It is actually a duplicate. Closing therefore.
Please feel invited to continue the discussion over there.

(I agree that this is a useful feature).

*** This bug has been marked as a duplicate of bug 741725 ***