From: Harald Welte <laforge@gnumonks.org>
To: "YOSHIFUJI Hideaki / ?$B5HF#1QL@" <yoshfuji@linux-ipv6.org>
Cc: netdev@oss.sgi.com, usagi-users@linux-ipv6.org
Subject: Re: 2.6.8.1 IPv6 Routing Problem
Date: Sun, 19 Sep 2004 00:02:11 +0200 [thread overview]
Message-ID: <20040918220211.GI6005@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20040918.084304.75142669.yoshfuji@linux-ipv6.org>
[-- Attachment #1: Type: text/plain, Size: 2379 bytes --]
On Sat, Sep 18, 2004 at 08:43:04AM +0900, YOSHIFUJI Hideaki / ?$B5HF#1QL@ wrote:
> > I'm experiencing some strange problems on a 2.6.8.1 vanilla kernel. I
> > tried to reproduce it with a minimal system:
> :
> > (intermixed with a 'ip6tables -A OUTPUT -j LOG' and '-A INPUT -j LOG'
> > rules for diagnostics).
>
> It is not minimum with ip6tables. :-)
i just added ip6tables to get some log messages on incoming/outgoing
packets (small embedded system with no tcpdump).
> Anyway, please try the latest bk tree.
> There are may fixes in it.
In fact the problem disappeared with 2.6.9-rc2. I thought the idea of
2.6.8.x is to have real show-stopper bugfixes go into that series... and
if something like this is severely broken in ipv6, I would say it
rectifies a 2.6.8.2 release, don't you think?
I have to admit that this is the first time that my linux ipv6 setup
breaks within four years...
Now I'm stuck with another issue: The interfaces suddenly no logner
get any link-local addresses:
/proc/net # ip -6 addr
2: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qlen 1000
inet6 3ffe:400:900:1100::1/64 scope global
valid_lft forever preferred_lft forever
inet6 3ffe:400:900:1100:207:e9ff:fe09:b920/64 scope global
valid_lft forever preferred_lft forever
3: lo: <LOOPBACK,UP> mtu 16436
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
4: eth0.2: <BROADCAST,MULTICAST,UP> mtu 1500
inet6 3ffe:400:900:1101::1/64 scope global
valid_lft forever preferred_lft forever
inet6 3ffe:400:900:1101:207:e9ff:fe09:b920/64 scope global
valid_lft forever preferred_lft forever
5: eth0.3: <BROADCAST,MULTICAST,UP> mtu 1500
inet6 3ffe:400:900:9999::1/64 scope global
valid_lft forever preferred_lft forever
inet6 3ffe:400:900:9999:207:e9ff:fe09:b920/64 scope global
valid_lft forever preferred_lft forever
8: tap0: <BROADCAST,MULTICAST,UP> mtu 1399 qlen 1000
inet6 3ffe:400:900:3001::2/64 scope global
valid_lft forever preferred_lft forever
/proc/net # uname -r
2.6.9-rc2
Thanks!
--
- Harald Welte <laforge@gnumonks.org> http://www.gnumonks.org/
============================================================================
Programming is like sex: One mistake and you have to support it your lifetime
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-18 22:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-17 23:08 2.6.8.1 IPv6 Routing Problem Harald Welte
2004-09-17 23:43 ` YOSHIFUJI Hideaki / 吉藤英明
2004-09-18 0:28 ` (usagi-users 03036) " YOSHIFUJI Hideaki / 吉藤英明
2004-09-18 22:02 ` Harald Welte [this message]
2004-09-19 1:06 ` David S. Miller
2004-09-19 2:11 ` YOSHIFUJI Hideaki / 吉藤英明
2004-09-19 2:20 ` YOSHIFUJI Hideaki / 吉藤英明
2004-09-19 7:46 ` Harald Welte
2004-09-20 5:08 ` Pekka Savola
2004-09-20 6:20 ` YOSHIFUJI Hideaki / 吉藤英明
2004-09-22 2:57 ` David S. Miller
2004-09-22 3:06 ` YOSHIFUJI Hideaki / 吉藤英明
2004-12-25 11:54 ` Harald Welte
2004-12-25 21:56 ` David S. Miller
2004-12-26 5:45 ` Herbert Xu
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=20040918220211.GI6005@sunbeam.de.gnumonks.org \
--to=laforge@gnumonks.org \
--cc=netdev@oss.sgi.com \
--cc=usagi-users@linux-ipv6.org \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).