SixXS::Sunset 2017-06-06

Troubles routing subnet to windows XP
[nl] Shadow Hawkins on Friday, 19 December 2003 22:36:36
I am trying to route my ipv6 subnet to my windows XP machines. The router is a debian machine with RADVD configured. I do get an ipv6 address on my windows machine, but routing does not seem to work. (cant ping any ipv6 address) Can somebody please tell me what I'm doing wrong? :) tnx. radvd.conf: --- interface eth1 { AdvSendAdvert on; prefix 2001:838:37b:1::/64 { AdvOnLink on; }; }; --- --- netsh interface ipv6>show address Interface 4: Local Area Connection Addr Type DAD State Valid Life Pref. Life Address --------- ---------- ---------- ---------- ----------------------------------- Anonymous Preferred 601826 83259 2001:838:37b:1:1d77:2c7c:a6c1:4efd Public Preferred 2591800 604600 2001:838:37b:1:20c:6eff:fe45:afa1 Link Preferred 4294967295 4294967295 fe80::20c:6eff:fe45:afa1 Interface 1: Loopback Pseudo-Interface Addr Type DAD State Valid Life Pref. Life Address --------- ---------- ---------- ---------- ----------------------------------- Loopback Preferred 4294967295 4294967295 ::1 Link Preferred 4294967295 4294967295 fe80::1 ------------------------------------------------------------------------------- netsh interface ipv6>show route Publish Type Met Prefix Idx Gateway/Interface Name ------- -------- --- ------------------------ --- ------------------------ no Autoconf 8 2001:838:37b:1::/64 4 Local Area Connection no Autoconf 256 ::/0 4 fe80::201:2ff:fe39:2a3c
Troubles routing subnet to windows XP
[ch] Jeroen Massar SixXS Staff on Friday, 19 December 2003 23:04:16
Can your XP box do: C:\ ping6 fe80::201:2ff:fe39:2a3c%4 And don't forget to turn on forwarding on your router ;)
Troubles routing subnet to windows XP
[nl] Shadow Hawkins on Friday, 19 December 2003 23:12:02
forwarding is turned on ofcourse :) pinging fe80::201:2ff:fe39:2a3c%4 works. pinging 2001:838:37b:1:1d77:2c7c:a6c1:4efd works. pinging 2001:838:37b:1:20c:6eff:fe45:afa1 works. Interface 4: Ethernet: Local Area Connection {2C735B08-D297-4AD8-ADB8-632FA2D267B7} uses Neighbor Discovery uses Router Discovery link-layer address: 00-0c-6e-45-af-a1 preferred global 2001:838:37b:1:1d77:2c7c:a6c1:4efd, life 6d22h33m49s/22h31m 2s (anonymous) preferred global 2001:838:37b:1:20c:6eff:fe45:afa1, life 29d23h59m26s/6d23h5 9m26s (public) preferred link-local fe80::20c:6eff:fe45:afa1, life infinite multicast interface-local ff01::1, 1 refs, not reportable multicast link-local ff02::1, 1 refs, not reportable multicast link-local ff02::1:ff45:afa1, 2 refs, last reporter multicast link-local ff02::1:ffc1:4efd, 1 refs, last reporter link MTU 1500 (true link MTU 1500) current hop limit 64 reachable time 37000ms (base 30000ms) retransmission interval 1000ms DAD transmits 1
Troubles routing subnet to windows XP
[ch] Jeroen Massar SixXS Staff on Saturday, 20 December 2003 00:02:44
2001:838:37b:1:1d77:2c7c:a6c1:4efd is your 'anonymous' address. "netsh int ipv6 set privacy disabled" should get rid of that one, I think it is the most annoying feature of IPv6 ;) As you can ping your default gateway, you probably peeped up on the route back, thus the gateway still needs a route to your subnet. Did you also configure an address out of the same /64 on your router? Next up to test after that: traceroute6's from the internal host, traceroute6 from router and from external host. You should also check your neighbour caches "netsh int ipv6 show neigh"
Troubles routing subnet to windows XP
[nl] Shadow Hawkins on Saturday, 20 December 2003 14:50:27
ah ok :) that fixed it :)) thanks!

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

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