public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pekka Pietikainen <pp@ee.oulu.fi>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Philip Pemberton <usenet07@philpem.me.uk>, linux-kernel@vger.kernel.org
Subject: Re: IPv6: 6to4 tunnel randomly cutting out on 2.6.8.1 - any   patches?
Date: Sat, 19 May 2007 19:48:03 +0300	[thread overview]
Message-ID: <20070519164802.GA10510@ee.oulu.fi> (raw)
In-Reply-To: <Pine.LNX.4.61.0705190950370.9015@yvahk01.tjqt.qr>

On Sat, May 19, 2007 at 09:52:57AM +0200, Jan Engelhardt wrote:
> >> >   I'm currently trying to set IPv6 up on a Linux-based router. The
> >> > aforementioned router runs kernel 2.6.8.1, and just about all the
> >> > hardware driver modules are binary modules. For the record, I'd love
> >> > to upgrade the router to one of the newer kernels, but AIUI I can't do
> >> > it because I don't have the source to the bmods. But anyway...
> How can you tell? The binary blobs may have a glitch, flaw, bug, that
> makes them write more-or-less random values to random memory locations,
> thereby inadvertently killing the functionality of other modules (such
> as the ipv6 tunnel).
> 
> If the bug happens without the blobs, _then_ one may start figuring out
> what (non-binary) modules may cause interaction problems with the ipv6
> tunnel (or if it's the tunnel module itself).
Then again, IPv6 in < 2.6.can't remember, but .8 is one of them
_was_ pretty awful. I think it started being okish around .14 or .15?

If you feel like spending lots of time, you could try to shoehorn net/*
from the latest rhel4/centos4 kernel (2.6.9-based) into your router, someone
might have spent the effort fixing the relevant bugs in that tree (but maybe
not, until the 4.5 kernel it used to spew Badness in dst_release at
include/net/dst.h:149 every few seconds if your box was on a ipv6 network :D
)

Personally, I'd get a new router without binary blobs, value of time spent
doing the shoehorning > price of new router, I'm sure, but you may value
your free time differently :)

I do know sixxs ipv6 tunnels are rock solid with openwrt (2.4-based) ;)

  reply	other threads:[~2007-05-19 16:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17 20:59 IPv6: 6to4 tunnel randomly cutting out on 2.6.8.1 - any patches? Philip Pemberton
2007-05-17 21:34 ` David Miller
2007-05-17 21:46   ` Philip Pemberton
2007-05-19  7:52     ` Jan Engelhardt
2007-05-19 16:48       ` Pekka Pietikainen [this message]
2007-05-19 18:12         ` Philip Pemberton

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=20070519164802.GA10510@ee.oulu.fi \
    --to=pp@ee.oulu.fi \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=usenet07@philpem.me.uk \
    /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