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 548114 - NM 0.7 Fails To Set Custom MTU
NM 0.7 Fails To Set Custom MTU
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: nm-applet
unspecified
Other All
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
: 544069 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-08-17 10:19 UTC by Nullack
Modified: 2008-10-06 10:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nullack 2008-08-17 10:19:51 UTC
Please describe the problem:
Im on revision 0.80 of NM on Intrepid Ibex Alpha. The edit gui for auto eth0 has the default MTU size as automatic. When a user populates the field to 1492 which is a valid field population the GUI accepts the value but actually fails to implement it. If the user manually does a /etc/init.d/networking stop and start and then queries the terminal via sudo ifconfig eth0 it is seen that the MTU has once again been reset to 1500 instead of 1492.

My original bug on the Ubuntu bug tracker:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/258743

Steps to reproduce:
1. Right click NM applet
2. Select edit connections
3. Select auto eth0 and edit
4. Change MTU from automatic to 1492
5. Close and observe no effect
6. Restart networking and observe no effect
7. Reopen applet and see the mtu is back to automatic


Actual results:
MTU preference is not activated

Expected results:
User preference for MTU to be activated

Does this happen every time?
Yes

Other information:
Comment 1 Nullack 2008-08-17 10:23:28 UTC
Sorry typo - Im on 0.7.0 which in the Ubuntu repo appears to be from your SVN dated 20080721
Comment 2 Dan Williams 2008-08-17 12:51:45 UTC
confirmed; page-wired.c isn't connecting widget changed signals correctly to update the connection when settings change.  pretty easy fix.
Comment 3 Dan Williams 2008-08-17 22:59:24 UTC
*** Bug 544069 has been marked as a duplicate of this bug. ***
Comment 4 Nullack 2008-08-27 20:25:19 UTC
I'm unable to set a target milestone so can I please comment that should this bug enter into production it is a common use case where user's want to set specific wired ethernet settings and not use DHCP. I will be delighted to assist with testing on any builds with a fix in it, thanks.
Comment 5 Dan Williams 2008-10-06 10:51:49 UTC
Should be fixed I as of today's SVN, though it's been fixed for a while I think.