|
Ticket ID: SIXXS #4340541 Ticket Status: User PoP: frmrs01 - Jaguar Network SARL (Marseille)
No connectivity on tunnel T20672
![[fr]](/s/countries/fr.gif) Shadow Hawkins on Friday, 22 April 2011 13:08:58
Hi,
I would like to report connectivity issues on tunnel T20672. No traffic has been going through the tunnel since the beginning of April.
The tunnel is apparently established correctly as aiccu doesn't report any error.
aiccu test fails at the IPv6 Remote endpoint ping, indicating the problem is not on our side.
We're using AICCU from Debian Squeeze (which is version 20070115-14). There doesn't seem to be any bug report concerning connectivity issues on the Debian BTS, and the tunnel worked for a few weeks after the upgrade.
For testing, I cleared out IPv6 firewall tables, to no avail. The routing table is reproduced below :
2a01:240:fe00:68::/64 dev sixxs2 proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
2a01:240:fe3d:4::/64 dev crans proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
2a01:240:fe3d:c804::/64 dev crans.2 proto kernel metric 256 mtu 1496 advmss 1436 hoplimit 4294967295
fe80::/64 dev crans proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev crans.2 proto kernel metric 256 mtu 1496 advmss 1436 hoplimit 4294967295
fe80::/64 dev ens proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev sixxs2 proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
default via 2a01:240:fe00:68::1 dev sixxs2 metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295
IPv4 traceroute to the PoP:
traceroute to 78.153.240.201 (78.153.240.201), 30 hops max, 60 byte packets
1 irts-ext.ens-cachan.fr (138.231.135.5) 3.544 ms 3.480 ms 3.464 ms
2 pioneer.zrt.ens-cachan.fr (138.231.132.1) 5.519 ms 5.467 ms 5.430 ms
3 193.49.65.1 (193.49.65.1) 5.505 ms 5.775 ms 6.128 ms
4 * * *
5 vl172-orsay-rtr-021.noc.renater.fr (193.51.189.249) 10.728 ms 10.714 ms 10.661 ms
6 te0-1-0-5-paris1-rtr-001.noc.renater.fr (193.51.189.242) 10.947 ms 12.072 ms 11.993 ms
7 te0-3-1-0-lyon1-rtr-001.noc.renater.fr (193.51.189.126) 12.230 ms 12.351 ms 15.111 ms
8 * * *
9 jaguar-l2-2.peers.lyonix.net (77.95.71.32) 15.621 ms 15.621 ms 15.607 ms
10 sixxs.cust.jaguar-network.net (78.153.224.50) 17.519 ms 18.021 ms 17.984 ms
11 78.153.240.201 (78.153.240.201) 18.200 ms 18.171 ms 21.005 ms
Of course, no IPv6 connectivity so no IPv6 traceroute.
Maybe this is related to the fact that, as a consequence of upgrading our transparent proxy to a newer version of squid, a significant part of our HTTP traffic (think Google, YouTube and consorts) is going through IPv6, hence incurring a lot of traffic (~20Mb/s daily peak) on our tunnel, coming from only one IP address (either 2a01:240:fe3d:4:21f:29ff:fe08:a4ae or 2a01:240:fe3d:c804:21f:29ff:fe08:a4ae, I'm not quite sure which one squid chooses). This of course could be disabled if this is a problem for the PoP.
Thanks in advance
State change: user
The state of this ticket has been changed to user
No connectivity on tunnel T20672
The tunnel is apparently established correctly as aiccu doesn't report any error.
AICCU only does the setup of a tunnel, it is unable to show any errors as it would just be speculating of what the problem might be as there are tons of problems that can occur.
This is why there is this big yellow/orange box which points to the contact page which has a checklist. Please check that checklist and provide the requested details from that list.
And no, there are not traffic limitations.
|
![[ch]](/s/countries/ch.gif)
on Friday, 22 April 2011 23:51:17
Posting is only allowed when you are