|
Ticket ID: SIXXS #650216 Ticket Status: User PoP:
routing issues between uschi01 and usqas01
![[us]](/s/countries/us.gif) Shadow Hawkins on Tuesday, 08 January 2008 00:06:19
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
I have active tunnels from uschi01, usqas01 and usewr01.
From ewr I have no problems contacting the other two.
From chi I can telnet to qas; sending mail and browsing port 80 both work.
But I cannot get from qas to chi. None of tcp/80, tcp/53 nor udp/53 get thru.
Pings also fail in both directions.
All three can contact noc.sixxs.net w/o problem.
I do not know how long this has gone on.
State change: user
The state of this ticket has been changed to user
routing issues between uschi01 and usqas01
Please actually read and understand the "Reporting Problems" section on the Contact page and provide a lot more information. Source & Destination addresses are useful in this case and also a tcpdump showing the traffic, traceroutes of the paths taken etc etc etc.
routing issues between uschi01 and usqas01
Shadow Hawkins on Wednesday, 09 January 2008 03:30:30
Just an update: uschi01.sixxs.net is now completely offline.
v4 traceroutes from a number of sites around the US all route to kcnap.net and then fall on the floor.
It looks like TowardEX hsa broken v4 routing.
Also, on the v6 side I can only get to uschi01.sixxs.net from other TowardEX occaid pops, eg:
1 gw-15.ewr-01.us.sixxs.net (2001:4830:1200:e::1) 279.236 ms
2 bbr01-g0-3.nwrk01.occaid.net (2001:4830:e2:29::1) 168.935 ms
3 bbr01-t1-0.bstn01.occaid.net (2001:4830:ff:15c4::2) 188.874 ms
4 bbr01-g1-0.chcg01.occaid.net (2001:4830:ff:1300::2) 229.962 ms
5 sixxs-ic-1501-ord.customer.occaid.net (2001:4830:e5:5::2) 170.996 ms
But from the non-TowardEX occaid POPs (usqas01, by Hotnic) the v6 routing also fails.
It is also impossible to get to usatl01.sixxs.net from the Hotnic pop; routing also goes to tiscali.net and fails. And via v4 the routing to usatl01 loops between 207.210.95.249 and 207.210.95.250. And also for routing from the Hotic pop to TowardEX's usbos01 pop.
So this seems to be a problem with TowardEX's adverts.
routing issues between uschi01 and usqas01
Carmen Sandiego on Wednesday, 09 January 2008 19:15:21
v4 traceroutes from a number of sites around the US all route to kcnap.net and then fall on the floor.
My logs show that this problem started at about 2:10 AM CST Tuesday morning which happens to be when large unseasonable thunderstorms were rolling over Kansas City.
Tracing route to uschi01.sixxs.net [66.39.212.2]
over a maximum of 13 hops:
1 4 ms 10 ms <1 ms [192.168.2.1]
2 177 ms 190 ms 113 ms bras5-l0.stlsmo.sbcglobal.net [151.164.182.114]
3 94 ms 65 ms 120 ms dist2-vlan50.stlsmo.sbcglobal.net [151.164.14.131]
4 37 ms 140 ms 99 ms 151.164.93.224
5 144 ms 63 ms 68 ms ex1-p0-0.eqchil.sbcglobal.net [151.164.42.147]
6 65 ms 58 ms 63 ms te7-2.ccr02.ord03.atlas.cogentco.com [154.54.11.237]
7 113 ms 143 ms 161 ms vl3498.ccr02.ord01.atlas.cogentco.com [154.54.5.1]
8 64 ms 83 ms 117 ms te3-4.ccr02.mci01.atlas.cogentco.com [154.54.5.173]
9 215 ms 196 ms 168 ms te8-1.mpd01.mci01.atlas.cogentco.com [154.54.24.89]
10 124 ms 99 ms 97 ms kcnap.demarc.cogentco.com [66.28.31.138]
11 112 ms 100 ms 68 ms cr02-ge-vlan1-1.kc.kcnap.net [66.39.192.6]
12 * * * Request timed out.
13 * * * Request timed out.
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 08 January 2008 01:10:58
Posting is only allowed when you are