Bug 1047083 - FC20 Regression DHCP Client ignores interface-mtu DHCP Option
Summary: FC20 Regression DHCP Client ignores interface-mtu DHCP Option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-28 22:22 UTC by Derek Atkins
Modified: 2014-07-04 12:29 UTC (History)
3 users (show)

Fixed In Version: NetworkManager-0.9.9.0-41.git20131003.fc20
Clone Of:
Environment:
Last Closed: 2014-07-04 12:29:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 721420 0 None None None Never
Red Hat Bugzilla 1093231 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 1093231

Description Derek Atkins 2013-12-28 22:22:06 UTC
Description of problem:

Earlier versions of Fedora honored the interface-mtu setting.
Fedora 20 does not.
This is critical for networks where the default MTU does not work and DHCP tells the client what MTU top use.
Note that this worked in previous versions of Fedora, so this is a regression in F20.

Version-Release number of selected component (if applicable):

NetworkManager-0.9.9.0-22.git20131003.fc20.x86_64
dhcp-common-4.2.5-26.fc20.x86_64
dhcp-libs-4.2.5-26.fc20.x86_64
dhclient-4.2.5-26.fc20.x86_64

How reproducible:
100%


Steps to Reproduce:
1. Issue an interface-mtu option in a DHCP configuration
2. Start a F20 DHCP client connection against that config
3. Notice that the dhcp lease in /var/lib/NetworkManager... contains the correct interface-mtu setting from the DHCP config
4. Notice that "ifconfig" shows the default MTU, not the setting from the dhcp lease

Actual results:
The interface sets the default MTU, ignoring the dhcp setting.
In my case this causes all TCP traffic to fail because the default MTU is too big for the network

Expected results:

the DHCP client should honor the interface-mtu setting like it did in previous versions of Fedora.

Additional info:

The lease info in /var/lib/... contains:

lease {
  interface "ens32";
   ...
  option interface-mtu 1476;
   ...
}

But ifconfig has an MTU of 1500.

Comment 1 Jirka Klimes 2014-04-22 09:08:48 UTC
A fix has been pushed upstream:
0757e33 core: fix MTU handling while merging/subtracting IP configs (bgo #721420)

Comment 2 Fedora Update System 2014-07-02 16:07:06 UTC
NetworkManager-0.9.9.0-41.git20131003.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/NetworkManager-0.9.9.0-41.git20131003.fc20

Comment 3 Fedora Update System 2014-07-03 04:10:27 UTC
Package NetworkManager-0.9.9.0-41.git20131003.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing NetworkManager-0.9.9.0-41.git20131003.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-8033/NetworkManager-0.9.9.0-41.git20131003.fc20
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2014-07-04 12:29:49 UTC
NetworkManager-0.9.9.0-41.git20131003.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.