|
Ticket ID: SIXXS #6356262 Ticket Status: User PoP: czprg01 - Ignum, s.r.o. (Prague)
Tunnel T72281 down
![[cz]](/s/countries/cz.gif) Shadow Hawkins on Saturday, 28 January 2012 01:33:52
Hi,
For the last 30 hours or so I haven't been able to activate my tunnel T72281. For several hours, it was not even possible to start aiccu, now it can be started but the connection cannot be established.
The Inner Tunnel Endpoint (2a01:8c00:ff00:f3::1) is inaccessible though the IPv4 address of it (217.31.57.16) works fine.
I'm using Fedora 16 + aiccu 2007.01.15-console-linux, no problems since I set the tunnel and subnet up last Summer. To me it appears the problem is with the PoP at czprg01.
With regards,
Tomas Pecina (tomas@pecina.cz)
State change: user
The state of this ticket has been changed to user
Tunnel T72281 down
Please actually read and follow the "Reporting Problems" section on the Contact page and provide the requested details.
Tunnel T72281 down
Shadow Hawkins on Saturday, 28 January 2012 11:12:04
I don't know what information might be useful, everything seemed to be working fine and there was no change in my connection when the tunnel broke down.
Here are some details though:
uname -a:
Linux master.pecina.cz 3.2.1-3.fc16.x86_64 #1 SMP Mon Jan 23 15:36:17 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
traceroute:
traceroute to 217.31.57.16 (217.31.57.16), 30 hops max, 60 byte packets
1 router.pecina.cz (192.168.1.1) 1.434 ms 2.271 ms 3.280 ms
2 mail.gremis.cz (195.47.64.54) 11.302 ms 13.417 ms 15.964 ms
3 195.47.11.1.adsl.nextra.cz (195.47.11.1) 18.809 ms 20.738 ms 23.675 ms
4 phnc10-vl-62.net.nextra.cz (195.47.20.254) 27.114 ms 29.294 ms 31.506 ms
5 ph700-gwb-ge1-0-0-28.cz.net (213.29.170.81) 35.972 ms 38.739 ms 39.637 ms
6 ph700-ex1-tge0-4-0-0.cz.net (213.29.165.78) 44.777 ms 43.774 ms 46.917 ms
7 nix-m.backbone.ignum.cz (91.210.16.8) 46.328 ms 8.818 ms 9.483 ms
8 czprg01.sixxs.net (217.31.57.16) 12.623 ms 14.510 ms 16.447 ms
traceroute6:
traceroute to 2a01:8c00:ff00:f3::1 (2a01:8c00:ff00:f3::1), 30 hops max, 80 byte packets
1 * * *
...
30 * * *
tcpdump:
tcpdump: WARNING: sixxs: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on sixxs, link-type RAW (Raw IP), capture size 1500 bytes
10:59:46.026932 IP6 2a01:8c00:ff00:f3::2 > 2a01:8c00:ff00:f3::1: ICMP6, echo request, seq 11, length 64
10:59:47.026949 IP6 2a01:8c00:ff00:f3::2 > 2a01:8c00:ff00:f3::1: ICMP6, echo request, seq 12, length 64
10:59:48.026930 IP6 2a01:8c00:ff00:f3::2 > 2a01:8c00:ff00:f3::1: ICMP6, echo request, seq 13, length 64
1
...
Tunnel T72281 down
there was no change in my connection when the tunnel broke down.
No change, but you have a kernel from January 23rd....
Here are some details though:
Please provide all details as requested on the contact page.
traceroute6: traceroute to 2a01:8c00:ff00:f3::1 (2a01:8c00:ff00:f3::1), 30 hops max, 80 byte packets 1 * * *
While a traceroute6 to the PoP side of the tunnel could be useful to show that your packets going over the wrong route, as it is a directly connected tunnel, supplying the routing table of the host would be a lot more useful.
tcpdump: WARNING: sixxs: no IPv4 address assigned
As stated on the contact page, one needs to look at the interface where the in-IPv4 tunneled packets go over.
Please actually provide more details, as the details you are providing don't tell anything, except that something is broken, but that is a statement you already made.
|
![[ch]](/s/countries/ch.gif)
on Saturday, 28 January 2012 02:25:41
Posting is only allowed when you are