public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: linux-kernel@vger.kernel.org
Cc: felix-linuxkernel@fefe.de
Subject: Re: ipv6 getting more and more broken
Date: Fri, 10 Dec 2004 23:14:59 +0100	[thread overview]
Message-ID: <41BA1FE3.3020108@g-house.de> (raw)
In-Reply-To: <20041209024649.GA26553@codeblau.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

felix-linuxkernel@fefe.de schrieb:
> ipv6 is broken for me with 2.6.9 (worked great with 2.6.7, less good but
> still workable with 2.6.8).  Here are the symptoms:

i *felt* something was wrong around 2.6.8.1 or 2.6.9 but i tried to blame
my (free) tunnel broker. having 2.6.10-BK for a while now, everything is
back to normal. link-local addresses assigned, radvd is working too.

> Also, I would like to have a way to do mss clamping for IPv6.  I am
> running a Linux based PPPoE router using 6to4, and would like to
> route IPv6 to the LAN behind it, but TCP connections keep getting stuck.

hm, no issues here. mss clamping is described very often, but i never
really needed it. my ipv6 clients are working fine ;)

Christian.
- --
BOFH excuse #221:

The mainframe needs to rest.  It's getting old, you know.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBuh/j+A7rjkF8z0wRAqTeAJ9+wV+hN7SQdqJvTqd5QVfs32SuDgCePh0e
ZGUUSKv1plfZg2TNvmihQPU=
=UpiK
-----END PGP SIGNATURE-----

      parent reply	other threads:[~2004-12-10 22:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-09  2:46 ipv6 getting more and more broken felix-linuxkernel
2004-12-09  3:44 ` Aleksandar Milivojevic
2004-12-09  4:42 ` David S. Miller
2004-12-09  7:19 ` Jeff Garzik
2004-12-10 22:14 ` Christian Kujau [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=41BA1FE3.3020108@g-house.de \
    --to=evil@g-house.de \
    --cc=felix-linuxkernel@fefe.de \
    --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