From: Harald Welte <laforge@netfilter.org>
To: netdev@oss.sgi.com
Cc: usagi-users@linux-ipv6.org
Subject: 2.6.8.1 IPv6 Routing Problem
Date: Sat, 18 Sep 2004 01:08:03 +0200 [thread overview]
Message-ID: <20040917230803.GJ2678@sunbeam.de.gnumonks.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 4628 bytes --]
Hi!
I'm experiencing some strange problems on a 2.6.8.1 vanilla kernel. I
tried to reproduce it with a minimal system:
1) address configuration (just loopback, link-local and one global)
/proc/sys/net/ipv6/conf # ip -6 addr show
1: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qlen 1000
inet6 3ffe:400:900:3001::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::20d:b9ff:fe00:a88/64 scope link
valid_lft forever preferred_lft forever
3: lo: <LOOPBACK,UP> mtu 16436
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2) routing table:
/proc/sys/net/ipv6/conf # ip -6 route show
3ffe:400:900:3001::/64 dev eth0 metric 256
fe80::/64 dev eth0 metric 256
ff00::/8 dev eth0 metric 256
default dev eth0 metric 256
unreachable default dev lo metric -1 error -101
3) ping to localhost:
(intermixed with a 'ip6tables -A OUTPUT -j LOG' and '-A INPUT -j LOG'
rules for diagnostics).
/proc/sys/net/ipv6/conf # ping6 ::1
PING ::1 (::1): ou IN= OUT=lo 56 data bytes
SRC=0000:0000:0000:0000:0000:0000:0000:0001 DST=0000:0000:0000:0000:0000:0000:0000:0001 LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=27911 SEQ=0
in IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:86:dd SRC=0000:0000:0000:0000:0000:0000:0000:0001 DST=0000:0000:0000:0000:0000:0000:0000:0001 LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=27911 SEQ=0
ou IN= OUT=lo SRC=0000:0000:0000:0000:0000:0000:0000:0001 DST=0000:0000:0000:0000:0000:0000:0000:0001 LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=129 CODE=0 ID=27911 SEQ=0
in IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:86:dd SRC=0000:0000:0000:0000:0000:0000:0000:0001 DST=0000:0000:0000:0000:0000:0000:0000:0001 LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=129 CODE=0 ID=27911 SEQ=0
64 bytes from ::1: icmp6_seq=0 ttl=64 time=246.2 ms
4) ping to global address
/proc/sys/net/ipv6/conf # ping6 3ffe:400:900:3001::2
PING 3ffe:400:90ou IN= OUT=eth0 0:3001::2 (3ffe:SRC=3ffe:0400:0900:3001:0000:0000:0000:0002 400:900:3001::2)DST=3ffe:0400:0900:3001:0000:0000:0000:0002 : 56 datLEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0
PROTO=ICMPv6 TYPE=128 CODE=0 ID=28167 SEQ=0
ou IN= OUT=eth0 SRC=3ffe:0400:0900:3001:0000:0000:0000:0002 DST=ff02:0000:0000:0000:0000:0001:ff00:0002 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=135 CODE=0
ou IN= OUT=eth0 SRC=3ffe:0400:0900:3001:0000:0000:0000:0002 DST=ff02:0000:0000:0000:0000:0001:ff00:0002 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=135 CODE=0
ou IN= OUT=eth0 SRC=3ffe:0400:0900:3001:0000:0000:0000:0002 DST=3ffe:0400:0900:3001:0000:0000:0000:0002 LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=28167 SEQ=256
ou IN= OUT=eth0 SRC=3ffe:0400:0900:3001:0000:0000:0000:0002 DST=ff02:0000:0000:0000:0000:0001:ff00:0002 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=135 CODE=0
ou IN= OUT=eth0 SRC=3ffe:0400:0900:3001:0000:0000:0000:0002 DST=3ffe:0400:0900:3001:0000:0000:0000:0002 LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=28167 SEQ=512
ou IN= OUT=eth0 SRC=3ffe:0400:0900:3001:0000:0000:0000:0002 DST=3ffe:0400:0900:3001:0000:0000:0000:0002 LEN=152 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=1 CODE=3 [SRC=3ffe:0400:0900:3001:0000:0000:0000:0002 DST=3ffe:0400:0900:3001:0000:0000:0000:0002 LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=28167 SEQ=0 ]
ou IN= OUT=eth0 SRC=3ffe:0400:0900:3001:0000:0000:0000:0002 DST=ff02:0000:0000:0000:0000:0001:ff00:0002 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=135 CODE=0
ou IN= OUT=eth0 SRC=3ffe:0400:0900:3001:0000:0000:0000:0002 DST=3ffe:0400:0900:3001:0000:0000:0000:0002 LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=28167 SEQ=768
--- 3ffe:400:900:3001::2 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
Apparently the node tries to do neighbour solicitation on itself, and
then even sends an ICMPv6 destination unreachable to itself, all over
the ethernet device ?!?
Can anybody please explain what's going on?
Thanks!
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-09-17 23:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-17 23:08 Harald Welte [this message]
2004-09-17 23:43 ` 2.6.8.1 IPv6 Routing Problem YOSHIFUJI Hideaki / 吉藤英明
2004-09-18 0:28 ` (usagi-users 03036) " YOSHIFUJI Hideaki / 吉藤英明
2004-09-18 22:02 ` Harald Welte
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=20040917230803.GJ2678@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=netdev@oss.sgi.com \
--cc=usagi-users@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).