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 658018 - No option to change MTU for mobile broadband in NetworkManager
No option to change MTU for mobile broadband in NetworkManager
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: nm-applet
unspecified
Other Linux
: Normal major
: ---
Assigned To: Dan Williams
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2011-09-01 22:28 UTC by James Haigh
Modified: 2020-11-12 14:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description James Haigh 2011-09-01 22:28:27 UTC
Originally reported at:
  https://bugs.launchpad.net/bugs/801313

Mobile broadband connections seem to work best when the MTU is 1430:
http://ubuntuforums.org/showthread.php?t=1630684

Currently there is no native way of setting this in NM and I have to change it by this command every time I connect:
sudo ifconfig ppp0 mtu 1430

MTU can be set for wired and wireless, why not mobile?

I suggest that the MTU value should be set on the 'Mobile Broadband' tab of a connection under the 'Advanced' section. It should also be 1430 by default (or some other common recommended value for mobile broadband).

I'm running Natty but I've never seen an option in other releases either.
Comment 1 André Klapper 2020-11-12 14:27:12 UTC
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).