Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Esrevatem Dlareme
|
Posted - 2003.08.19 20:11:00 -
[1]
Edited by: Esrevatem Dlareme on 19/08/2003 20:12:02 This isn't exactly on topic but...I figure this is prolly the most likely place that the devs might see this, and it might help them with the CTD problem that started monday...
First off, there' s a new worm out. (Worm Info) It's a good worm. It will remove the msblaster worm for you, and download the patch from MS to protect you from the msblaster worm, then reboot your pc without asking. Yeah...but anyway, this new worm is causing an extremely high amount of network traffic which is literally slowing down the entire internet...smart move on whoever did that. This worm was first spotted on the 18th...the first day that I personally started crashing to login and desktop. (I don't normally CTD hardly ever)
My traceroute data to the Tranquility Server: C:\>tracert 157.157.139.10
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 150 ms 150 ms 140 ms gain-pm3-2.nortex.net [63.160.158.4] 2 140 ms 150 ms 140 ms gain-rtr-1.nortex.net [63.160.158.1] 3 140 ms 140 ms 131 ms red101.wcc.net [208.24.116.101] 4 150 ms 151 ms 310 ms isp-con-85.wcc.net [63.175.2.85] 5 161 ms 150 ms 160 ms dal-edge-11.inet.qwest.net [65.115.192.81] 6 160 ms 150 ms 150 ms dal-core-02.inet.qwest.net [205.171.25.149] 7 150 ms 170 ms 151 ms dal-brdr-02.inet.qwest.net [205.171.25.50] 8 150 ms 151 ms 160 ms acr1-so-2-0-0.Dallas.cw.net [208.172.131.201] 9 170 ms 170 ms 150 ms agr3-loopback.Dallas.cw.net [208.172.130.103] 10 170 ms 170 ms 151 ms dcr1-so-0-2-0.Dallas.cw.net [208.172.139.9] 11 281 ms 270 ms 280 ms bcr1.Thamesside.cw.net [166.63.210.61] 12 280 ms 271 ms 270 ms iar1-loopback.Thamesside.cw.net [166.63.210.7] 13 * * 291 ms iceland-telecom-ltd.Thamesside.cw.net [166.63.217.6] 14 * * * Request timed out. 15 * * * Request timed out.
All hops after 13 time out. I only get one packet back from iceland-telecom-ltd.Thamesside.cw.net [166.63.217.6], and on subsequent traceroutes, It doesn't even get listed, except again I get one packet back on the last traceroute I did...I expect this is the problem point atm, at least it is providing serious problems for me...I can't really speculate *why* this address is fubar'd for me atm, it could be due to many things, but it's most likely a chokepoint that's being closed off by internet traffic being generated by the new worm...
Any thoughts? Any other traceroutes to confirm/contrast this data? |
Lijah Reaper
|
Posted - 2003.08.19 20:27:00 -
[2]
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 1 ms 1 ms 1 ms homeportal.gateway.2wire.net [172.16.0.1] 2 10 ms 10 ms 7 ms 10.172.16.1 3 7 ms 13 ms 8 ms 172.30.150.81 4 8 ms 9 ms 10 ms 12.124.179.153 5 9 ms 9 ms 12 ms gbr6-p80.n54ny.ip.att.net [12.123.1.206] 6 12 ms 11 ms 11 ms tbr2-p012401.n54ny.ip.att.net [12.122.11.29] 7 10 ms 9 ms 15 ms ggr2-p390.n54ny.ip.att.net [12.123.3.62] 8 13 ms 10 ms 9 ms att-gw.chi.above.net [192.205.32.198] 9 85 ms 85 ms 120 ms bcr2.Thamesside.cw.net [166.63.210.62] 10 85 ms 87 ms 87 ms iar1-loopback.Thamesside.cw.net [166.63.210.7] 11 * * 87 ms iceland-telecom-ltd.Thamesside.cw.net [166.63.21 7.6] 12 * * * Request timed out. 13 ^C
Thats what I got :). Just because you can't ping a server doesn't mean it isn't there, or working correctly. It just means it's blocking pings.
However, the fact that it takes so many tries to ping that last server, and it actually gets through once in a while, is rather odd.
|
Lijah Reaper
|
Posted - 2003.08.19 20:28:00 -
[3]
Wow... I have <100ms ping to the UK? Awesome!
|
Doc Brown
|
Posted - 2003.08.19 20:29:00 -
[4]
from these traceroutes, it looks like the problem is at bcr1.Thamesside.cw.net a this is where the traceroute times jump.
That's a Cable & Wireless router, and probably a border/core router (bcr1).
_________________________________________________
There are no bad ideas, only bad implementations. |
ToKE
|
Posted - 2003.08.19 21:30:00 -
[5]
Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>cd C:\>tracert 157.157.139.10
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 38 ms 15 ms 25 ms 172.24.127.254 2 9 ms 9 ms 7 ms blfs-t2cam1-a-ge92.inet.ntl.com [213.105.206.1]
3 51 ms 11 ms 7 ms blfs-t2core-a-ge-wan61.inet.ntl.com [213.105.205 .29] 4 13 ms 10 ms 12 ms ren-bb-a-so-210-0.inet.ntl.com [62.253.188.217]
5 24 ms 25 ms 20 ms bre-bb-b-so-200-0.inet.ntl.com [62.253.185.166]
6 49 ms 21 ms 21 ms 195.50.116.133 7 24 ms 29 ms 21 ms so-4-0-0.mp1.London2.Level3.net [212.187.129.249 ] 8 95 ms 95 ms 94 ms so-1-0-0.bbr1.Washington1.level3.net [212.187.12 8.138] 9 96 ms 96 ms 130 ms so-6-0-0.edge1.Washington1.Level3.net [209.244.1 1.10] 10 97 ms 96 ms 96 ms uunet-level3-oc48.Washington1.Level3.net [209.24 4.219.158] 11 107 ms 96 ms 97 ms 0.so-0-3-0.XL1.DCA5.ALTER.NET [152.63.43.170] 12 99 ms 97 ms 97 ms 0.so-0-0-0.TL1.DCA6.ALTER.NET [152.63.38.69] 13 114 ms 118 ms 115 ms 0.so-3-0-0.TL1.CHI2.ALTER.NET [152.63.13.17] 14 114 ms 116 ms 114 ms 0.so-7-0-0.XL1.CHI2.ALTER.NET [152.63.68.81] 15 114 ms 115 ms 114 ms 0.so-6-1-0.BR6.CHI2.ALTER.NET [152.63.64.49] 16 123 ms 119 ms 131 ms bpr1-so-6-0-0.ChicagoEquinix.cw.net [208.174.226 .1] 17 146 ms 132 ms 118 ms dcr2-so-4-3-0.Chicago.cw.net [208.175.10.237] 18 117 ms 119 ms 143 ms bcr2.Thamesside.cw.net [166.63.210.62] 19 121 ms 168 ms 123 ms iar1-loopback.Thamesside.cw.net [166.63.210.7] 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out.
Trace complete.
C:\> _______________________________________________ Ahaahhhh you didn't count on my loyal army of Prostitutes did you? |
Luc Boye
|
Posted - 2003.08.19 21:49:00 -
[6]
Timeout in traceroute doesn't have to be a sign of bad ping. It could also mean that the node is refusing ICMP packets (ping and such). --
2004.12.29 23:33:40combatMining Pollution Cloud hits you, doing 140.0 damage. |
Ehxo
|
Posted - 2003.08.19 22:12:00 -
[7]
Edited by: Ehxo on 19/08/2003 22:33:58 My trace...
Quote: [ehxo@enterprise] /home/ehxo: traceroute 157.157.139.10 traceroute to 157.157.139.10 (157.157.139.10), 64 hops max, 44 byte packets 1 gnax-switch-100 (216.180.224.1) 0.512 ms 0.429 ms 0.599 ms 2 gnax-router-gige (209.51.131.57) 0.520 ms 0.440 ms 0.309 ms 3 atl-core-b.gnax.net (209.51.134.153) 0.705 ms 0.464 ms 0.559 ms 4 wcg-gige.gnax.net (209.51.130.34) 0.566 ms 0.436 ms 0.379 ms 5 atlnga6lce1-atm.wcg.net (64.200.126.69) 1.052 ms 1.056 ms 0.763 ms 6 ces1-gigabitethernet6-2-0-301.AtlantaPaix.cw.net (208.173.58.129) 1.002 ms 0.962 ms 0.872 ms 7 dcr1-so-4-3-0.Atlanta.cw.net (208.172.75.109) 0.961 ms 0.857 ms 1.257 ms 8 bcr1.Thamesside.cw.net (166.63.210.61) 108.937 ms 108.695 ms 109.574 ms 9 iar1-loopback.Thamesside.cw.net (166.63.210.7) 108.735 ms 108.830 ms 111.727 ms 10 iceland-telecom-ltd.Thamesside.cw.net (166.63.217.6) 108.838 ms * 108.788 ms 11 * * *
More info about the domain cw.net:
Quote: Registrant: Cable & Wireless PLC (SBWEMNLLSD) 124 Theobalds Road London, UK WC1X 8RX UK
Domain Name: CW.NET
Administrative Contact, Technical Contact: Internet DNS Engineering (MTC3-ORG)[email protected] Internet DNS Engineering 9000 Regency Parkway Suite 200 Cary, NC 27511 US 800-977-4662 opt.4/ 919-4 fax: 1 919 465 4187
Record expires on 14-May-2005. Record created on 13-May-1995. Database last updated on 19-Aug-2003 18:07:51 EDT.
Domain servers in listed order:
NS.CW.NET 204.70.128.1 NS3.CW.NET 204.70.25.234 NS4.CW.NET 204.70.49.234 NS2.CW.NET 204.70.57.242 NS5.CW.NET 204.71.116.25
|
ToKE
|
Posted - 2003.08.19 22:25:00 -
[8]
well the lag has gone BIG time, so im happier, my trace is alot faster too. Both traces were done with game running
Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>cd C:\>tracert 157.157.139.10
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 8 ms 41 ms 45 ms 172.24.127.254 2 10 ms 18 ms 44 ms blfs-t2cam1-a-ge92.inet.ntl.com [213.105.206.1]
3 22 ms 9 ms 11 ms blfs-t2core-a-ge-wan61.inet.ntl.com [213.105.205 .29] 4 10 ms 9 ms 12 ms ren-bb-a-so-210-0.inet.ntl.com [62.253.188.217]
5 15 ms 13 ms 9 ms ren-bb-b-ae0-0.inet.ntl.com [62.253.185.186] 6 18 ms 17 ms 15 ms man-bb-a-so-600-0.inet.ntl.com [62.253.185.170]
7 * * * Request timed out. 8 37 ms 24 ms 23 ms bcr2-so-3-0-0.Thamesside.cw.net [166.63.209.201]
9 32 ms 38 ms 23 ms iar1-loopback.Thamesside.cw.net [166.63.210.7] 10 23 ms * * iceland-telecom-ltd.Thamesside.cw.net [166.63.21 7.6] 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * _______________________________________________ Ahaahhhh you didn't count on my loyal army of Prostitutes did you? |
ToKE
|
Posted - 2003.08.19 22:33:00 -
[9]
oh.. no.. wait i got booted again
_______________________________________________ Ahaahhhh you didn't count on my loyal army of Prostitutes did you? |
Jarjar
|
Posted - 2003.08.19 23:00:00 -
[10]
jarjar@raven->~$ traceroute 157.157.139.10 traceroute to 157.157.139.10 (157.157.139.10), 64 hops max, 40 byte packets 1 217.208.141.1 (217.208.141.1) 6.993 ms 6.836 ms 6.697 ms 2 10.0.111.1 (10.0.111.1) 6.661 ms 6.669 ms 7.394 ms 3 u-d2-feth3-2.se.telia.net (217.208.140.254) 7.111 ms 7.481 ms 6.882 ms 4 vs-b-c1-pos1-1.se.telia.net (213.64.25.29) 10.703 ms 8.413 ms 8.98 ms 5 hy-sc1-pos13-1.se.telia.net (212.181.203.209) 11.212 ms 10.133 ms 9.624 ms 6 s-b4-pos2-0.telia.net (213.248.66.17) 10.64 ms 10.326 ms 10.96 ms 7 s-b3-pos11-0.telia.net (213.248.64.150) 10.57 ms 8.939 ms 9.249 ms 8 ycr2-so-0-2-0.Stockholm.cw.net (166.63.220.65) 11.196 ms 9.849 ms 9.221 ms 9 ycr1-so-2-0-0.Stockholm.cw.net (166.63.220.29) 33.370 ms 33.179 ms 33.876 ms 10 ycr1-so-1-0-0.Copenhagen.cw.net (208.173.216.25) 29.615 ms 28.734 ms 29.599 ms 11 ycr2-so-2-0-0.Copenhagen.cw.net (208.173.216.2) 34.396 ms 34.202 ms 33.483 ms 12 bcr1-so-2-0-0.Amsterdam.cw.net (208.173.211.233) 34.490 ms 34.436 ms 34.116 ms 13 bcr2.Thamesside.cw.net (166.63.210.62) 44.154 ms bcr1.Thamesside.cw.net (166.63.210.61) 41.637 ms 41.674 ms 14 iar1-loopback.Thamesside.cw.net (166.63.210.7) 44.208 ms 43.666 ms 41.768 ms 15 iceland-telecom-ltd.Thamesside.cw.net (166.63.217.6) 44.296 ms 43.302 ms 43.503 ms 16 * * * 17 * * * ^C jarjar@raven->~$ ping 157.157.139.10 PING 157.157.139.10 (157.157.139.10): 56 data bytes --- 157.157.139.10 ping statistics --- 11 packets transmitted, 0 packets received, 100% packet loss
The server is up though. I guess they're blocking it or something.
|
|
Jean Starwind
|
Posted - 2003.08.20 00:09:00 -
[11]
considering the new worm pings addresses to find new host to infect you are all adding to the problems!!! :P actually i dont think there is a problem related to this, since they originally thought traffice was not working but have now found out the server nodes are causing them and are working on the fix.
Btw my routers ICMP (ping) is a "stealth" port so it doesnt let anyone know it is even there, no response. Big pimpin |
Griskin Thor
|
Posted - 2003.08.20 00:25:00 -
[12]
Some quick info for those not familiar with EVE's network setup:
cw.net, Cable & Wireless, is an international backbone provider (as well as local ISP in some areas) that EVE has it's overseas peering to the US with. IIRC there is one peer in NY and one in Washington DC. These links help avoid lag that might otherwise be experienced with other transatlantic hops.
The increased ping times at the Thamesside.cw.net network is to be expected: that is the UK side of the transatlantic peer. 80-100ms latency is not unusual across such a long peer. In some cases you'll even see latency that high just getting from one coast of the US to the other.
As for the poor bugger who was coming from ntl.com (a UK ISP from what I can tell) over Level3.net to Washington DC to Chicago then back to the Washington C&W peer and over to London.. well, it looks like all of NTLs direct peers with the C&W portion of the network must have been overloaded, forcing their link to go overseas and back for a good connection. Most likely bad network design on Level3s part.. but then, I hate Level3. :)
Griskin Thor Chief Operations Officer >Lightwave Enterprises<
- "Oh yeah? Well, back in my day we had to mine omber with our teeth! And walk back to the station to sell it. Up the gravity well. Both ways!" |
sutty
|
Posted - 2003.08.20 00:30:00 -
[13]
Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\tom>cd C:\Documents and Settings\tom
C:\Documents and Settings\tom>C:
C:\Documents and Settings\tom>tracert 157.157.139.10
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 * * * Request timed out. 2 13 ms 7 ms 8 ms oldh-t2cam1-b-ge-wan52-123.inet.ntl.com [80.5.16 4.221] 3 12 ms 8 ms 13 ms man-t2core-b-ge-wan64.inet.ntl.com [213.104.242. 181] 4 9 ms 10 ms 10 ms man-bb-b-so-210-0.inet.ntl.com [62.253.184.61] 5 8 ms 12 ms 12 ms man-bb-a-ae0-0.inet.ntl.com [62.253.187.177] 6 8 ms 11 ms 12 ms ycr2-so-3-0.Manchester.cw.net [208.175.252.89] 7 17 ms 17 ms 20 ms bcr2-so-3-0-0.Thamesside.cw.net [166.63.209.201]
8 26 ms 19 ms 21 ms iar1-loopback.Thamesside.cw.net [166.63.210.7] 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 *
|
Mr Nice
|
Posted - 2003.08.20 00:50:00 -
[14]
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 * * * Request timed out. 2 * * * Request timed out. 3 30 ms 30 ms 30 ms POS5-0.GW1.LND9.ALTER.NET [146.188.63.129] 4 24 ms 24 ms 24 ms so-3-0-0.xr1.lnd9.alter.net [158.43.150.141] 5 22 ms 30 ms 30 ms so-0-1-0.TR1.LND9.ALTER.NET [146.188.15.33] 6 30 ms 23 ms 37 ms POS1-0.BR1.LND9.ALTER.NET [146.188.7.242] 7 30 ms 30 ms 30 ms 146.188.41.46 8 30 ms 30 ms 30 ms zcr2-ge-2-0-0.Londonlnt.cw.net [166.63.222.130]
9 30 ms 30 ms 30 ms bcr2.Thamesside.cw.net [166.63.210.62] 10 30 ms 30 ms 30 ms iar1-loopback.Thamesside.cw.net [166.63.210.7] 11 * iceland-telecom-ltd.Thamesside.cw.net [166.63.217.6] reports: Destination net unreachable.
Trace complete.
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |