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

Bug#411839: marked as done (linux-2.6: IPv6 PMTU table not garbage collected?)

Your message dated Sat, 5 Jul 2008 12:05:28 +0200
with message-id <20080705100528.GG7212@baikonur.stro.at>
and subject line Re: linux-2.6: IPv6 PMTU table not garbage collected?
has caused the Debian Bug report #411839,
regarding linux-2.6: IPv6 PMTU table not garbage collected?
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.)


-- 
411839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411839
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-2.6
Version: 2.6.18-8
Severity: normal

Symptoms: After a few weeks/months of uptime, my IPv6 machines whose
IPv6 "first hop" link MTU is more than the minimum (1280) stop
reacting to ICMPv6 "too big" packets and keep sending TCP packets
above the MTU of the path to other hosts.

Expected behaviour: After getting an ICMPv6 "too big" packet, send only
packets smaller than the MTU in given in that ICMPv6 packet to this
host.

Analysis:

I get the impression that the table where the kernel keeps the PMTU to
the IPv6 hosts it communicates with overflows over time, after a few
weeks or months of uptime. It looks like entries in that table expire
(because I do get the too big packets problem with hosts my hosts
communicate with a lot, they certainly were in the table in the past),
but that the place taken by expired entries is not freed up. Thus the
table doesn't get new entries added when the ICMPv6 "too big" packet
comes in and the TCP stack doesn't go back to smaller packets.

The symptoms seen by the users is that e.g. a SSH or SMTP connection
gets established OK, but once they start doing something "big" with it
(like the DATA phase of the SMTP dialogue or doing an ls of a big
directory in a ssh session), the connexion freezes. Once that effect
kicks in, it affects all new IPv6 connections/hosts. A tcpdump shows
that ICMPv6 "too big" packets come in, but that my host keeps sending
too big packets. A reboot cures it.

I vaguely remember that the first time this happened, I found some
statistics file in /proc/ or /sys/ where one line said some table had
4095 entries, which led me to this analysis. Alas, when it happened
again I could not remember what file that was and can't find it again
now. I didn't report it at the time because the kernel run by this
machine is rather old. But now it happened on a machine running
2.6.18-3-amd64, and "echo 8192 > /proc/sys/net/ipv6/route/max_size"
seems to have helped the problem.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-amd64
Locale: LANG=fr_LU.UTF-8, LC_CTYPE=fr_LU.UTF-8 (charmap=UTF-8)

--- End Message ---
--- Begin Message --- 
Version: 2.6.24-1

On Sat, Jul 05, 2008 at 06:09:40AM +0200, Lionel Elie Mamane wrote:
> On Fri, Jul 04, 2008 at 10:54:03PM +0200, maximilian attems wrote:
> > can you still reproduce that with an uptodate kernel
> > at best 2.6.25? it has newer ipv6 with more features and fixes?
> 
> I haven't encountered the problem in a long time.
> 
> -- 
> Lionel

thus closing, thanks for the feedback!

-- 
maks

--- End Message ---
Reply to: