From: David Miller <davem@davemloft.net>
To: usenet07@philpem.me.uk
Cc: 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 14:34:09 -0700 (PDT) [thread overview]
Message-ID: <20070517.143409.102123884.davem@davemloft.net> (raw)
In-Reply-To: <f2ifnf$ooh$1@sea.gmane.org>
From: Philip Pemberton <usenet07@philpem.me.uk>
Date: Thu, 17 May 2007 21:59:31 +0100
> 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.
next prev parent reply other threads:[~2007-05-17 21:34 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 [this message]
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=20070517.143409.102123884.davem@davemloft.net \
--to=davem@davemloft.net \
--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