NetBSD Problem Report #34686

From reinoud@13thmonkey.org  Sun Oct  1 14:40:18 2006
Return-Path: <reinoud@13thmonkey.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id BFB8463B9D6
	for <gnats-bugs@gnats.NetBSD.org>; Sun,  1 Oct 2006 14:40:18 +0000 (UTC)
Message-Id: <20061001144013.256D45307@rangerover.13thmonkey.org>
Date: Sun,  1 Oct 2006 16:40:12 +0200 (CEST)
From: reinoud@netbsd.org
Reply-To: reinoud@netbsd.org
To: gnats-bugs@NetBSD.org
Subject: IPv6 neighbour discovery going wrong
X-Send-Pr-Version: 3.95

>Number:         34686
>Category:       kern
>Synopsis:       IPv6 neighbour discovery going wrong
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    is
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Oct 01 14:45:00 +0000 2006
>Closed-Date:    Sat Mar 24 08:02:23 +0000 2018
>Last-Modified:  Sat Mar 24 08:02:23 +0000 2018
>Originator:     Reinoud Zandijk
>Release:        NetBSD 4.0_BETA
>Organization:

>Environment:


System: NetBSD rangerover 4.0_BETA NetBSD 4.0_BETA (GENERIC) #2: Sun Oct 1 14:22:50 CEST 2006 reinoud@heethoofdje.kasbah:/usr/tmp/heethoofdje.obj/sys/arch/sparc/compile/GENERIC sparc
Architecture: sparc
Machine: sparc

My rc.d is configured as follows :
# networking
ip6mode=router
ip6uniquelocal=YES
rtsol=NO
route6d=YES
route6d_flags=""
pf=YES

 210c211
 < #options 	GATEWAY		# packet forwarding ("router switch")
 ---
 > options 	GATEWAY		# packet forwarding ("router switch")
 214c215
 < options 	NS		# Xerox NS networking
 ---
 > #options 	NS		# Xerox NS networking
 216c217
 < options 	ISO,TPIP	# OSI networking
 ---
 > #options 	ISO,TPIP	# OSI networking
 225,227c226,228
 < options 	PPP_BSDCOMP	# Add BSD compression to ppp device
 < options 	PPP_DEFLATE	# Add deflate (libz) compression to ppp device
 < options 	PPP_FILTER	# Add active filters for ppp (via bpf)
 ---
 > #options 	PPP_BSDCOMP	# Add BSD compression to ppp device
 > #options 	PPP_DEFLATE	# Add deflate (libz) compression to ppp device
 > #options 	PPP_FILTER	# Add active filters for ppp (via bpf)
 608c609
 < pseudo-device	bridge
 ---
 > #pseudo-device	bridge

>Description:

The machine designated as a router is not pinging other machines until its 
pinged by them thus indicating a ndp problem AFAIK. As an example:

reinoud@rangerover 9> ping6 eek
PING6(56=40+8+8 bytes) 2001:7b8:341::1 --> 2001:7b8:341::f
16 bytes from 2001:7b8:341::f, icmp_seq=29 hlim=64 time=697.405 ms
16 bytes from 2001:7b8:341::f, icmp_seq=30 hlim=64 time=2.208 ms
16 bytes from 2001:7b8:341::f, icmp_seq=31 hlim=64 time=2.169 ms
16 bytes from 2001:7b8:341::f, icmp_seq=32 hlim=64 time=2.33 ms

eek: ping6 rangerover.13thmonkey.org
PING6(56=40+8+8 bytes) 2001:7b8:341::f --> 2001:7b8:341::1
16 bytes from 2001:7b8:341::1, icmp_seq=1 hlim=64 time=1.792 ms
^C

As soon as i ping back the router, it suddenly can ping the machine.



>How-To-Repeat:

tryout to ping a machine that is not yet in the ndp from a machine that is 
configured as an IPv6 router. It won't work until the destination machine 
pings the router once.


>Fix:
Unknown, propably and most likely inside IPv6 stack.


>Release-Note:

>Audit-Trail:
From: Rui Paulo <rpaulo@fnop.net>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/34686: IPv6 neighbour discovery going wrong
Date: Sun, 1 Oct 2006 15:50:24 +0100

 On Oct 1, 2006, at 3:45 PM, reinoud@netbsd.org wrote:

 >> Number:         34686
 >> Category:       kern
 >> Synopsis:       IPv6 neighbour discovery going wrong
 >> Confidential:   no
 >> Severity:       critical
 >> Priority:       high
 >> Responsible:    kern-bug-people
 >> State:          open
 >> Class:          sw-bug
 >> Submitter-Id:   net
 >> Arrival-Date:   Sun Oct 01 14:45:00 +0000 2006
 >> Originator:     Reinoud Zandijk
 >> Release:        NetBSD 4.0_BETA
 >> Organization:
 > 	
 >> Environment:
 > 	
 > 	
 > System: NetBSD rangerover 4.0_BETA NetBSD 4.0_BETA (GENERIC) #2:  
 > Sun Oct 1 14:22:50 CEST 2006 reinoud@heethoofdje.kasbah:/usr/tmp/ 
 > heethoofdje.obj/sys/arch/sparc/compile/GENERIC sparc
 > Architecture: sparc
 > Machine: sparc
 >
 > My rc.d is configured as follows :
 > # networking
 > ip6mode=router
 > ip6uniquelocal=YES
 > rtsol=NO
 > route6d=YES
 > route6d_flags=""
 > pf=YES
 >
 >  210c211
 >  < #options 	GATEWAY		# packet forwarding ("router switch")
 >  ---
 >> options 	GATEWAY		# packet forwarding ("router switch")
 >  214c215
 >  < options 	NS		# Xerox NS networking
 >  ---
 >> #options 	NS		# Xerox NS networking
 >  216c217
 >  < options 	ISO,TPIP	# OSI networking
 >  ---
 >> #options 	ISO,TPIP	# OSI networking
 >  225,227c226,228
 >  < options 	PPP_BSDCOMP	# Add BSD compression to ppp device
 >  < options 	PPP_DEFLATE	# Add deflate (libz) compression to ppp device
 >  < options 	PPP_FILTER	# Add active filters for ppp (via bpf)
 >  ---
 >> #options 	PPP_BSDCOMP	# Add BSD compression to ppp device
 >> #options 	PPP_DEFLATE	# Add deflate (libz) compression to ppp device
 >> #options 	PPP_FILTER	# Add active filters for ppp (via bpf)
 >  608c609
 >  < pseudo-device	bridge
 >  ---
 >> #pseudo-device	bridge
 >
 >> Description:
 >
 > The machine designated as a router is not pinging other machines  
 > until its
 > pinged by them thus indicating a ndp problem AFAIK. As an example:
 >
 > reinoud@rangerover 9> ping6 eek
 > PING6(56=40+8+8 bytes) 2001:7b8:341::1 --> 2001:7b8:341::f
 > 16 bytes from 2001:7b8:341::f, icmp_seq=29 hlim=64 time=697.405 ms
 > 16 bytes from 2001:7b8:341::f, icmp_seq=30 hlim=64 time=2.208 ms
 > 16 bytes from 2001:7b8:341::f, icmp_seq=31 hlim=64 time=2.169 ms
 > 16 bytes from 2001:7b8:341::f, icmp_seq=32 hlim=64 time=2.33 ms
 >
 > eek: ping6 rangerover.13thmonkey.org
 > PING6(56=40+8+8 bytes) 2001:7b8:341::f --> 2001:7b8:341::1
 > 16 bytes from 2001:7b8:341::1, icmp_seq=1 hlim=64 time=1.792 ms
 > ^C
 >
 > As soon as i ping back the router, it suddenly can ping the machine.
 >
 >
 > 	
 >> How-To-Repeat:
 >
 > tryout to ping a machine that is not yet in the ndp from a machine  
 > that is
 > configured as an IPv6 router. It won't work until the destination  
 > machine
 > pings the router once.
 >
 > 	
 >> Fix:
 > Unknown, propably and most likely inside IPv6 stack.
 > 	
 >
 >> Unformatted:
 >  Sources downloaded from 200609140000Z. Kernel from today.

 Can you give us more information about the state of ndp by printing  
 ndp entries?

 --
 Rui Paulo


From: Reinoud Zandijk <reinoud@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Subject: Re: kern/34686: IPv6 neighbour discovery going wrong
Date: Sun, 1 Oct 2006 17:13:00 +0200

 Hi Rui :),

 here it is!

 On Sun, Oct 01, 2006 at 02:55:03PM +0000, Rui Paulo wrote:
 >  >> Unformatted:
 >  >  Sources downloaded from 200609140000Z. Kernel from today.
 >  
 >  Can you give us more information about the state of ndp by printing  
 >  ndp entries?

 rangerover# ndp -a
 Neighbor                             Linklayer Address  Netif Expire    S Flags
 cl-46.ede-01.nl.sixxs.net            (incomplete)        gif0 permanent R 
 rangerover.13thmonkey.org            08:00:20:18:a7:22   hme0 permanent R 
 heethoofdje.13thmonkey.org           00:11:2f:52:44:7c   hme0 23h36m34s S 
 eek.13thmonkey.org                   (incomplete)        hme0 expired   N 
 fe80::a00:20ff:fe18:a722%le0         08:00:20:18:a7:22    le0 permanent R 
 fe80::a00:20ff:fe18:a722%hme0        08:00:20:18:a7:22   hme0 permanent R 
 fe80::1%lo0                          (incomplete)         lo0 permanent R 
 fe80::a00:20ff:fe18:a722%gif0        (incomplete)        gif0 permanent R 
 rangerover# 
 rangerover# 
 rangerover# ping6 eek.13thmonkey.org
 PING6(56=40+8+8 bytes) 2001:7b8:341::1 --> 2001:7b8:341::f
 ^C
 --- eek.13thmonkey.org ping6 statistics ---
 30 packets transmitted, 0 packets received, 100.0% packet loss
 rangerover# ndp -a
 Neighbor                             Linklayer Address  Netif Expire    S Flags
 cl-46.ede-01.nl.sixxs.net            (incomplete)        gif0 permanent R 
 rangerover.13thmonkey.org            08:00:20:18:a7:22   hme0 permanent R 
 heethoofdje.13thmonkey.org           00:11:2f:52:44:7c   hme0 23h36m0s  S 
 fe80::a00:20ff:fe18:a722%le0         08:00:20:18:a7:22    le0 permanent R 
 fe80::a00:20ff:fe18:a722%hme0        08:00:20:18:a7:22   hme0 permanent R 
 fe80::1%lo0                          (incomplete)         lo0 permanent R 
 fe80::a00:20ff:fe18:a722%gif0        (incomplete)        gif0 permanent R 
 rangerover# 


 eek pings rangerover


 rangerover# ndp -a
 Neighbor                             Linklayer Address  Netif Expire    S Flags
 cl-46.ede-01.nl.sixxs.net            (incomplete)        gif0 permanent R 
 rangerover.13thmonkey.org            08:00:20:18:a7:22   hme0 permanent R 
 heethoofdje.13thmonkey.org           00:11:2f:52:44:7c   hme0 23h35m27s S 
 eek.13thmonkey.org                   08:00:2b:81:61:1e   hme0 25s       R 
 fe80::a00:20ff:fe18:a722%le0         08:00:20:18:a7:22    le0 permanent R 
 fe80::a00:20ff:fe18:a722%hme0        08:00:20:18:a7:22   hme0 permanent R 
 fe80::1%lo0                          (incomplete)         lo0 permanent R 
 fe80::a00:20ff:fe18:a722%gif0        (incomplete)        gif0 permanent R 
 rangerover# 


 rangerover# ping6 eek.13thmonkey.org
 PING6(56=40+8+8 bytes) 2001:7b8:341::1 --> 2001:7b8:341::f
 16 bytes from 2001:7b8:341::f, icmp_seq=0 hlim=64 time=3.111 ms
 16 bytes from 2001:7b8:341::f, icmp_seq=1 hlim=64 time=2.238 ms
 ^C
 --- eek.13thmonkey.org ping6 statistics ---
 2 packets transmitted, 2 packets received, 0.0% packet loss
 round-trip min/avg/max/std-dev = 2.238/2.675/3.111/0.617 ms

 rangerover# 

From: Rui Paulo <rpaulo@fnop.net>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/34686: IPv6 neighbour discovery going wrong
Date: Sun, 1 Oct 2006 17:36:11 +0100

 On Oct 1, 2006, at 4:15 PM, Reinoud Zandijk wrote:
 >
 >  rangerover# ndp -a
 >  Neighbor                             Linklayer Address  Netif  
 > Expire    S Flags
 >  cl-46.ede-01.nl.sixxs.net            (incomplete)        gif0  
 > permanent R
 >  rangerover.13thmonkey.org            08:00:20:18:a7:22   hme0  
 > permanent R
 >  heethoofdje.13thmonkey.org           00:11:2f:52:44:7c   hme0  
 > 23h36m34s S
 >  eek.13thmonkey.org                   (incomplete)        hme0  
 > expired   N

 ^^^^^^^^^^^^

 Nothing will work while the entry is in this state.


 >  fe80::a00:20ff:fe18:a722%le0         08:00:20:18:a7:22    le0  
 > permanent R
 >  fe80::a00:20ff:fe18:a722%hme0        08:00:20:18:a7:22   hme0  
 > permanent R
 >  fe80::1%lo0                          (incomplete)         lo0  
 > permanent R
 >  fe80::a00:20ff:fe18:a722%gif0        (incomplete)        gif0  
 > permanent R
 >  rangerover#
 >  rangerover#
 >  rangerover# ping6 eek.13thmonkey.org
 >  PING6(56=40+8+8 bytes) 2001:7b8:341::1 --> 2001:7b8:341::f
 >  ^C
 >  --- eek.13thmonkey.org ping6 statistics ---
 >  30 packets transmitted, 0 packets received, 100.0% packet loss
 >  rangerover# ndp -a
 >  Neighbor                             Linklayer Address  Netif  
 > Expire    S Flags
 >  cl-46.ede-01.nl.sixxs.net            (incomplete)        gif0  
 > permanent R
 >  rangerover.13thmonkey.org            08:00:20:18:a7:22   hme0  
 > permanent R
 >  heethoofdje.13thmonkey.org           00:11:2f:52:44:7c   hme0  
 > 23h36m0s  S
 >  fe80::a00:20ff:fe18:a722%le0         08:00:20:18:a7:22    le0  
 > permanent R
 >  fe80::a00:20ff:fe18:a722%hme0        08:00:20:18:a7:22   hme0  
 > permanent R
 >  fe80::1%lo0                          (incomplete)         lo0  
 > permanent R
 >  fe80::a00:20ff:fe18:a722%gif0        (incomplete)        gif0  
 > permanent R
 >  rangerover#
 >
 >
 >  eek pings rangerover
 >
 >
 >  rangerover# ndp -a
 >  Neighbor                             Linklayer Address  Netif  
 > Expire    S Flags
 >  cl-46.ede-01.nl.sixxs.net            (incomplete)        gif0  
 > permanent R
 >  rangerover.13thmonkey.org            08:00:20:18:a7:22   hme0  
 > permanent R
 >  heethoofdje.13thmonkey.org           00:11:2f:52:44:7c   hme0  
 > 23h35m27s S
 >  eek.13thmonkey.org                   08:00:2b:81:61:1e   hme0  
 > 25s       R
                                                                 ^^^^^^^
 After the 25s does the entry stay in ``expired'' state ?

 --
 Rui Paulo


From: Reinoud Zandijk <reinoud@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Subject: Re: kern/34686: IPv6 neighbour discovery going wrong
Date: Sun, 1 Oct 2006 20:35:38 +0200

 --7AUc2qLy4jB3hD7Z
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline

 On Sun, Oct 01, 2006 at 04:40:03PM +0000, Rui Paulo wrote:
 >  >  rangerover# ndp -a
 >  >  Neighbor                             Linklayer Address  Netif  
 >  > Expire    S Flags
 >  >  cl-46.ede-01.nl.sixxs.net            (incomplete)        gif0  
 >  > permanent R
 >  >  rangerover.13thmonkey.org            08:00:20:18:a7:22   hme0  
 >  > permanent R
 >  >  heethoofdje.13thmonkey.org           00:11:2f:52:44:7c   hme0  
 >  > 23h35m27s S
 >  >  eek.13thmonkey.org                   08:00:2b:81:61:1e   hme0  
 >  > 25s       R
 >                                                                  ^^^^^^^
 >  After the 25s does the entry stay in ``expired'' state ?

 nope! it gets a nice 24 hours time slot :)

 I'll try again with a new kernel; build from scratch since i fear there 
 might be some gcc3 contamination in it :-S

 Reinoud


 --7AUc2qLy4jB3hD7Z
 Content-Type: application/pgp-signature
 Content-Disposition: inline

 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.2.1 (NetBSD)

 iQEVAwUBRSAKc4KcNwBDyKpoAQKF2Af/UTCuj865NIPRsLFXDR0b6CknuSHPJTIg
 VbfNiTSvpVg4ezMtP1tOsZw9PPDn+/sGDCKJ+l3EoBcsfnV/lotD+2I2kfxdBHxD
 nhnecfI6H2aX8rUeza1dbhWa0AhxYF2C7LJUN/CUjAdBt2wQbr55ON5/YMNMTWJb
 aQNWFKi15OS9cszxW6Ze8wekPWTfTRqRcJRCGBDiUSsIepjvMGGQxbKEN9NiVoKT
 wJQQQpNSUi42Fdl3AC/GgjQb9/aKKvXNj9ABPQv1bsmugHL7MoYCn3OwPbPyai7a
 fPYyUNXjg+VuYD4hMOUV3FP0kx5QJTvZy9f+SSHOTEYY5kxQ+HxWDQ==
 =Vte4
 -----END PGP SIGNATURE-----

 --7AUc2qLy4jB3hD7Z--

State-Changed-From-To: open->feedback
State-Changed-By: is@NetBSD.org
State-Changed-When: Thu, 17 Nov 2011 10:35:22 +0000
State-Changed-Why:
Your symptoms point to a multicast reception problem....
a) Is it still there in netbsd-5 or later?
b) does it work when you run tcpdump (or anything else enabling
   promiscuous mode)? This would be a confirmation.
c) with tcpdump compared to tcpdump -p, see whether the NDP multicasts
   arrive without promiscuous mode)


Responsible-Changed-From-To: kern-bug-people->is
Responsible-Changed-By: is@NetBSD.org
Responsible-Changed-When: Thu, 17 Nov 2011 10:42:37 +0000
Responsible-Changed-Why:
I'm not familiar with hme, but I can at least analyze.


State-Changed-From-To: feedback->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 23 Jan 2012 01:35:47 +0000
State-Changed-Why:
fix submitter's address


State-Changed-From-To: open->feedback
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 23 Jan 2012 01:36:08 +0000
State-Changed-Why:
and try again:

Your symptoms point to a multicast reception problem....
a) Is it still there in netbsd-5 or later?
b) does it work when you run tcpdump (or anything else enabling
   promiscuous mode)? This would be a confirmation.
c) with tcpdump compared to tcpdump -p, see whether the NDP multicasts
   arrive without promiscuous mode)


State-Changed-From-To: feedback->closed
State-Changed-By: maxv@NetBSD.org
State-Changed-When: Sat, 24 Mar 2018 08:02:23 +0000
State-Changed-Why:
Close this PR, it's not relevant anymore, the code has significantly
changed since. If you're still having this problem please submit a
new PR.


>Unformatted:
 Sources downloaded from 200609140000Z. Kernel from today.

Home	PR Database Search