|
neighbor solicitations not been answered...?
![[de]](/s/countries/de.gif) Shadow Hawkins on Monday, 13 October 2003 14:47:56
hi everyone,
for 2 days i got my windows box connected over my linux router to my ipv6-subnet-space. however, on saturday evening it blurred out and now i'm back without connectivity.
my guess is, that my linux box doesn't answer the neighbor solicitation messages the windows box is sending...
tcpdump -i eth1 ip6 (on linux-router - debian sid):
--
14:31:41.528519 fe80::205:5dff:fedd:4271 > ip6-allnodes: icmp6: router advertisement
14:33:05.615496 sys88.ipv6.lechte.net > orange.kame.net: icmp6: echo request
14:33:06.616507 sys88.ipv6.lechte.net > orange.kame.net: icmp6: echo request
14:33:07.617567 sys88.ipv6.lechte.net > orange.kame.net: icmp6: echo request
14:33:08.618457 sys88.ipv6.lechte.net > orange.kame.net: icmp6: echo request
14:33:10.179957 fe80::250:bfff:fe90:e720 > fe80::205:5dff:fedd:4271: icmp6: neighbor sol: who has fe80::205:5dff:fedd:4271
14:33:11.179925 fe80::250:bfff:fe90:e720 > fe80::205:5dff:fedd:4271: icmp6: neighbor sol: who has fe80::205:5dff:fedd:4271
14:33:12.179912 fe80::250:bfff:fe90:e720 > fe80::205:5dff:fedd:4271: icmp6: neighbor sol: who has fe80::205:5dff:fedd:4271
14:33:35.715931 sys88.ipv6.lechte.net > ff02::1:ffdd:4271: icmp6: neighbor sol: who has fe80::205:5dff:fedd:4271
14:33:36.679768 sys88.ipv6.lechte.net > ff02::1:ffdd:4271: icmp6: neighbor sol: who has fe80::205:5dff:fedd:4271
14:33:37.679728 sys88.ipv6.lechte.net > ff02::1:ffdd:4271: icmp6: neighbor sol: who has fe80::205:5dff:fedd:4271
--
fe80::250:bfff:fe90:e720 -> my windows machine
sys88.ipv6.lechte.net -> my windows machine, ip from subnet-space
fe80::205:5dff:fedd:4271 -> my linux-router
routing table on the linux machine:
ip -6 ro
--
2001:768:1900:82::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1280 metric10 64
2001:768:194c::1337:0/112 dev eth1 proto kernel metric 256 mtu 1280 advmss 1280 metric10 64
2001:768:194c::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1280 metric10 64
fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1500 metric10 64
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1500 metric10 64
fe80::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1280 metric10 64
ff00::/8 dev eth1 proto kernel metric 256 mtu 1500 advmss 1500 metric10 1
ff00::/8 dev eth0 proto kernel metric 256 mtu 1500 advmss 1500 metric10 1
ff00::/8 dev sixxs proto kernel metric 256 mtu 1280 advmss 1280 metric10 1
default via 2001:768:1900:82::1 dev sixxs metric 1024 mtu 1280 advmss 1280 metric10 64
--
2001:768:1900:82::/64 -> my tunnelspace
2001:768:194c::/48 -> my subnet-space
eth1 is connected to my lan, sixxs is the tunnel
configuration of my windows box:
--
C:\>ipv6 if 4
Interface 4 (site 1): Local Area Connection
uses Neighbor Discovery
link-level address: 00-50-bf-90-e7-20
preferred address 2001:768:194c::1337:254, infinite/infinite
preferred address fe80::250:bfff:fe90:e720, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ff90:e720, 1 refs, last reporter
multicast address ff02::1:ff37:254, 1 refs, last reporter
link MTU 1280 (true link MTU 1500)
current hop limit 64
reachable time 26000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
C:\>ipv6 rt
::/96 -> 2 pref 0 (lifetime infinite)
2001:768:194c::1337:0/112 -> 4 pref 1 (lifetime infinite)
::/0 -> 4/fe80::205:5dff:fedd:4271 pref 16 (lifetime 1568s)
--
i have not touched anything which is not shown (besides address-config on the linux-box, but i didn't do this the first time, i'm pretty sure it's all right.
as i already stated, it worked previously, and i can remember seeing the neighbor solicitation messages answered by my router. i don't see them answered now and i'm wondering why, resp. how to turn it on again...
any help appreciated!
sebastian
neighbor solicitations not been answered...?
2001:768:194c::1337:0/112 dev eth1 proto kernel metric 256 mtu 1280 advmss 1280 metric10 64
What is that doing there ? A /112... use /64's for links as I think I have said in another topic also.
2001:768:194c::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1280 metric10 64
If you want to correctly 'terminate' the /48, make that a /48.
Next to that it could be that your NIC in the linux box doesn't properly support multicast thus causing it to drop the solicitation messages.
neighbor solicitations not been answered...?
Shadow Hawkins on Monday, 13 October 2003 15:24:232001:768:194c::1337:0/112 dev eth1 proto kernel metric 256 mtu 1280 advmss 1280 metric10 64 What is that doing there ? A /112... use /64's for links as I think I have said in another topic also.
yes, you did. but
1) it worked before.
2) i like it. it's not like i have need for it, i can change it to /64, if you think that solves my problem. else i'd like it to be this way.
2001:768:194c::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1280 metric10 64 If you want to correctly 'terminate' the /48, make that a /48.
right. fixed that.
Next to that it could be that your NIC in the linux box doesn't properly support multicast thus causing it to drop the solicitation messages.
how can i find out about that?
neighbor solicitations not been answered...?
2) i like it. it's not like i have need for it, i can change it to /64, if you think that solves my problem. else i'd like it to be this way.
Check the RFC's and the drafts, there are a number of reasons for doing this.
Also why use a /112 and cause all these problems when you have 65535 /64's at your disposal?
> Next to that it could be that your NIC in the linux box doesn't properly support multicast thus causing it to drop the solicitation messages. how can i find out about that?
"ifconfig eth1 promisc" should do the trick as then the device will just parse all the traffic that gets send to it. Most current cards should work though, but some simply don't. It could also be a problem with a switch btw. but you are seeing the traffic apparently.
neighbor solicitations not been answered...?
Shadow Hawkins on Monday, 13 October 2003 20:47:26
Hi Sebastian,
apologize if the following is "stupid" :+ ... have you already tried a reboot of your linux box?
(wasn't it you facing a "no mem/space" problem some time ago, solved by a reboot?)
Marc
|
![[ch]](/s/countries/ch.gif)
on Monday, 13 October 2003 14:55:25
Posting is only allowed when you are