|
Ticket ID: SIXXS #1260084 Ticket Status: Resolved PoP: uschi02 - Your.Org, Inc. (Chicago, Illinois)
uschi02 not passing any traffic
![[ca]](/s/countries/ca.gif) Shadow Hawkins on Tuesday, 17 November 2009 14:25:38
As can been (both at my end of my tunnel, but more importantly) https://www.ipv4.sixxs.net/misc/traffic/?pop=uschi02&last=1day uschi02 doesn't seem to be passing any traffic.
Although this is clearly related to the PoP, not my end, my handle is BJM1-SIXXS.
uschi02 not passing any traffic
![[us]](/s/countries/us.gif) Shadow Hawkins on Tuesday, 17 November 2009 15:20:50
I'm (JWM7-RIPE) also experiencing this behavior. Both of my tunnels to uschi02 (T19631 and T19632) stopped passing traffic within the last twenty four hours. No configuration changes have been made on my end. Bouncing the tunnel interface does not effect any change.
uschi02 not passing any traffic
Shadow Hawkins on Tuesday, 17 November 2009 16:59:33
I tried restarting my tunnels too and it still doesn't work.
I have two tunnels ending at uschi02 and they can't access the v6 space, nor each other.
On my end, it started to stop forwarding traffic at 19h25 yesterday night (local time, EST, according to my Nagios).
uschi02 not passing any traffic
Shadow Hawkins on Tuesday, 17 November 2009 17:07:12
Hello,
"Me too." Two tunnels on uschi02 quit working over the past day.
Jim Nelson / JNN2-SIXXS
T16121 - Heartbeat tunnel on Ubuntu w/ aiccu 2007.01.15 . "aiccu test" fails on 2/8 : "####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (216.14.98.22)" . No pings are returned. Tested from US Dallas, TX Verizon FiOS network source IP 173.74.146.149 .
T17257 - AYIYA tunnel on WinXP w/ aiccu 2008-03-15 console version. "aiccu test" fails on 2/8: "####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (216.14.98.22)". No pings are returned. Tested from US Dallas, TX Sprint Aircard source IP 174.148.28.165 .
uschi02 not passing any traffic
Shadow Hawkins on Tuesday, 17 November 2009 17:49:37
im unable to ping the ipv4 endpoint.
ping 216.14.98.22
PING 216.14.98.22 (216.14.98.22) 56(84) bytes of data.
^C
--- 216.14.98.22 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2370ms
source is 216.75.14.43
I woke up to it being down.
my handle is DGH2-SIXXS
uschi02 not passing any traffic
Shadow Hawkins on Tuesday, 17 November 2009 19:37:16
I am experiencing the same problem with uschi02. i too tried pinging the PoP's IPv4 address and did not get any packets back.
uname -a
Linux dopamine 2.6.28-16-server #55-Ubuntu SMP Tue Oct 20 20:50:00 UTC 2009 i686 GNU/Linux
joe@dopamine:~$ ifconfig sixxs0
sixxs0 Link encap:IPv6-in-IPv4
inet6 addr: 2001:4978:f:3df::2/64 Scope:Global
inet6 addr: fe80::633f:f0f3/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:1788 (1.7 KB)
I set my router to log proto 41 traffic. I can see when I try to ping out, but I do not see any incoming activity on proto 41.
Source:99.63.240.243 -Destination:216.14.98.22 - [Forward]
[Tue, 2009-11-17 13:21:55] - IP Packet [Type Field:41] - Source:99.63.240.243 -Destination:216.14.98.22 - [Forward]
[Tue, 2009-11-17 13:26:27] - IP Packet [Type Field:41] - Source:99.63.240.243 -Destination:216.14.98.22 - [Forward]
[Tue, 2009-11-17 13:26:28] - IP Packet [Type Field:41] - Source:99.63.240.243 -Destination:216.14.98.22 - [Forward]
My handle is JSC8-SIXXS
uschi02 not passing any traffic
Shadow Hawkins on Tuesday, 17 November 2009 21:46:44
It looks like I am having the same issue getting a connection. The aiccu test fails when I am unable to ping sixxs IPv4 endpoint.
[2/8] Ping the IPv4 Remote/PoP Outer Endpoint (216.14.98.22)
PING 216.14.98.22 (216.14.98.22): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
--- 216.14.98.22 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
My handle is ZBB1-SIXXS
uschi02 not passing any traffic
Shadow Hawkins  on Tuesday, 17 November 2009 23:12:35
We're investigating this now. It appears that there's some desync between the router's routing table showing up in software, and what actually made it to the hardware. If we can't have it corrected within another 45 minutes, we'll schedule an emergency reload on the router.
uschi02 not passing any traffic
Shadow Hawkins on Wednesday, 18 November 2009 00:53:14
This seems to be fixed now. If anyone is still experiencing problems, please email noc@your.org for some one-on-one troubleshooting.
uschi02 not passing any traffic
Shadow Hawkins on Wednesday, 18 November 2009 01:12:31
Everything is working again for me. Looks like its fixed. Contact at Your.org was very responsive :)
State change: confirmed
 Shadow Hawkins on Wednesday, 18 November 2009 01:17:56
The state of this ticket has been changed to confirmed
State change: resolved
Shadow Hawkins on Wednesday, 18 November 2009 01:18:01
The state of this ticket has been changed to resolved
|
Posting is only allowed when you are