[Bug 791280] New: MTU only at 576 with cable internet provicer via dhcp (eth0) - regression in iscdhcpclient?
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c0
Summary: MTU only at 576 with cable internet provicer via dhcp
(eth0) - regression in iscdhcpclient?
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: x86
OS/Version: openSUSE 12.1
Status: NEW
Severity: Major
Priority: P5 - None
Component: Network
AssignedTo: bnc-team-screening@forge.provo.novell.com
ReportedBy: abittner@abittner.de
QAContact: qa-bugs@suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.11 (KHTML, like
Gecko) Chrome/23.0.1271.64 Safari/537.11
moved an opensuse box to 12.1/x86, latest updates applied, multiple ethernet
cards and the internet provider changed from xdsl/pppoe to cableinternet via
simple dhcpv4 on ethernet card (pcie/onboard, realtek)
now I am wondering why my MTU for the eth0 interface that connects to the cable
modem gets set to 576 according to my research that is the lowest common mtu
value that is available according to various ethernet and dhcp specs.
some research landed me over at some ubuntu/debian bugs talking about some bad
dhcp script of the isc-dhcp-client, but which is supposedly fixed in isc-dhcp
4.2.2-1, but opensuse 12.1 has even newer?
I didnt have the chance to mess with enforcing some different MTU value on this
affected box, or bootup some other more recent opensuse 12.2 linux with that
cable modem or even try a windows machine directly with the cable modem just to
see if the mtu 576 is an issue there as well. I am currently only able to
remotely access this machine, thats why I am trying to avoid to disabling the
network by messing things up, maybe I can help more at a later time.
so maybe anyone can look into this if the isc-dhcp is really buggy and unfixed
with opensuse 12.1, and if those ubuntu/debian bugs with isc-dhcp are valid and
legit and somehow went missing in opensuse or some regeression got
re-introduced with a later isc-dhcp again?
thanks for helping to sort this out.
debian/ubuntu bugs:
http://osdir.com/ml/ubuntu-bugs/2011-12/msg27989.html
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/881558
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638267
bug excerpt:
.....
Bug Description
the following lines of /sbin/dhclient-script fails to detect MTU of 576:
~$ grep -A1 -n 'lt 576' /sbin/dhclient-script
177:if [ -z "$new_interface_mtu" ] || [ "$new_interface_mtu" -lt 576 ]; then
178- new_interface_mtu=''
The correct syntax is -le not -lt.
This has also been reported in debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638267
But should be a simple fix and not require a new package.
The result of this error is that the MTU of an interface configured by DHCP is
dropped down to 576.
.....
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Actual Results:
I am originally reporting this as the ethernet throughput on this cable
internet connected box is rather very low and sluggish and very jumpy, ssh
sessions for example are very erratic and weird, so that made me to looking for
the reason for this behavior and I then came across those MTU 576 issues. But
then again I was also thinking about some kernel/driver(realtek) issues or
incompatibilities or similar. Not quite sure.
tuxmachine:/sbin # grep 576 *
dhclient-script: $(( $new_interface_mtu )) -lt 576 ] ;
dhclient-script: # 68 is the minimal legal value, but 576 the real life
minimum
tuxmachine:/sbin # ls -lart dhc*
-rwxr-xr-x 1 root root 76284 Oct 29 2011 dhcpcd
-rwxr-x--- 1 root root 19771 Sep 17 13:41 dhclient-script
-rwxr-xr-x 1 root root 1802884 Sep 17 13:41 dhclient
lrwxrwxrwx 1 root root 8 Nov 14 14:51 dhclient6 -> dhclient
rpm -aq | grep -i dhc
dhcpcd-3.2.3-47.70.1.2.i586
dhcp-client-4.2.4.P2-0.6.13.1.i586
dhcp-4.2.4.P2-0.6.13.1.i586
tuxmachine:/sbin # rpm -qi dhcp
Name : dhcp
Version : 4.2.4.P2
Release : 0.6.13.1
Architecture: i586
Install Date: Wed Nov 14 14:50:27 2012
Group : Productivity/Networking/Boot/Servers
Size : 1735945
License : BSD-3-Clause
Signature : RSA/SHA256, Wed Sep 26 16:45:42 2012, Key ID b88b2fd43dbdc284
Source RPM : dhcp-4.2.4.P2-0.6.13.1.src.rpm
Build Date : Mon Sep 17 13:41:41 2012
Build Host : build19
Relocations : (not relocatable)
Packager : http://bugs.opensuse.org
Vendor : openSUSE
URL : http://www.isc.org/software/dhcp
Summary : Common Files Used by ISC DHCP Software
Description :
This package contains common programs used by both the ISC DHCP
server ("dhcp-server" package) and client ("dhcp-client") as the
omshell and common manual pages.
Authors:
--------
Internet Systems Consortium, Inc.
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c
Jiaying ren
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c1
--- Comment #1 from andreas bittner
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c2
--- Comment #2 from andreas bittner
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c3
--- Comment #3 from andreas bittner
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c4
Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c5
--- Comment #5 from Marius Tomaschewski
What also seems odd about the dhcp with the german cableinternet provider is the very low lease times in a few thousand seconds worth of lease time only? Although some documentation was speaking about those numbers were being minutes, but thats somehow not the case here?
No, the times are in secs. "Usually", you'll get the same IP address, but you have to start a renew after 44 minutes (2676/60). When you don't do, the lease (& IP address) will expire after 78 minutes. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c6
--- Comment #6 from Marius Tomaschewski
Question now is, how can an Interface be kept at 1500MTU if its wired ethernet via yast2 or some config files the best ways without being too hacky.
You can use "yast2 sysconfig" to set -M in /etc/sysconfig/network/dhcp. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c7
--- Comment #7 from andreas bittner
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c8
--- Comment #8 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c9
--- Comment #9 from andreas bittner
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c10
--- Comment #10 from Marius Tomaschewski
I already had that minimal request line in the config file last week, and that didnt help. I now have additionally the -M parameter in the other config file in sysconfig directory, that helps
Sure... sysconfig can use two different dhcp clients: dhcpcd: default client, needs DHCPCD_USER_OPTIONS='-M' parameter dhclient: ISC client from "dhcp-client" package, makes use of the /etc/dhclient.conf file. The dhclient is used only, when you change the DHCLIENT_BIN to "dhclient" in /etc/sysconfig/network/dhcp. Otherwise dhcpcd.
so should I then contact this ISP and tell them about their misbehaviour or something? Is somebody disrespecting any RFCs or standards or anything?
No, I don't see anything would break some RFCs... The server reports what the administrator configured. It is expected, the admin provides an MTU, which is suitable for the connection, ... This low and inconsistent mtu (I guess, your gateway isn't using 576) causes a lot of "Path MTU Discovery" resends and when some firewall blocks the ICMP notifications on the path, ... You can try to report it to the ISP as it disrupts you and lowers the througput; I which you luck! But I don't think they will change this... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c15
--- Comment #15 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c16
--- Comment #16 from Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c17
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=791280
https://bugzilla.novell.com/show_bug.cgi?id=791280#c18
--- Comment #18 from Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com