|
Ticket ID: SIXXS #4469577 Ticket Status: User PoP: frmrs01 - Jaguar Network SARL (Marseille)
unable to make T64421 tunnel work
![[fr]](/s/countries/fr.gif) Shadow Hawkins on Sunday, 01 May 2011 18:56:03
Hello,
After an unsuccessful first attempt with the static tunnel type, I requested a change to automatic tunnel type.
The tunnel never got working.
On my side, I use the aiccu Debian package. The logs in verbose mode are included below.
This is the second tunnel I order. The first one has been working perfectly for weeks.
I am looking for hints on the way to investigate further.
I already tried to ping the IPv6 PoP end of the tunnel from a functionnal interface without success.
Apr 28 18:55:09 Cooper aiccu[3888]: sock_getline() : "200 SixXS TIC Service on nlams04.sixxs.net ready (http://www.sixxs.net)"
Apr 28 18:55:09 Cooper aiccu[3888]: sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-linux Linux/2.6.38.4"
Apr 28 18:55:09 Cooper aiccu[3888]: sock_getline() : "200 Client Identity accepted"
Apr 28 18:55:09 Cooper aiccu[3888]: sock_printf() : "get unixtime"
Apr 28 18:55:09 Cooper aiccu[3888]: sock_getline() : "200 1304009709"
Apr 28 18:55:09 Cooper aiccu[3888]: sock_printf() : "starttls"
Apr 28 18:55:09 Cooper aiccu[3888]: sock_getline() : "400 This service is not SSL enabled (yet)"
Apr 28 18:55:09 Cooper aiccu[3888]: TIC Server does not support TLS but TLS is not required, continuing
Apr 28 18:55:09 Cooper aiccu[3888]: sock_printf() : "username ZZZZ-SIXXS"
Apr 28 18:55:09 Cooper aiccu[3888]: sock_getline() : "200 ZZZZ-SIXXS choose your authentication challenge please"
Apr 28 18:55:09 Cooper aiccu[3888]: sock_printf() : "challenge md5"
Apr 28 18:55:09 Cooper aiccu[3888]: sock_getline() : "200 d2fdb4b51da27c10bc6dfde3771dfad3"
Apr 28 18:55:09 Cooper aiccu[3888]: sock_printf() : "authenticate md5 5af4848cb8ab40173276d0ad41f605b2"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "200 Successfully logged in using md5 as PLE4-SIXXS (Philippe Latu)"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_printf() : "tunnel show T64421"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "201 Showing tunnel information for T64421"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "TunnelId: T64421"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "Type: ayiya"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "IPv6 Endpoint: 2a01:240:fe00:175::2"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "IPv6 POP: 2a01:240:fe00:175::1"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "IPv6 PrefixLength: 64"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "Tunnel MTU: 1280"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "Tunnel Name: ZZZZ"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "POP Id: frmrs01"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "IPv4 Endpoint: ayiya"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "IPv4 POP: aa.bb.cc.dd"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "UserState: enabled"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "AdminState: enabled"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "Password: xxxx"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "Heartbeat_Interval: 60"
Apr 28 18:55:10 Cooper aiccu[3888]: sock_getline() : "202 Done"
Apr 28 18:55:10 Cooper aiccu[3888]: Successfully retrieved tunnel information for T64421
Apr 28 18:55:10 Cooper aiccu[3888]: sock_printf() : "QUIT None of this is real"
Apr 28 18:55:10 Cooper aiccu[3902]: AICCU running as PID 3902
Apr 28 18:55:10 Cooper aiccu[3902]: [AYIYA-start] : Anything in Anything (draft-02)
Apr 28 18:55:10 Cooper aiccu[3902]: [AYIYA-tun->tundev] : (Socket to TUN) started
State change: user
The state of this ticket has been changed to user
unable to make T64421 tunnel work
I am looking for hints on the way to investigate further.
Check if your firewall allows AYIYA packets to get to the PoP.
The details requested by that big yellow/orange box would at least give us a partial insight in what might go wrong, but unfortunately you are not supplying that information.
unable to make T64421 tunnel work
Shadow Hawkins on Sunday, 08 May 2011 21:48:30
Hello,
I have set up a public IPv4 address which is not filtered.
Although I can contact the PoP on its IPv4 address, it seems I don't get any answer to the AYIYA packets that are sent.
Here is a tshark sample of the trafic :
130.120.84.98 -> 78.153.240.201 AYIYA Source port: 59348 Destination port: 5072
130.120.84.98 -> 78.153.240.201 AYIYA Source port: 59348 Destination port: 5072
130.120.84.98 -> 78.153.240.201 ICMP Echo (ping) request (id=0x2024, seq(be/le)=1/256, ttl=64)
78.153.240.201 -> 130.120.84.98 ICMP Echo (ping) reply (id=0x2024, seq(be/le)=1/256, ttl=52)
130.120.84.98 -> 78.153.240.201 ICMP Echo (ping) request (id=0x2024, seq(be/le)=2/512, ttl=64)
78.153.240.201 -> 130.120.84.98 ICMP Echo (ping) reply (id=0x2024, seq(be/le)=2/512, ttl=52)
130.120.84.98 -> 78.153.240.201 ICMP Echo (ping) request (id=0x2024, seq(be/le)=3/768, ttl=64)
78.153.240.201 -> 130.120.84.98 ICMP Echo (ping) reply (id=0x2024, seq(be/le)=3/768, ttl=52)
2a01:240:fe00:175::2 -> 2a01:240:fe00:175::1 ICMPv6 Echo (ping) request
2a01:240:fe00:175::2 -> 2a01:240:fe00:175::1 ICMPv6 Echo (ping) request
2a01:240:fe00:175::2 -> 2a01:240:fe00:175::1 ICMPv6 Echo (ping) request
2a01:240:fe00:175::2 -> 2a01:240:fe00:175::1 ICMPv6 Echo (ping) request
2a01:240:fe00:175::2 -> 2a01:240:fe00:175::1 ICMPv6 Echo (ping) request
130.120.84.98 -> 78.153.240.201 AYIYA Source port: 59348 Destination port: 5072
130.120.84.98 -> 78.153.240.201 AYIYA Source port: 59348 Destination port: 5072
130.120.84.98 -> 78.153.240.201 AYIYA Source port: 59348 Destination port: 5072
130.120.84.98 -> 78.153.240.201 AYIYA Source port: 59348 Destination port: 5072
130.120.84.98 -> 78.153.240.201 AYIYA Source port: 59348 Destination port: 5072
Unfortunately, I have no way to capture trafic outside the campus.
Regards,
unable to make T64421 tunnel work
I have set up a public IPv4 address which is not filtered.
How sure are you that it is not filtered? As there are no valid AYIYA packets received on the PoP. And without that the tunnel won't work.
Please contact your network staff and ask them how 'unfiltered' your connection is, and if you are allowed to do tunneling in the first place.
Note that you are inside RENATER and thus they should be able to provide you with native IPv6, thus maybe your network administration is blocking tunneling protocols.
unable to make T64421 tunnel work
Shadow Hawkins on Monday, 09 May 2011 22:20:15
I have now installed the AICCU package on another machine located in another perimeter of the campus. The tunnel is now fully functionnal and this ticket can safely be closed.
Thanks for your patience.
Regards,
|
![[ch]](/s/countries/ch.gif)
on Sunday, 01 May 2011 18:57:06
Posting is only allowed when you are