[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20070427160554.8419450c.akpm@linux-foundation.org>
Date: Fri, 27 Apr 2007 16:05:54 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: netdev@...r.kernel.org
Cc: "bugme-daemon@...nel-bugs.osdl.org"
<bugme-daemon@...zilla.kernel.org>, frlinux@...inux.net
Subject: Re: [Bugme-new] [Bug 8382] New: 2.6.20 cannot route packets outside
tunnel
,On Fri, 27 Apr 2007 16:01:04 -0700
bugme-daemon@...zilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8382
>
> Summary: 2.6.20 cannot route packets outside tunnel
> Kernel Version: 2.6.20.9
> Status: NEW
> Severity: high
> Owner: yoshfuji@...ux-ipv6.org
> Submitter: frlinux@...inux.net
>
>
> Most recent kernel where this bug did *NOT* occur: 2.6.19.7
> Distribution: Debian Etch 4.0
> Hardware Environment: i386 VIA Samuel 2 700mhz
> Software Environment: Debian Etch
> Problem Description:
>
> I am using an IPv6 tunnel broker (SixXs) which is using aiccu (dynamic IPv4
> address using heartbeat to get in sync with IPv6 tunnel to SixXS). When using
> 2.6.20.x it doesn't route packets outside the tunnel anymore. This means that
> from my gateway, i can ping my local interface and my remote one but not a
> single other IPv6 address.
>
> When trying to traceroute or send IPv6 packets from any other machine on my
> network to an outside IPv6 address, i keep getting a network unreachable message.
>
> This was tested against 2.6.20.{5,7,8,9} and also 2.6.19.6/7. It works perfectly
> on any 2.6.19.x kernel or previous but fails under 2.6.20.x
>
> I made a diff in the IPv6 stack between 19 and 20 but my programming skills are
> clearly lacking :(
>
> Steps to reproduce:
>
> Compile with IPv6 settings that I am including with this bug report, 2.6.19
> works, 2.6.20 doesn't.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists