[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#503699: marked as done (tcp mtu negotiation issue in 2.6.18-6-amd64)

Your message dated Sat, 27 Dec 2008 22:27:04 +0100
with message-id <20081227212704.GA10547@galadriel.inutil.org>
and subject line Re: tcp mtu negotiation issue in 2.6.18-6-amd64
has caused the Debian Bug report #503699,
regarding tcp mtu negotiation issue in 2.6.18-6-amd64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
503699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503699
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.18-6-amd64
Version: 2.6.18.dfsg.1-22etch2
When configuring the network interface as mtu 9000, tcp mtu negotiation is not working correctly. When the debian server initiates a tcp connection and the other side tells it can only use mtu 1500, it is ignored and still uses its own mtu 9000 when sending packets. If the other side (which is using mtu 1500) initiates the connection, then the debian server drops down to 1500 and things are fine.
I updated to testing's kernel linux-image-2.6.26-1-amd64 which has resolved this issue and is working correctly. 

Rich

--- End Message ---
--- Begin Message --- 
Version: 2.6.26-1

On Mon, Oct 27, 2008 at 12:25:05PM -0500, Richard Wohlstadter wrote:
> Package: linux-image-2.6.18-6-amd64
> Version: 2.6.18.dfsg.1-22etch2
>
> When configuring the network interface as mtu 9000, tcp mtu negotiation  
> is not working correctly.  When the debian server initiates a tcp  
> connection and the other side tells it can only use mtu 1500, it is  
> ignored and still uses its own mtu 9000 when sending packets.  If the  
> other side (which is using mtu 1500) initiates the connection, then the  
> debian server drops down to 1500 and things are fine.
>
> I updated to testing's kernel linux-image-2.6.26-1-amd64 which has  
> resolved this issue and is working correctly.

Thanks, marking that version as fixed in 2.6.26 for unstable.

If you want to continue to run a supported Etch kernel you could
try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4:
http://packages.qa.debian.org/l/linux-2.6.24.html

Cheers,
        Moritz

--- End Message ---
Reply to: