SixXS::Sunset 2017-06-06

routing problem with my subnet
[de] Shadow Hawkins on Monday, 17 April 2006 10:03:47
Hello, I have installed radvd on my linux PC which gave my Win PC the following Ips: IP-Adresse. . . . . . . . . . . . : 2001:6f8:12c4:0:5d1f:d5fe:d49d:a41b IP-Adresse. . . . . . . . . . . . : 2001:6f8:12c4:0:20c:6eff:fec2:3c03 IP-Adresse. . . . . . . . . . . . : fe80::20c:6eff:fec2:3c03%4 Ping from Win to PoPv6: Pinging 2001:6f8:900:642::1 wird angepingt von 2001:6f8:12c4:0:5d1f:d5fe:d49d:a41b mit 32 Bytes Daten: Antwort von 2001:6f8:900:642::1: Bytes=32 Zeit=27ms Antwort von 2001:6f8:900:642::1: Bytes=32 Zeit=27ms Antwort von 2001:6f8:900:642::1: Bytes=32 Zeit=27ms Antwort von 2001:6f8:900:642::1: Bytes=32 Zeit=35ms tracert from Win to PoPv6 tracert -d 2001:6f8:900:642::1 Routenverfolgung zu 2001:6f8:900:642::1 über maximal 30 Abschnitte 1 1 ms <1 ms 1 ms 2001:6f8:900:642::2 2 37 ms 29 ms 29 ms 2001:6f8:900:642::1 Ablaufverfolgung beendet. So this works fine without any problems, but when I want to ping newszilla, it isn't possible: ping6 newszilla6.xs4all.nl from Win newszilla6.xs4all.nl [2001:888:0:5::119] wird angepingt von 2001:6f8:12c4:0:5d1f:d5fe:d49d:a41b mit 32 Bytes Daten: Antwort von 2001:6f8:900:642::2: Keine Route zum Ziel. (no route) Antwort von 2001:6f8:900:642::2: Keine Route zum Ziel. Antwort von 2001:6f8:900:642::2: Keine Route zum Ziel. Antwort von 2001:6f8:900:642::2: Keine Route zum Ziel. Ping-Statistik für 2001:888:0:5::119 Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100% Verlust), tracert from Win tracert -d newszilla6.xs4all.nl Routenverfolgung zu newszilla6.xs4all.nl [2001:888:0:5::119] über maximal 30 Ab schnitte: 1 Zielnetz nicht erreichbar. Ablaufverfolgung beendet. However, I can ping and tracert newszilla with my Linux PC. Here is ip -6 route 2001:6f8:900:642::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 64 2001:6f8:12c4::/48 dev eth0 metric 1024 mtu 1500 advmss 1440 hoplimit 64 fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220 hoplimit 64 fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 64 ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1220 hoplimit 1 ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 1 default via 2001:6f8:900:642::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 64 unreachable default dev lo proto none metric -1 error -101 advmss 1220 hoplimit 255 Any ideas?
routing problem with my subnet
[ch] Jeroen Massar SixXS Staff on Monday, 17 April 2006 11:29:02
2001:6f8:12c4::/48 dev eth0 metric 1024 mtu 1500 advmss 1440 hoplimit 64
Why is that still a /48 instead of the /64 I mentioned in your previous thread? Most likely because of the /48 you don't have a default route on your windows box. Router Advertisements work with /64's, not with /48's (which is 65536 /64's). Dump the routes on the Windows box too, as the box where it is going wrong is the windows box. Also you might want to check if the linux box has an address out of the /64 on it's eth0. Then try pinging that address from the Windows box. Then you should also have a default route on the Windows box, which can go over the address out of the /64 or the link-local address of eth0 on the linux box.
routing problem with my subnet
[nl] Shadow Hawkins on Monday, 17 April 2006 12:35:00
Jeroen is most definitly right here. Not using /64 for links is the most common error one can make (and will) with IPv6. But an lot of things just don't work well if you choose another prefix. I have been bitten as well when I started with IPv6 doing things the wrong way.
routing problem with my subnet
[de] Shadow Hawkins on Monday, 17 April 2006 17:18:49
Well, thanks for your help, but first it was useless. Then I restarted my Linux PC and now it works :D
routing problem with my subnet
[nl] Shadow Hawkins on Monday, 17 April 2006 12:30:16
Get the output of the following commands from your IPv6 'router': ifconfig -a netstat -nr -A inet6 cat /proc/sys/net/ipv6/conf/all/forwarding Also show the IPv6 routing info from your windows machine.

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

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