|
Ticket ID: SIXXS #829761 Ticket Status: User PoP: deham01 - Easynet (Hamburg)
My tunnel doesn't work
![[de]](/s/countries/de.gif) Shadow Hawkins on Tuesday, 21 October 2008 08:42:14
Since about 1:30am, 2008-10-17 my ayiya tunnel is down. I can ping the endpoint 212.224.0.188 but traceroute gives me that I get no UDP packets back, as you can see at this (non verbose) tcpdump:
16:57:06.891608 IP 192.168.9.254.60646 > bombadil.deadset.org.domain: 44789+ A? tic.sixxs.net. (31)
16:57:06.892207 IP bombadil.deadset.org.domain > 192.168.9.254.60646: 44789 3/3/0 CNAME tic.m.sixxs.net.,[|domain]
16:57:06.894266 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: S 1131478960:1131478960(0) win 5840 <mss 1460,sackOK,timestamp 4294912107 0,nop,wscale 6>
16:57:06.915970 IP broker04.ams.nl.sixxs.net.3874 > 192.168.9.254.35099: S 1738299784:1738299784(0) ack 1131478961 win 5792 <mss 1460,sackOK,timestamp 1058630117 4294912107,nop,wscale 10>
16:57:06.916514 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: . ack 1 win 92 <nop,nop,timestamp 4294912112 1058630117>
16:57:07.098830 IP broker04.ams.nl.sixxs.net.3874 > 192.168.9.254.35099: P 1:70(69) ack 1 win 6 <nop,nop,timestamp 1058630163 4294912112>
16:57:07.099497 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: . ack 70 win 92 <nop,nop,timestamp 4294912158 1058630163>
16:57:07.099595 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: P 1:71(70) ack 70 win 92 <nop,nop,timestamp 4294912158 1058630163>
16:57:07.123918 IP broker04.ams.nl.sixxs.net.3874 > 192.168.9.254.35099: . ack 71 win 6 <nop,nop,timestamp 1058630169 4294912158>
16:57:07.133083 IP broker04.ams.nl.sixxs.net.3874 > 192.168.9.254.35099: P 70:99(29) ack 71 win 6 <nop,nop,timestamp 1058630172 4294912158>
16:57:07.133588 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: P 71:84(13) ack 99 win 92 <nop,nop,timestamp 4294912167 1058630172>
16:57:07.161407 IP broker04.ams.nl.sixxs.net.3874 > 192.168.9.254.35099: P 99:114(15) ack 84 win 6 <nop,nop,timestamp 1058630179 4294912167>
16:57:07.161945 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: P 84:93(9) ack 114 win 92 <nop,nop,timestamp 4294912174 1058630179>
16:57:07.186423 IP broker04.ams.nl.sixxs.net.3874 > 192.168.9.254.35099: P 114:156(42) ack 93 win 6 <nop,nop,timestamp 1058630185 4294912174>
16:57:07.186957 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: P 93:113(20) ack 156 win 92 <nop,nop,timestamp 4294912180 1058630185>
16:57:07.212014 IP broker04.ams.nl.sixxs.net.3874 > 192.168.9.254.35099: P 156:204(48) ack 113 win 6 <nop,nop,timestamp 1058630191 4294912180>
16:57:07.212716 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: P 113:127(14) ack 204 win 92 <nop,nop,timestamp 4294912186 1058630191>
16:57:07.241504 IP broker04.ams.nl.sixxs.net.3874 > 192.168.9.254.35099: P 204:241(37) ack 127 win 6 <nop,nop,timestamp 1058630199 4294912186>
16:57:07.242156 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: P 127:177(50) ack 241 win 92 <nop,nop,timestamp 4294912194 1058630199>
16:57:07.276275 IP broker04.ams.nl.sixxs.net.3874 > 192.168.9.254.35099: P 241:328(87) ack 177 win 6 <nop,nop,timestamp 1058630208 4294912194>
16:57:07.276991 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: P 177:196(19) ack 328 win 92 <nop,nop,timestamp 4294912202 1058630208>
16:57:07.308332 IP broker04.ams.nl.sixxs.net.3874 > 192.168.9.254.35099: P 328:370(42) ack 196 win 6 <nop,nop,timestamp 1058630216 4294912202>
16:57:07.345454 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: . ack 370 win 92 <nop,nop,timestamp 4294912220 1058630216>
16:57:07.351026 IP broker04.ams.nl.sixxs.net.3874 > 192.168.9.254.35099: P 370:696(326) ack 196 win 6 <nop,nop,timestamp 1058630226 4294912202>
16:57:07.351585 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: . ack 696 win 108 <nop,nop,timestamp 4294912221 1058630226>
16:57:07.352923 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: P 196:224(28) ack 696 win 108 <nop,nop,timestamp 4294912221 1058630226>
16:57:07.352978 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: F 224:224(0) ack 696 win 108 <nop,nop,timestamp 4294912221 1058630226>
16:57:07.374914 IP broker04.ams.nl.sixxs.net.3874 > 192.168.9.254.35099: F 696:696(0) ack 225 win 6 <nop,nop,timestamp 1058630232 4294912221>
16:57:07.377607 IP 192.168.9.254.35099 > broker04.ams.nl.sixxs.net.3874: . ack 697 win 108 <nop,nop,timestamp 4294912228 1058630232>
16:57:07.528425 IP 192.168.9.254.45104 > deham01.sixxs.net.5072: UDP, length 92
16:57:07.607430 IP 192.168.9.254.45104 > deham01.sixxs.net.5072: UDP, length 44
16:57:07.608707 IP 192.168.9.254.45104 > deham01.sixxs.net.5072: UDP, length 44
16:57:07.608760 IP 192.168.9.254.45104 > deham01.sixxs.net.5072: UDP, length 44
16:57:11.525727 IP 192.168.9.254.45104 > deham01.sixxs.net.5072: UDP, length 92
16:57:15.527214 IP 192.168.9.254.45104 > deham01.sixxs.net.5072: UDP, length 92
[fixed title]
State change: user
The state of this ticket has been changed to user
My tunnel doesn't work
Tcpdumps are nice and all that, but with the output you provide the only thing that I can conclude is that you are starting AICCU (but which version etc, on which platform etc, I have no idea), which then contacts the TIC server, and then starts sending outbound AYIYA packets. There are no contents of these packets, thus can't know what is actually in there.
Please do a tcpdump and record it to a file, using -s 1500 to store the full packets. But more importantly at this moment (the moment where a user says that it doesn't work), provide all the configuration details, as requested in the reporting problems checklist.
My tunnel doesn't work
Shadow Hawkins on Wednesday, 22 October 2008 17:19:20
I know that a full dump provides more information. But I didn't wanted to make my credentials publicly available, only wanted to show, that the TIC server points me to the correct POP and I don't get any response from that.
Until October, the 16th, the tunnel worked fine. I haven't touched the configuration since then. The working configuration was on an Ubuntu 8.04 system with the distribution provided version 20070115-7. I also tried it on a debian lenny (version 20070115-9) in a completely different environment. Both configuration files were generated by the install script.
As I thought it was clear by my previous description: 'aiccu test' failed at test [6/8] (Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:900:bc9::1))
I've just dumped a raw trace of what happens with 'aiccu test'. I'm fine with mailing it to someone who probably already has access to my tunnel credentials.
Matthias Rabe
My tunnel doesn't work
only wanted to show, that the TIC server points me to the correct POP
What other PoP would it point you to? Tunnels are allocated per PoP and the PoPs and tunnels have static addresses.
I haven't touched the configuration since then
Did you, or the part you can't know, also not touched the rest of the Internet that might affect packet flow between you and the PoP?
Both configuration files were generated by the install script.
Which "install script"?
As I thought it was clear by my previous description: 'aiccu test' failed at test [6/8] (Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:900:bc9::1))
Which can be because of a LOT of problems, starting with packets not being delivered at the PoP.
I'm fine with mailing it to someone who probably already has access to my tunnel credentials.
Please try reading the contact page, it contains all the details for these situations.
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 21 October 2008 08:38:32
Posting is only allowed when you are