|
Ticket ID: SIXXS #542973 Ticket Status: Resolved PoP: simbx01 - Amis (Maribor)
weird Windows problem (can't ping POP)
![[ro]](/s/countries/ro.gif) Shadow Hawkins on Saturday, 30 June 2007 18:46:32
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
Hi, my user-id is GIS1-SIXXS and I seem to be having problems using AICCU on Windows XP. Here are some outputs:
Windows IP Configuration
Host Name . . . . . . . . . . . . : darling
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
PPP adapter RDS:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 79.113.226.119
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 79.113.226.119
DNS Servers . . . . . . . . . . . : 208.67.222.222
193.231.249.1
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter aiccu:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Configured Tunnel Interface
Physical Address. . . . . . . . . : 4F-71-E2-77
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 2001:15c0:65ff:f9::2
IP Address. . . . . . . . . . . . : fe80::6:4f71:e277%6
Default Gateway . . . . . . . . . : 2001:15c0:65ff:f9::1
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
Physical Address. . . . . . . . . : 00-0B-6A-9E-E9-6C
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::20b:6aff:fe9e:e96c%4
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 4F-71-E2-77
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:79.113.226.119%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled
Pinging 2001:15c0:65ff:f9::2 with 32 bytes of data:
Reply from 2001:15c0:65ff:f9::2: time<1ms
Reply from 2001:15c0:65ff:f9::2: time<1ms
Reply from 2001:15c0:65ff:f9::2: time<1ms
Reply from 2001:15c0:65ff:f9::2: time<1ms
Ping statistics for 2001:15c0:65ff:f9::2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging 2001:15c0:65ff:f9::1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2001:15c0:65ff:f9::1:
Packets: Sent = 3, Received = 0, Lost = 3 (100% loss),
Control-C
Tracing route to gold.inlimbo.org [212.18.63.73]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 10.0.0.1
2 2 ms 1 ms 1 ms 86-123-119-9.rdsnet.ro [86.123.119.9]
3 1 ms 1 ms 1 ms 213-154-113-18.rdsnet.ro [213.154.113.18]
4 2 ms 1 ms 1 ms 213-154-113-21.rdsnet.ro [213.154.113.21]
5 * 118 ms 212 ms 213-154-124-145.rdsnet.ro [213.154.124.145]
6 26 ms 26 ms 26 ms xr01.frankfurt.rdsnet.ro [213.154.124.10]
7 25 ms 25 ms 26 ms decix-rds-1-ro.fra.seabone.net [195.22.211.229]
8 42 ms 42 ms 42 ms customer-side-telekom-aus-4-at-vie8.vie.seabone.net [195.22.215.46]
9 42 ms 43 ms * 195.3.70.197
10 42 ms 42 ms 42 ms 195.3.70.70
11 50 ms 51 ms 51 ms 80.120.176.182
12 53 ms 50 ms 51 ms maribor3-ge-2-8.amis.net [212.18.35.74]
13 50 ms 50 ms 50 ms gold.inlimbo.org [212.18.63.73]
Trace complete.
What happens is that the tunnel seems to establish ok. I can ping the local v6 address, but not the remote (POP) address. Windows firewall is disabled and no other security software is running. I'm not using NAT.
The "weird" in the subject is because of what I'm seeing in Wireshark. When I issue the ping command in XP, although I get a "Request timed out", I see the echo reply displayed in Wireshark. I've also seen echo requests initiated by the POP, but there are no replies from my computer. Traceroute to the v4 POP IP works. Traceroute to www.kame.net doesn't, although the name is resolved correctly:
Tracing route to www.kame.net [2001:200:0:8002:203:47ff:fea5:3085]
over a maximum of 30 hops:
1 * * * Request timed out.
2 ^C
At the TCP level, SIXXS says I'm connected using a v4 IP. Wireshark shows that the 3-way handshake is only partially completed:
1 0.000000 2001:15c0:65ff:f9::2 -> 2001:838:1:1:210:dcff:fe20:7c7c TCP 1026 > http [SYN] Seq=0 Len=0 MSS=1220
2 0.095703 2001:838:1:1:210:dcff:fe20:7c7c -> 2001:15c0:65ff:f9::2 TCP http > 1026 [SYN, ACK] Seq=0 Ack=1 Win=5760 Len=0 MSS=1440
3 2.938477 2001:15c0:65ff:f9::2 -> 2001:838:1:1:210:dcff:fe20:7c7c TCP 1026 > http [SYN] Seq=0 Len=0 MSS=1220
4 3.033203 2001:838:1:1:210:dcff:fe20:7c7c -> 2001:15c0:65ff:f9::2 TCP http > 1026 [SYN, ACK] Seq=0 Ack=1 Win=5760 Len=0 MSS=1440
5 4.493164 2001:838:1:1:210:dcff:fe20:7c7c -> 2001:15c0:65ff:f9::2 TCP http > 1026 [SYN, ACK] Seq=0 Ack=1 Win=5760 Len=0 MSS=1440
6 8.973633 2001:15c0:65ff:f9::2 -> 2001:838:1:1:210:dcff:fe20:7c7c TCP 1026 > http [SYN] Seq=0 Len=0 MSS=1220
7 9.068360 2001:838:1:1:210:dcff:fe20:7c7c -> 2001:15c0:65ff:f9::2 TCP http > 1026 [SYN, ACK] Seq=0 Ack=1 Win=5760 Len=0 MSS=1440
8 10.495117 2001:838:1:1:210:dcff:fe20:7c7c -> 2001:15c0:65ff:f9::2 TCP http > 1026 [SYN, ACK] Seq=0 Ack=1 Win=5760 Len=0 MSS=1440
9 21.316407 2001:15c0:65ff:f9::2 -> 2001:838:1:1:210:dcff:fe20:7c7c TCP 1027 > http [SYN] Seq=0 Len=0 MSS=1220
10 21.415039 2001:838:1:1:210:dcff:fe20:7c7c -> 2001:15c0:65ff:f9::2 TCP http > 1027 [SYN, ACK] Seq=0 Ack=1 Win=5760 Len=0 MSS=1440
11 24.262696 2001:15c0:65ff:f9::2 -> 2001:838:1:1:210:dcff:fe20:7c7c TCP 1027 > http [SYN] Seq=0 Len=0 MSS=1220
12 24.356446 2001:838:1:1:210:dcff:fe20:7c7c -> 2001:15c0:65ff:f9::2 TCP http > 1027 [SYN, ACK] Seq=0 Ack=1 Win=5760 Len=0 MSS=1440
13 25.700196 2001:838:1:1:210:dcff:fe20:7c7c -> 2001:15c0:65ff:f9::2 TCP http > 1027 [SYN, ACK] Seq=0 Ack=1 Win=5760 Len=0 MSS=1440
14 30.297852 2001:15c0:65ff:f9::2 -> 2001:838:1:1:210:dcff:fe20:7c7c TCP 1027 > http [SYN] Seq=0 Len=0 MSS=1220
15 30.392578 2001:838:1:1:210:dcff:fe20:7c7c -> 2001:15c0:65ff:f9::2 TCP http > 1027 [SYN, ACK] Seq=0 Ack=1 Win=5760 Len=0 MSS=1440
16 31.693360 2001:838:1:1:210:dcff:fe20:7c7c -> 2001:15c0:65ff:f9::2 TCP http > 1027 [SYN, ACK] Seq=0 Ack=1 Win=5760 Len=0 MSS=1440
Heartbeat UDP packets sent from my PC don't get a response (I don't know if they should, but I thought it's worth mentioning).
I'm using the latest version of AICCU from SIXXS.
In the end, I want to say that the first time I connected using AICCU, it worked fine. The behaviour described above started about a week or so ago.
P.S.: I put "Windows" in the subject because things work fine from Linux. More precisely, I'm using Ubuntu 7.04 and AICCU compiled from source and all 8 tests from "./aiccu test" are passed, I can connect with "aiccu start" and SIXXS says I'm connected with an IPv6 address.
State change: invalid
The state of this ticket has been changed to invalid
weird Windows problem (can't ping POP)
You still miss:
- routing table
- interface table
Use netsh for those, not ipconfig which doesn't contain the needed information.
Also it seems you have an RFC1918 address in the traceroute.
Trying to do TCP when you can't even ping6 the remote endpoint is a bit futile, check the rest first.
weird Windows problem (can't ping POP)
Shadow Hawkins on Sunday, 01 July 2007 15:08:22
C:\Documents and Settings\user>netsh interface ipv6 show address
Querying active state...
Interface 7: aiccu
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Manual Preferred infinite infinite 2001:15c0:65ff:f9::2
Link Preferred infinite infinite fe80::7:4f71:e637
Interface 5: Teredo Tunneling Pseudo-Interface
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Link Preferred infinite infinite fe80::5445:5245:444f
Interface 4: Local Area Connection
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Link Preferred infinite infinite fe80::20b:6aff:fe9e:e96c
Interface 2: Automatic Tunneling Pseudo-Interface
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Link Preferred infinite infinite fe80::5efe:79.113.230.55
Interface 1: Loopback Pseudo-Interface
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Loopback Preferred infinite infinite ::1
Link Preferred infinite infinite fe80::1
C:\Documents and Settings\user>netsh interface ipv6 show route
Querying active state...
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- ---- ------------------------ --- ---------------------
yes Manual 1 ::/0 7 2001:15c0:65ff:f9::1
no Manual 1 2001:15c0:65ff:f9::/64 7 aiccu
C:\Documents and Settings\user>netsh interface ipv6 show interface
Querying active state...
Idx Met MTU State Name
--- ---- ----- ------------ -----
7 1 1280 Connected aiccu
5 2 1280 Disconnected Teredo Tunneling Pseudo-Interface
4 0 1500 Connected Local Area Connection
3 1 1280 Disconnected 6to4 Pseudo-Interface
2 1 1280 Disconnected Automatic Tunneling Pseudo-Interface
1 0 1500 Connected Loopback Pseudo-Interface
I use PPPoE to connect to my ISP and 10.0.0.1 is the ISP's POP IP.
weird Windows problem (can't ping POP)
IP Address. . . . . . . . . . . . : 79.113.226.119
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 79.113.226.119
That looks quite odd, the gateway is your own machine and it is a /32? Strange.
Based on the information provided though I have no idea what further could be wrong. In theory, it should work.
weird Windows problem (can't ping POP)
Shadow Hawkins on Tuesday, 03 July 2007 21:36:29
Problem solved by reinstalling the NIC driver. I should have done that before posting, but it only came to mind after I got the tunnel working on another Windows XP from a different partition.
Thanks for your time.
State change: resolved
The state of this ticket has been changed to resolved
|
![[ch]](/s/countries/ch.gif)
on Sunday, 01 July 2007 01:26:11
Posting is only allowed when you are