winXP setup...
Shadow Hawkins on Saturday, 31 January 2004 04:05:31
For some reason I have problem to make heartbit working.
I did:
WinXP SP1 fresh install + all MS patches
netsh interface ipv6 reset
netsh interface ipv6 6to4 set state disabled disabled
netsh interface ipv6 set privacy disabled
direct connect to cable modem (no router)
time sync
Then I ran Heartbeat, so far so good, but only ping6 newszilla6.xs4all.nl works!?!
Others not. Any help would be appreciated, I just don't know what to do next.
D:\admin>ping6 newszilla6.xs4all.nl
Pinging newszilla6.xs4all.nl [2001:888:0:4::119]
from 3ffe:4005:1000:7::2 with 32 bytes of data:
Reply from 2001:888:0:4::119: bytes=32 time=102ms
Reply from 2001:888:0:4::119: bytes=32 time=108ms
Reply from 2001:888:0:4::119: bytes=32 time=103ms
Reply from 2001:888:0:4::119: bytes=32 time=99ms
Ping statistics for 2001:888:0:4::119:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 99ms, Maximum = 108ms, Average = 103ms
D:\admin>ping6 www.6bone.net
Pinging 6bone.net [3ffe:b00:c18:1::10]
from 3ffe:4005:1000:7::2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 3ffe:b00:c18:1::10:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
D:\admin>ping6 www.kame.net
Pinging orange.kame.net [2001:200:0:8002:203:47ff:fea5:3085]
from 3ffe:4005:1000:7::2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2001:200:0:8002:203:47ff:fea5:3085:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
D:\admin>netsh interface ipv6 show route
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
no Manual 1 3ffe:4005:1000:7::/64 6 SixXS
no Manual 1 ::/0 6 SixXS
yes Manual 1102 ::/0 3 2002:c058:6301::c058:6301
yes Manual 1091 ::/0 3 2002:836b:213c:1:e0:8f08:f020:8
yes Manual 1001 2002::/16 3 6to4 Tunneling Pseudo-Interface
D:\admin>netsh interface ipv6 show address
Interface 6: SixXS
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ---------- ---------- -----------------------------------
Manual Preferred 4294967295 4294967295 3ffe:4005:1000:7::2
Link Preferred 4294967295 4294967295 fe80::6:4516:fcbe
Interface 4: 3com
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ---------- ---------- -----------------------------------
Link Preferred 4294967295 4294967295 fe80::201:3ff:fe25:613
Interface 3: 6to4 Tunneling Pseudo-Interface
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ---------- ---------- -----------------------------------
Other Preferred 4294967295 4294967295 2002:4516:fcbe::4516:fcbe
Interface 2: Automatic Tunneling Pseudo-Interface
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ---------- ---------- -----------------------------------
Link Preferred 4294967295 4294967295 fe80::5efe:69.22.252.190
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
D:\admin>netsh interface ipv6 show interface
Idx Met MTU State Name
--- --- ----- ------------ -----
6 1 1280 Connected SixXS
4 0 1500 Connected 3com
3 1 1280 Connected 6to4 Tunneling Pseudo-Interface
2 1 1280 Connected Automatic Tunneling Pseudo-Interface
1 0 1500 Connected Loopback Pseudo-Interface
D:\admin>netsh interface ipv6 show state
6over4 State : default
D:\Documents and Settings\admin>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
D:\admin>netsh interface ipv6 show destinationcache
Interface 6: SixXS
PMTU Destination Address Next Hop Address
---- ---------------------------------- ----------------------------------
1280 3ffe:4005:1000:7::1 3ffe:4005:1000:7::1
1280 2001:200:0:8002:203:47ff:fea5:3085 2001:200:0:8002:203:47ff:fea5:3085
1280 2001:888:0:4::119 2001:888:0:4::119
1280 3ffe:b00:c18:1::10 3ffe:b00:c18:1::10
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
D:\admin>netsh interface ipv6 show neighbors
Interface 6: SixXS
Internet Address Physical Address Type
-------------------------------------------- ----------------- -----------
3ffe:4005:1000:7::1 62.24.229.120 Permanent
2001:200:0:8002:203:47ff:fea5:3085 62.24.229.120 Permanent
2001:888:0:4::119 62.24.229.120 Permanent
3ffe:b00:c18:1::10 62.24.229.120 Permanent
fe80::6:4516:fcbe 69.22.252.190 Permanent
3ffe:4005:1000:7::2 69.22.252.190 Permanent
Interface 4: 3com
Internet Address Physical Address Type
-------------------------------------------- ----------------- -----------
fe80::201:3ff:fe25:613 00-01-03-25-06-13 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:4516:fcbe::4516:fcbe 127.0.0.1 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:69.22.252.190 127.0.0.1 Permanent
Interface 1: Loopback Pseudo-Interface
Internet Address Physical Address Type
-------------------------------------------- ----------------- -----------
fe80::1 Permanent
::1 Permanent
D:\admin>ipv6 if
Interface 6: Configured Tunnel Interface
{EA902F3D-C960-C8BA-4FEA-5149B2C148A8}
does not use Neighbor Discovery
does not use Router Discovery
routing preference 1
link-layer address: 69.22.252.190
remote link-layer address: 62.24.229.120
preferred global 3ffe:4005:1000:7::2, life infinite (manual)
preferred link-local fe80::6:4516:fcbe, life infinite
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 33000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 4: Ethernet: 3com
{CD9C898D-64CD-4334-AB87-F227CA66E9D6}
uses Neighbor Discovery
uses Router Discovery
link-layer address: 00-01-03-25-06-13
preferred link-local fe80::201:3ff:fe25:613, 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:ff25:613, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 26500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 3: 6to4 Tunneling Pseudo-Interface
{A995346E-9F3E-2EDB-47D1-9CC7BA01CD73}
does not use Neighbor Discovery
does not use Router Discovery
routing preference 1
preferred global 2002:4516:fcbe::4516:fcbe, life infinite
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 15500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 0
Interface 2: Automatic Tunneling Pseudo-Interface
{48FCE3FC-EC30-E50E-F1A7-71172AEEE3AE}
does not use Neighbor Discovery
does not use Router Discovery
routing preference 1
EUI-64 embedded IPv4 address: 0.0.0.0
router link-layer address: 0.0.0.0
preferred link-local fe80::5efe:69.22.252.190, life infinite
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 42500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 0
Interface 1: Loopback Pseudo-Interface
{6BD113CC-5EC2-7638-B953-0B889DA72014}
winXP setup...
Jeroen Massar on Saturday, 31 January 2004 12:34:18 D:\admin>netsh interface ipv6 show route Publish Type Met Prefix Idx Gateway/Interface Name ------- -------- --- ------------------------ --- ------------------------ no Manual 1 3ffe:4005:1000:7::/64 6 SixXS no Manual 1 ::/0 6 SixXS yes Manual 1102 ::/0 3 2002:c058:6301::c058:6301 yes Manual 1091 ::/0 3 2002:836b:213c:1:e0:8f08:f020:8 yes Manual 1001 2002::/16 3 6to4 Tunneling Pseudo-Interface
Seeing this I see you still have 6to4 enabled, as you didn't do any traceroute's (tracert6 in Windows) we can't really see what path it really took, though according to the above list and metrics it should use the tunnel.
A traceroute6 along with a timestamp would be more logical. The neighbor cache does indicate that it goes over the tunnel.
See Latency, select the gblon01 POP and then IPv6 well know destinations and you will see that it is reachable from the POP.
winXP setup...
Shadow Hawkins on Saturday, 31 January 2004 16:44:59
looks like I can't disable 6to4, or I'm typing wrong command :?
C:\admin>netsh interface ipv6 6to4 set state disabled disabled
Ok.
C:\admin>netsh interface ipv6 show route
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
no Manual 1 3ffe:4005:1000:7::/64 6 SixXS
no Manual 1 ::/0 6 SixXS
yes Manual 1091 ::/0 3 2002:836b:213c:1:e0:8f08:f020:8
yes Manual 1091 ::/0 3 2002:c058:6301::c058:6301
yes Manual 1001 2002::/16 3 6to4 Tunneling Pseudo-Interface
C:\admin>tracert6 newszilla6.xs4all.nl
Tracing route to newszilla6.xs4all.nl [2001:888:0:4::119]
from 3ffe:4005:1000:7::2 over a maximum of 30 hops:
1 91 ms 92 ms 94 ms gw-8.lon-01.gb.sixxs.net [3ffe:4005:1000:7::1]
2 91 ms 94 ms 93 ms fa-0-0-IPv6-omnipotent.thn.kewlio.net.uk [3ffe:4005:fefe::ffff]
3 108 ms 109 ms 100 ms 2001:7f8:5::3d57:1
4 101 ms 102 ms 131 ms ams-ix.sara.xs4all.net [2001:7f8:1::a500:3265:1]
5 102 ms 102 ms 101 ms 2001:888:0:1105::1
6 102 ms 108 ms 101 ms newszilla6.xs4all.nl [2001:888:0:4::119]
Trace complete.
C:\admin>tracert6 www.kame.net
Tracing route to orange.kame.net [2001:200:0:8002:203:47ff:fea5:3085]
from 3ffe:4005:1000:7::2 over a maximum of 30 hops:
1 92 ms 92 ms 93 ms gw-8.lon-01.gb.sixxs.net [3ffe:4005:1000:7::1]
2 92 ms 92 ms 94 ms dc-0-IPv6-numen.sov.kewlio.net.uk [3ffe:4005:fefe::5555]
3 * * * Request timed out.
4 * * * Request timed out.
5
winXP setup...
Jeroen Massar on Saturday, 31 January 2004 17:42:59 yes Manual 1091 ::/0 3 2002:836b:213c:1:e0:8f08:f020:8 yes Manual 1091 ::/0 3 2002:c058:6301::c058:6301 yes Manual 1001 2002::/16 3 6to4 Tunneling Pseudo-Interface
These routes are installed manually, thus you will have to do it yourself. Easy way out "ipv6 reset", you will need to redisable the privacy settings etc then though. These are now easy clickable options in the new SACC client btw.
Tracing route to orange.kame.net [2001:200:0:8002:203:47ff:fea5:3085] from 3ffe:4005:1000:7::2 over a maximum of 30 hops: 1 92 ms 92 ms 93 ms gw-8.lon-01.gb.sixxs.net [3ffe:4005:1000:7::1] 2 92 ms 92 ms 94 ms dc-0-IPv6-numen.sov.kewlio.net.uk [3ffe:4005:fefe::5555] 3 * * * Request timed out. 4 * * * Request timed out. 5
There is apparently a transit peering problem, Kewlio is on busy fixing it.
winXP setup...
Shadow Hawkins on Sunday, 01 February 2004 07:35:40
O-)
Posting is only allowed when you are logged in. |