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 745747 - Allow the user to specify a connection is capped/metered
Allow the user to specify a connection is capped/metered
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Network
git master
Other Linux
: Normal enhancement
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 754056 (view as bug list)
Depends on: 741725 754409
Blocks:
 
 
Reported: 2015-03-06 14:34 UTC by Emmanuele Bassi (:ebassi)
Modified: 2018-03-22 21:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Emmanuele Bassi (:ebassi) 2015-03-06 14:34:04 UTC
Mobile broadband connections are not all detectable as mobile devices; in some case, they are just Ethernet or Wi-Fi connections going through a mobile-like device. It is up to the user to specify that a connection is actually capped/metered, in those cases, and avoid blowing through the monthly user quota, or start spending tons of money on roaming charges.

It would be good to have a setting inside NetworkManager, and exposed in the UI, to let the user specify that a certain connection is capped/metered; this would allow tools like GNOME Software, or the web browser, or anything that automatically connects to the network, to be aware of the limitations of a connection.

Additionally, having a way to specify an actual quota would allow client-side capping, as well as usage statistics. This would also be helpful for parental controls.
Comment 1 Matthias Clasen 2015-03-06 22:09:40 UTC
I've filed a NetworkManager bug a while ago, asking for a place to store this information. See bug 741725
Comment 2 Bastien Nocera 2015-04-07 08:42:09 UTC
Roaming charges are a completely different problem, one of cost, but roaming can be disabled with manual intervention.
Comment 3 Robert Buchholz 2015-04-17 09:17:52 UTC
Bastien, I agree roaming is a different issue and should be handled in the device setting up the mobile broadband connection (i.e., phone/UMTS router). But this issue is still a question of cost in two cases:
1. Capped transfer is used up. Then you need to purchase more data, or increase your plan.
2. You have no "flat rate" data plan and pay mobile data per kb.

In both cases, having accidental unnecessary background traffic costs actual money.
Comment 6 Bastien Nocera 2015-08-25 09:06:37 UTC
*** Bug 754056 has been marked as a duplicate of this bug. ***
Comment 7 Bastien Nocera 2015-09-01 15:52:13 UTC
(In reply to Allan Day from comment #5)
> Initial design guidance:
> 
> https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/
> system-settings/network/aday/png/background-data.png

This makes it look like whether to use background data is based on the device used when it should actually be based on the connection used, eg. connecting via Wi-Fi to my phone (metered) and to my home Wi-Fi (unmetered) should have different values.
Comment 8 Bastien Nocera 2015-09-01 15:53:15 UTC
Bug 754409 contains some notes on setting the metered values by hand.
Comment 9 Allan Day 2015-09-10 14:40:14 UTC
(In reply to Bastien Nocera from comment #7)
...
> > https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/
> > system-settings/network/aday/png/background-data.png
> 
> This makes it look like whether to use background data is based on the
> device used when it should actually be based on the connection used, eg.
> connecting via Wi-Fi to my phone (metered) and to my home Wi-Fi (unmetered)
> should have different values.

I remember that I investigated that, and decided I didn't want it. I suspect that the reasons were:

 1. People are unlikely to find the setting if they have to dig down too far in order to find the setting.

 2. Since it's a significant global setting that effects your whole system, it should look like a significant setting that affects your whole system.

One possibility would be add more information, so that it is clear that the setting is tied to a particular connection - we could show the connection name below the background data label, for example.

If the setting was placed within each network connection, issue 2 means that we'd have to show a prominent, transient element at the global level when background data is off.
Comment 10 Allan Day 2015-09-10 14:41:28 UTC
Oh, one other reason:

 3. It's quite similar to airplane mode (in that it's a system-wide network mode).
Comment 11 Jan-Michael Brummer 2017-01-06 21:34:21 UTC
This feature is still missing in latest g-c-c. Will this be part of the redesign?
Comment 12 Bastien Nocera 2017-01-10 14:12:44 UTC
(In reply to Jan-Michael Brummer from comment #11)
> This feature is still missing in latest g-c-c. Will this be part of the
> redesign?

When it happens, yes.
Comment 13 rockonthemoonfm 2017-04-04 12:09:48 UTC
I use a USB 4G modem daily and off course I need to know how much data I consume to not let my provider suck my credit dry all the time. :\
By the way the gnome-controle-center Mobile Broadband module works, but it is quite buggy regarding toggling on/off the modem or connection. Actually it doesn't separate modem and connection settings, the switch has a bit overlapping functions.
Comment 14 Jonathan Kang 2017-04-05 03:37:49 UTC
(In reply to rockonthemoonfm from comment #13)
> I use a USB 4G modem daily and off course I need to know how much data I
> consume to not let my provider suck my credit dry all the time. :\
> By the way the gnome-controle-center Mobile Broadband module works, but it
> is quite buggy regarding toggling on/off the modem or connection. Actually
> it doesn't separate modem and connection settings, the switch has a bit
> overlapping functions.

In terms of the switch button issue, there is already a bug filed about it,
see bug#690361.
Comment 15 rockonthemoonfm 2017-10-19 15:34:05 UTC
ping 

Needed feature for a Purism Librem smartphone too
Comment 16 Bastien Nocera 2017-10-19 15:36:54 UTC
(In reply to rockonthemoonfm from comment #15)
> ping 
> 
> Needed feature for a Purism Librem smartphone too

Stop "pinging" in bug reports, this isn't helping. Last warning.
Comment 17 mirh 2018-03-22 18:45:04 UTC
(In reply to Allan Day from comment #9)
> I remember that I investigated that, and decided I didn't want it. I suspect
> that the reasons were:
> 
>  1. People are unlikely to find the setting if they have to dig down too far
> in order to find the setting.
> 
>  2. Since it's a significant global setting that effects your whole system,
> it should look like a significant setting that affects your whole system.
> 
> One possibility would be add more information, so that it is clear that the
> setting is tied to a particular connection - we could show the connection
> name below the background data label, for example.
> 
> If the setting was placed within each network connection, issue 2 means that
> we'd have to show a prominent, transient element at the global level when
> background data is off.

And I don't personally see anything wrong with it. 
And really (maybe it's me to be strange?) nm-connection-editor seems the most natural place on earth, given indeed it's a per-connection pref. 
Then, if you *also* want it in other places, it's another matter. 

(In reply to rockonthemoonfm from comment #13)
> I use a USB 4G modem daily and off course I need to know how much data I
> consume to not let my provider suck my credit dry all the time. :\

That's bug 763048
Comment 18 Georges Basile Stavracas Neto 2018-03-22 21:05:25 UTC
Starting from GNOME Settings 3.28, a new checkbox in the connection settings dialog allows you to mark the connection as metered or not.

I consider then this bug as FIXED.

Please reopen if necessary.