SixXS::Sunset 2017-06-06

Win XP + Destination address unreachable
[pt] Shadow Hawkins on Saturday, 06 March 2004 20:14:45
I'm trying to use SixXS through an ADSL (modem) connection and it has already worked perfectly before, but now I can't even ping anything. I'm using the heartbeat client and Windows XP + SP1 + updates, time is correctly synced using NTP and there's no router/nat device between the adsl connection and this machine. I've read all posts on this forum, but nothing worked for this case. Whenever I ping the POP (2001:b18:2000:b::1) I get:
Reply from 2001:b18:2000:b::2: Destination address unreachable.
This is my configuration:
Tunnel Information The configuration for this tunnel looks like: POP Description NFSi - Solucoes Internet, Lda. POP Location Lisboa, Portugal POP IPv4 81.92.202.9 Your Location Almada, Portugal Your IPv4 heartbeat IPv6 Prefix 2001:b18:2000:b::1/64 POP IPv6 2001:b18:2000:b::1 Your IPv6 2001:b18:2000:b::2 Last Alive 2004-03-05 22:19:29 Last Dead 2004-03-03 01:19:31 State Heartbeat netsh interface ipv6 show route: Publish Type Met Prefix Idx Gateway/Interface Name ------- -------- --- ------------------------ --- ------------------------ no Manual 1 ::/0 6 SixXS no Manual 1 2001:b18:2000:b::/64 6 SixXS netsh interface ipv6 show address: Interface 7: Local Area Connection Addr Type DAD State Valid Life Pref. Life Address --------- ---------- ---------- ---------- ----------------------------------- Link Preferred 4294967295 4294967295 fe80::202:44ff:fe67:df92 Interface 6: SixXS Addr Type DAD State Valid Life Pref. Life Address --------- ---------- ---------- ---------- ----------------------------------- Manual Preferred 4294967295 4294967295 2001:b18:2000:b::2 Link Preferred 4294967295 4294967295 fe80::6:50ac:123 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 interface: Idx Met MTU State Name --- --- ----- ------------ ----- 7 0 1500 Connected Local Area Connection 6 1 1280 Connected SixXS 3 1 1280 Connected 6to4 Tunneling Pseudo-Interface 2 1 1280 Connected Automatic Tunneling Pseudo-Interface 1 0 1500 Connected Loopback Pseudo-Interface netsh interface ipv6 show state: 6over4 State : default netsh interface ipv6 show privacy: Anonymous Address Parameters --------------------------------------------- Use Anonymous Addresses : disabled Duplicate Address Detection Attempts: 5 Maximum Valid Lifetime : 604800 seconds Maximum Preferred Lifetime : 86400 seconds Regenerate Time : 5 seconds Maximum Random Time : 600 seconds Random Time : 167 seconds netsh interface ipv6 show destinationcache: Interface 6: SixXS PMTU Destination Address Next Hop Address ---- ---------------------------------- ---------------------------------- 1280 2001:b18:2000:b::2 2001:b18:2000:b::2 1280 3ffe:400:280::1 3ffe:400:280::1 1280 2001:b18:2000:b::1 2001:b18:2000:b::1 1280 2001:240:0:1::d28a:575c 2001:240:0:1::d28a:575c 1280 2001:760:400:1:210:4bff:fe35:f2fa 2001:760:400:1:210:4bff:fe35:f2fa 1280 2001:770:18:2::1:2 2001:770:18:2::1:2 1280 2001:b18:2000::1 2001:b18:2000::1 Interface 3: 6to4 Tunneling Pseudo-Interface PMTU Destination Address Next Hop Address ---- ---------------------------------- ---------------------------------- 1280 2002:c058:6301::c058:6301 2002:c058:6301::c058:6301 1280 2002:836b:213c::836b:213c 2002:836b:213c::836b:213c netsh interface ipv6 show neighbors: Interface 7: Local Area Connection Internet Address Physical Address Type -------------------------------------------- ----------------- ----------- fe80::202:44ff:fe67:df92 00-02-44-67-df-92 Permanent Interface 6: SixXS Internet Address Physical Address Type -------------------------------------------- ----------------- ----------- 2001:b18:2000:b::2 80.172.1.35 Permanent 3ffe:400:280::1 81.92.202.9 Permanent 2001:b18:2000:b::1 81.92.202.9 Permanent 2001:240:0:1::d28a:575c 81.92.202.9 Permanent 2001:760:400:1:210:4bff:fe35:f2fa 81.92.202.9 Permanent 2001:770:18:2::1:2 81.92.202.9 Permanent 2001:b18:2000::1 81.92.202.9 Permanent fe80::6:50ac:123 80.172.1.35 Permanent Interface 3: 6to4 Tunneling Pseudo-Interface Internet Address Physical Address Type -------------------------------------------- ----------------- ----------- 2002:c058:6301::c058:6301 192.88.99.1 Permanent 2002:836b:213c::836b:213c 131.107.33.60 Permanent 2002:50ac:123::50ac:123 80.172.1.35 Permanent 2002:836b:213c:1:e0:8f08:f020:8 131.107.33.60 Permanent Interface 2: Automatic Tunneling Pseudo-Interface Internet Address Physical Address Type -------------------------------------------- ----------------- ----------- fe80::5efe:192.168.0.1 192.168.0.1 Permanent fe80::5efe:80.172.1.35 80.172.1.35 Permanent Interface 1: Loopback Pseudo-Interface Internet Address Physical Address Type -------------------------------------------- ----------------- ----------- fe80::1 Permanent ::1 Permanent ipv6 if: Interface 7: Ethernet: Local Area Connection uses Neighbor Discovery uses Router Discovery link-layer address: 00-02-44-67-df-92 preferred link-local fe80::202:44ff:fe67:df92, 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:ff67:df92, 1 refs, last reporter link MTU 1500 (true link MTU 1500) current hop limit 128 reachable time 40500ms (base 30000ms) retransmission interval 1000ms DAD transmits 1 Interface 6: Configured Tunnel Interface does not use Neighbor Discovery does not use Router Discovery routing preference 1 link-layer address: 80.172.1.35 remote link-layer address: 81.92.202.9 preferred global 2001:b18:2000:b::2, life infinite (manual) preferred link-local fe80::6:50ac:123, life infinite link MTU 1280 (true link MTU 65515) current hop limit 128 reachable time 16000ms (base 30000ms) retransmission interval 1000ms DAD transmits 1 Interface 3: 6to4 Tunneling Pseudo-Interface does not use Neighbor Discovery does not use Router Discovery forwards packets routing preference 1 link MTU 1280 (true link MTU 65515) current hop limit 128 reachable time 26000ms (base 30000ms) retransmission interval 1000ms DAD transmits 0 Interface 2: Automatic Tunneling Pseudo-Interface does not use Neighbor Discovery does not use Router Discovery forwards packets routing preference 1 EUI-64 embedded IPv4 address: 0.0.0.0 router link-layer address: 0.0.0.0 link MTU 1280 (true link MTU 65515) current hop limit 128 reachable time 38500ms (base 30000ms) retransmission interval 1000ms DAD transmits 0 Interface 1: Loopback Pseudo-Interface does not use Neighbor Discovery does not use Router Discovery link-layer address: preferred link-local ::1, life infinite preferred link-local fe80::1, life infinite link MTU 1500 (true link MTU 4294967295) current hop limit 128 reachable time 21500ms (base 30000ms) retransmission interval 1000ms DAD transmits 0
I tried using ethereal and windump/tcpdump, but they can't capture dial-up interfaces, they only allow me to capture my LAN interface. Is there anything wrong with my config? Thanks.
Win XP + Destination address unreachable
[ch] Jeroen Massar SixXS Staff on Saturday, 06 March 2004 20:25:55
"80.172.1.35: Time is 132 seconds off for 2001:b18:2000:b::2" It is off by 132 seconds = 2 minutes and 12 seconds. Are you sure your clock is synced?
Win XP + Destination address unreachable
[pt] Shadow Hawkins on Saturday, 06 March 2004 20:41:28
Well, I'm sure I had manually synced with time.windows.com, and just to be sure I also had synced with my linux box, which was running ntpd with 15 configured peers.. Anyway I synced again now with various ntp servers and the tunnel's working (for) now. :? Thanks ;)
Win XP + Destination address unreachable
[ch] Jeroen Massar SixXS Staff on Saturday, 06 March 2004 20:44:20
Number of peers does not matter, it's the quality of the NTP peer that does though. Also, most unix boxes don't allow big clock jumps thus if it is off for quite a big number it will only slowly change the time. Best thing to do is using your ISP's ntp servers, that is when they are stratum 1 or 2.
Win XP + Destination address unreachable
[pt] Shadow Hawkins on Saturday, 06 March 2004 20:57:25
I agree, but my ISP doesn't have an NTP server, and I don't really know how to measure quality apart from their stratum level, so I just chose a bunch of servers which had the minimum latency from my connection from a list of stratum 1 and 2 ntp servers. I suppose ntpd then figures out the best servers, because it also measures latency from all peers in real-time. I also knew about the big clock jumps, that's why I monitor the ntpd status with ntpq ;)

Please note Posting is only allowed when you are logged in.
Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker