From: Philip Pemberton <usenet07@philpem.me.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: IPv6: 6to4 tunnel randomly cutting out on 2.6.8.1 - any patches?
Date: Thu, 17 May 2007 22:46:14 +0100 [thread overview]
Message-ID: <f2iif3$3u3$1@sea.gmane.org> (raw)
In-Reply-To: <20070517.143409.102123884.davem@davemloft.net>
David Miller 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...
>
> Then don't come here looking for support, because we can't
> help you.
All I said was "I can't upgrade the kernel". There's nothing stopping me
patching it, as long as nothing happens to the Ethernet and ATM driver
interface side of things - this is all protocol-layer stuff and should be well
away from the EDI. I can't honestly see why/how fixing a bug in IPv6 would
completely invalidate the way the Ethernet/ATM drivers interface with the kernel.
All I wanted to know is if if there WAS a known IPv6 routing issue in this
kernel, and then fix the kernel I've got. That would leave me with a variant
of the kernel in itself.
I'm not claiming to have found an Oops, nor am I providing an Oops log from a
tainted kernel. All I'm trying to do is find out WHY this doesn't work, IF
it's a known issue, and HOW to fix it myself.
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.
next prev parent reply other threads:[~2007-05-17 21:46 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 [this message]
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='f2iif3$3u3$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