|
Ticket ID: SIXXS #5011269 Ticket Status: Resolved PoP: uschi02 - Your.Org, Inc. (Chicago, Illinois)
Tunnel T68381 unresponsive
![[us]](/s/countries/us.gif) Shadow Hawkins on Wednesday, 22 June 2011 07:35:59
Starting at about 3PM PDT, tunnel T68381 stopped passing IPv6 traffic. I am able to reach the POP via IPv4, and aiccu successfully configures the tunnel, however it does not work beyond that.
'aiccu test' fails at test #6, "Ping the IPv6 Remote/PoP Inner Tunnel Endpoint"
The machine which terminates this tunnel is running OpenBSD 4.9-STABLE, and aiccu compiled from ports. aiccu version is 20070115. This machine lives in Miami in the Terremark vCloud Express service, behind a NAT.
In an effort to troubleshoot, I temporarily reconfigured another machine of mine (which normally terminates tunnel T66817, under handle MBW7-SIXXS), to terminate tunnel T68381 using this handle. I was able to reproduce the same problem on that machine. Switching that machine back to its normal tunnel and handle resumed IPv6 connectivity. The other machine is geographically on the other side of the country in San Francisco, CA, also behind NAT. It runs Ubuntu 10.10, aiccu ver. 20070115 installed via apt.
tcpdump while trying to use the tunnel (my test was the classic "ping ipv6.google.com") shows UDP traffic to 216.14.98.22 (sixxs.cx01.chi.bb.your.org), and none returning.
Thank you for your assistance!
Tunnel T68381 unresponsive
Shadow Hawkins on Wednesday, 22 June 2011 07:44:03
A traceroute from the problem machine:
# traceroute uschi02.sixxs.net
traceroute to uschi02.sixxs.net (216.14.98.22), 64 hops max, 40 byte packets
1 10.112.4.1 (10.112.4.1) 0.659 ms 0.649 ms 0.659 ms
2 204.51.96.3 (204.51.96.3) 1.15 ms 0.850 ms 0.831 ms
3 72.46.239.97 (72.46.239.97) 1.27 ms 0.937 ms 0.882 ms
4 66.165.170.11 (66.165.170.11) 179.404 ms 22.8 ms 118.62 ms
5 t0-0-0-4.br2.mia.terremark.net (66.165.161.85) 5.892 ms 1.633 ms 1.233 ms
6 ge3-1.cr02.mia02.pccwbtn.net (198.32.124.130) 1.880 ms 1.927 ms 1.182 ms
7 your.org.ge2-5.br02.chc01.pccwbtn.net (63.218.5.38) 143.820 ms 56.771 ms 56.760 ms
8 sixxs.cx01.chi.bb.your.org (216.14.98.22) 58.211 ms 58.54 ms 57.834 ms
And from my other host, where I was able to reproduce the issue (technically this trace is from our edge router, as network policy prohibits it from users' workstations):
#traceroute 216.14.98.22
Type escape sequence to abort.
Tracing the route to sixxs.cx01.chi.bb.your.org (216.14.98.22)
1 12.116.205.77 0 msec 0 msec 0 msec
2 cr83.sffca.ip.att.net (12.122.137.10) 4 msec 4 msec 0 msec
3 cr1.sffca.ip.att.net (12.123.15.109) 4 msec 4 msec 0 msec
4 ggr7.sffca.ip.att.net (12.122.114.13) 32 msec 20 msec 48 msec
5 att-gw.sj.alter.net (192.205.36.62) 0 msec 0 msec 4 msec
6 0.ae3.XL4.SJC7.ALTER.NET (152.63.50.10) 4 msec 4 msec 4 msec
7 0.ge-4-3-0.XL4.CHI13.ALTER.NET (152.63.64.122) 52 msec 52 msec 52 msec
8 TenGigE0-7-1-0.GW5.CHI13.ALTER.NET (152.63.66.202) 68 msec 52 msec 52 msec
9 nlayer.customer.alter.net (63.84.100.186) 52 msec 56 msec 52 msec
10 as19255.ge-0-0-42-106.ar3.ord1.us.nlayer.net (69.31.111.22) 52 msec 52 msec 56 msec
11 sixxs.cx01.chi.bb.your.org (216.14.98.22) 52 msec 52 msec 52 msec
State change: resolved
The state of this ticket has been changed to resolved
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 22 June 2011 10:03:10
Posting is only allowed when you are