From: Cliff Albert <cliff@oisec.net>
To: poptix <poptix@poptix.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.4.4, 2.4.4-ac1, 2.4.4-ac2, neighbour discovery bug (ipv6)
Date: Thu, 3 May 2001 11:53:58 +0200 [thread overview]
Message-ID: <20010503115358.A7793@oisec.net> (raw)
In-Reply-To: <20010501154437.A23200@oisec.net> <Pine.LNX.4.33.0105022155090.444-100000@3jane.ashpool.org>
In-Reply-To: <Pine.LNX.4.33.0105022155090.444-100000@3jane.ashpool.org>; from poptix@poptix.net on Wed, May 02, 2001 at 09:56:20PM +0200
On Wed, May 02, 2001 at 09:56:20PM +0200, poptix wrote:
> >
> > When i traceroute6 my 2.4.4 box on my local lan, the 2.4.4 box panic's after about 10 seconds. The traceroute6 completes on the other box.
> >
> > 2.4.3-ac14 doesn't experience these problems. Only 2.4.4 (with or without ac{1,2}) panics
> >
> > ---- traceroute6 output ----
> > traceroute to neve.oisec.net (3ffe:8114:2000:0:250:bfff:fe21:629a) from 3ffe:8114:2000:0:210:4bff:feb3:1fb4, 30 hops max, 16 byte packets
> > 1 neve.oisec.net (3ffe:8114:2000:0:250:bfff:fe21:629a) 0.583 ms 0.278 ms 0.233 ms
> >
> >
> [snip]
>
> I am unable to reproduce this, either locally or remotely, I am also using
> the 2.4.4 kernel, do you have any more information on this, and is it
> possible to reproduce every time?
Was reproducable every single time, on multiple machines. a simple PING6 or TRACEROUTE6 would kill the box. Using native connection or tunneled connection doesn't matter after some investigation.
--
Cliff Albert | IRCNet: #linux.nl, #ne2000, #linux, #freebsd.nl
cliff@oisec.net | #openbsd, #ipv6, #cu2.nl
-[ICQ: 18461740]--------| 6BONE: CA2-6BONE RIPE: CA3348-RIPE
prev parent reply other threads:[~2001-05-03 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 13:44 PROBLEM: 2.4.4, 2.4.4-ac1, 2.4.4-ac2, neighbour discovery bug (ipv6) Cliff Albert
2001-05-02 19:56 ` poptix
2001-05-03 9:53 ` Cliff Albert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010503115358.A7793@oisec.net \
--to=cliff@oisec.net \
--cc=linux-kernel@vger.kernel.org \
--cc=poptix@poptix.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox