SixXS::Sunset 2017-06-06

ipv6 packet timeout problem only in LAN
[nl] Shadow Hawkins on Sunday, 09 November 2003 10:54:50
Hello, My linux 2.4.20-gentoo1.4 computer makes a pptp-connection to the Dutch ISP xs4all and also makes an ipv6-connection. The latter as follows: echo 1 > /proc/sys/net/ipv6/conf/default/forwarding echo 1 > /proc/sys/net/ipv6/conf/all/forwarding ip tunnel add unixc mode sit local 80.126.113.xxx remote 194.109.5.241 ttl 64 ip link set unixc up ip -6 route add ::/0 dev xs6all ip -6 route add 2000::/3 via 2001:888:10:c::1 ip -6 route add 2001:888:100c::/64 dev eth2 ip -6 addr add 2001:888:10:c::2/127 dev xs6all ip -6 addr add 2001:888:100c::1/64 dev eth2 ip -6 addr add 2001:888:100c::3 dev xs6all eth2 is my lan and eth1 is 10.0.0.150 for my speedtouch 510i adslmodemrouter (configged so it'll pptp itself in!). my radvd-conf is: interface eth2 { AdvSendAdvert on; AdvHomeAgentFlag off; prefix 2001:888:100c::/64 { AdvOnLink on; AdvAutonomous on; AdvRouterAddr off; }; }; There are too many timeouts happening for clients that get an ipv6-address by radvd. I think the cause lies within my lan! I could press ctrl+c and see what the output is of ping www.kame.net: --- www.kame.net ping statistics --- 5212 packets transmitted, 4403 received, +48 errors, 15% packet loss, time 5217762ms rtt min/avg/max/mdev = 357.390/383.197/1577.899/56.565 ms, pipe 2 tratz $ 15% is too much and so are 48 errors. I just don't know how to repair this, so does anyone else have the time to help me? And by the way, when I ping kame.net with my server, there isn't as much packetloss as is on my client. Mark
ipv6 packet timeout problem only in LAN
[ch] Jeroen Massar SixXS Staff on Sunday, 09 November 2003 11:09:27
ip tunnel add unixc mode sit local 80.126.113.xxx remote 194.109.5.241 ttl 64
ip link set unixc up
ip -6 route add ::/0 dev xs6all
device "unixc" and device "xs6all", shouldn't those be the same? :)
ip -6 addr add 2001:888:10:c::2/127 dev xs6all
If you go to 2.4.21 or higher watch out that the POP side will be nullrouted due to anycast.
15% is too much and so are 48 errors. I just don't know how to repair
this, so does anyone else have the time to help me? And by the way, when
I ping kame.net with my server, there isn't as much packetloss as is on
my client.
You might want to try tcpdump's and see what icmp errors are being sent...
ipv6 packet timeout problem only in LAN
[nl] Shadow Hawkins on Tuesday, 11 November 2003 16:00:21
I changed the config file correctly but just not in this post :) 15:54:37.721172 fe80::202:44ff:fe38:7b3e > ff02::1:ff38:7b3e: icmp6: neighbor sol: who has fe80::202:44ff:fe38:7b3e 15:54:38.721499 fe80::202:44ff:fe38:7b3e > ff02::1:ff4d:48f5: icmp6: neighbor sol: who has 2001:888:100c:0:250:fcff:fe4d:48f5 15:54:38.721550 2001:888:100c:0:250:fcff:fe4d:48f5 > fe80::202:44ff:fe38:7b3e: icmp6: neighbor adv: tgt is 2001:888:100c:0:250:fcff:fe4d:48f5 is some of the output tcpdump gives me. Look: --- 2001:888:100c::1 ping statistics --- 133 packets transmitted, 108 received, 18% packet loss, time 132025ms The machine being pinged is 10 meters away from the machine that pings and there are no cabling problems.
ipv6 packet timeout problem only in LAN
[ch] Jeroen Massar SixXS Staff on Tuesday, 11 November 2003 16:24:17
I guess your multicast is broken. Check the output of "ip -6 sho nei" which should reveal hosts that cannot be resolved. Try putting one of your machines drives in multicast and promisc modes, that should solve the problem partially. It could also be a switch problem btw, some don't support multicast properly unfortunatly.
ipv6 packet timeout problem only in LAN
[nl] Shadow Hawkins on Tuesday, 11 November 2003 16:32:47
my server: ip -6 n s shows: fe80::202:44ff:fe38:7b3e dev eth2 nud failed my client: fe80::202:44ff:fe38:7b3e dev eth0 lladdr 00:02:44:38:7b:3e router nud stale how can I turn on promiscuous mode?
ipv6 packet timeout problem only in LAN
[ch] Jeroen Massar SixXS Staff on Tuesday, 11 November 2003 17:13:02
nud failed & stale... just what I expected ;) "ip link set ethX multicast on" is the iproute way but you prolly want "ifconfig eth0 allmulti promisc multicast"
ipv6 packet timeout problem only in LAN
[nl] Shadow Hawkins on Tuesday, 11 November 2003 23:03:40
Yeah you're right, your suggestion helped right away :) Everything works better now, thanks for the help, Jeroen. I didn't even know there was this option. Excellent!
ipv6 packet timeout problem only in LAN
[nl] Shadow Hawkins on Thursday, 13 November 2003 00:27:15
It seems the fix lies in 'allmulti'.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker