public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Philip Pemberton <usenet07@philpem.me.uk>
To: linux-kernel@vger.kernel.org
Subject: IPv6: 6to4 tunnel randomly cutting out on 2.6.8.1 - any patches?
Date: Thu, 17 May 2007 21:59:31 +0100	[thread overview]
Message-ID: <f2ifnf$ooh$1@sea.gmane.org> (raw)

Hi,
   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...

   What I've done is set up an IPv6 subnet via the SixXS tunnel broker (and 
I've also tried the BT Exact tunnel broker, which has the same problem). This 
tunnel is then routed onto my LAN and set up router advertisement (with radvd) 
so the machines can get access to the IPv6 side of the Internet.

   The problem is that every 10 minutes or so, the IPv6 link (apparently the 
routing side as the router can still ping kame.net, but the other machines on 
the LAN can't) stops working for a few seconds (between 5 and 60) and comes 
back up of its own free will. Running the tunnel on another machine (with a 
2.6.16 kernel) stops the problem completely - IPv6 works perfectly. But being 
the energy-conscious person I am, I'd prefer to have as few machines powered 
up as possible.

   When IPv6 stops working, ping returns the error "sendmsg: Network is 
unreachable". The intermittent nature of this issue, and the fact that IPv6 
works fine when I move routing to a machine with a later kernel, leads me to 
believe that this may be an old kernel bug that got fixed in a later release, 
but evidently not this one...

   There appear to be a number of IPv6 related fixes in 2.6.9, but the patches 
are all globbed together in a single "patch-2.6.9.bz2" file - I'd like to 
apply some of the more promising ones directly, and try and fix the problem 
that way. The problem being that I can't find these patches as individual 
"this fixes X" releases, just as one huge 'go from 2.6.8.1 to 2.6.9' glob, and 
the git repository on kernel.org only seems to go back to 2.6.11.

   So what I'm wondering is, does anyone know if a bug like I've described was 
ever found between 2.6.8.1 and 2.6.16, and if so how it can be fixed?

Thanks.
-- 
Phil.                         |  (\_/)  This is Bunny. Copy and paste Bunny
usenet07@philpem.me.uk        | (='.'=) into your signature to help him gain
http://www.philpem.me.uk/     | (")_(") world domination.
If mail bounces, replace "07" with the last two digits of the current year.


             reply	other threads:[~2007-05-17 21:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17 20:59 Philip Pemberton [this message]
2007-05-17 21:34 ` IPv6: 6to4 tunnel randomly cutting out on 2.6.8.1 - any patches? David Miller
2007-05-17 21:46   ` Philip Pemberton
2007-05-19  7:52     ` Jan Engelhardt
2007-05-19 16:48       ` Pekka Pietikainen
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='f2ifnf$ooh$1@sea.gmane.org' \
    --to=usenet07@philpem.me.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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