Its ok Julius, I care not. Just giving the facts.
Sorry Klouse, was just going off of Variel's legendinfo on your death.
In no particular order...
Relg, by Bolgerman
Wormbaneii, by Bolgerman
Lotze, by Unknown
Klouse, by Unknown
That is where I come into play. I haven't died in
this war by a pk. I have died like 4 times at
mordor gates though. Last time I was pk'd was
at the Black Sword. Take that to the bank! :P
alright alright so maybe some of you have bad connections... but comparitively, its awful for me..tonight my connection was good, so I checked it out..and this was what it said:
C:\>tracert towers.angband.com
Tracing route to towers.angband.com [216.66.12.12]
over a maximum of 30 hops:
1 5 ms 2 ms 2 ms jc-lawrence.noment.net
2 25 ms 25 ms 14 ms sl-gw12-kc-5-1-0-TS23.sprintlink.net [144.232.22
7.209]
3 14 ms 14 ms 16 ms sl-bb21-kc-0-0.sprintlink.net [144.232.23.2]
4 34 ms 32 ms 40 ms sl-bb21-fw-10-2.sprintlink.net [144.232.18.117]
5 21 ms 27 ms 27 ms sl-gw20-fw-9-0.sprintlink.net [144.232.11.130]
6 22 ms 39 ms 29 ms sl-williamscom-11-0.sprintlink.net [144.232.194.
50]
7 98 ms 69 ms 63 ms 64.200.232.126
8 79 ms 79 ms 62 ms hrndva1wcx2-oc48.wcg.net [64.200.95.77]
9 93 ms 71 ms 88 ms nycmny2wcx2-oc48.wcg.net [64.200.240.45]
10 64 ms 77 ms 68 ms nycmny2wcx3-pos9-0.wcg.net [64.200.87.226]
11 57 ms 66 ms 79 ms nycmnyhlce1-oc48.wcg.net [64.200.87.110]
12 111 ms 100 ms 118 ms nycmnyhlce1-telehouse-gige.wcg.net [64.200.86.15
4]
13 104 ms 111 ms 90 ms 207.99.60.30
14 109 ms 94 ms 122 ms 216.66.12.12
Everytime you begin to think 'Maybe Nikka is gone for good this time!' he pops up again, it's really quite depressing.
is this a good connection? :)
:\>tracert towers.angband.com
Tracing route to towers.angband.com [216.66.12.12]
over a maximum of 30 hops:
1 14 ms 14 ms <10 ms 10.17.224.1
2 14 ms 14 ms 14 ms 12.215.16.161
3 14 ms 27 ms 14 ms 12.215.5.18
4 27 ms 14 ms 27 ms gbr2-a90s10.cgcil.ip.att.net [12.123.4.166]
5 27 ms 27 ms 28 ms tbr1-p013602.cgcil.ip.att.net [12.122.11.37]
6 27 ms 28 ms 13 ms 12.123.6.33
7 14 ms 28 ms 27 ms so-1-1-0.edge1.Chicago1.Level3.net [209.0.227.77
]
8 28 ms 13 ms 28 ms so-7-0-0.mp1.Chicago1.Level3.net [209.244.8.9]
9 69 ms 55 ms 55 ms so-3-0-0.mp2.NewYork1.Level3.net [64.159.1.42]
10 54 ms 55 ms 69 ms gige7-1.ipcolo1.NewYork1.Level3.net [64.159.17.9
9]
11 41 ms 55 ms 55 ms unknown.Level3.net [209.246.123.146]
12 41 ms 41 ms 55 ms f1-3.br1.nyc.he.net [216.66.3.22]
13 42 ms 41 ms 55 ms pilosoft-lis.gw.lightning.net [209.51.161.70]
14 55 ms 55 ms 68 ms 216.66.12.12
Trace complete.
C:\>
Packets: Sent=4, Received=4, Lost=0 (0% loss),
Approximate round trip time in milliseconds:
Minimum= 83ms, Maximum= 85ms, Average= 84ms
Yay!
no it's not good theo, you'd have to be less than 200ms ping rates
Approximate round trip times in milliseconds:
Minimum = 210ms, Maximum = 228ms, Average = 220ms.
Is that good?
With no packet loss!
Now that I'm not online...
Minimum = 20ms, Maximum = 24ms, Average = 21ms
Blah, you all got a good one:
Minimum = 357 ms, Maximum = 412ms, Medel = 388 ms
*sobs*
--- towers.angband.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 160.211/170.310/181.586/6.587 ms
[kkc@duckie kkc]$
Seen better days, aye. But sure as hell seen worse too :P Now let's stop flooding the poor server with ICMP before someone thinks we're trying to DDoS arda ;)
God bless ethernet:
Approximate round trip times in mili-seconds:
Minimum = 66ms, Maximum = 68ms, Average = 67ms
Of course to do that, you'd first have to get into the VC bar...
I get 50-100ms late at night, infinite lag at peak usage time, so if you want to kill me do it between 7 and 12 pm.
*Go into user support mode*
go to start -> run -> type 'command' or 'cmd'
this will bring up your dos box.
Then at the prompt type:
'tracert towers.angband.com'
and sit back and watch!
*apologizes to Julius in advance*
Adunazon, dont hate. notice how yours is the only derogatory statement on here?
and I'm sorry but I honestly don't know how you guys are doing this, I'm a chemist not computer whiz. Would be nice to know though *hinthint*
Tell me more about packet loss :) 21ms but I'm almost always lagged.
21ms ping rate...and 40% packet loss.
I mud with no less than 500 ms ping all year long.
That's when my connection is good.
Quit bitching. :P
actually my connection is pretty decent unless there are more than 3 people in the same room, when I'm in parties, or when I'm banged I have incredible big packets of lag, I assume it's as well for evryone...
For about a month last year, I would randomly go linkdead because of a dead router. I would have pings of 230 or so, then it would time out for about 20 seconds. That was fun. :)
ok, it's obvious we're all bored. someone post a log.
I think mine is ok ;)
C:\WINDOWS\Desktop>tracert towers.angband.co;
Unable to resolve target system name towers.angband.co;.
C:\WINDOWS\Desktop>tracert towers.angband.com
Tracing route to towers.angband.com [216.66.12.12]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms NECSIPAAL [xxx.xxx.x.x]
2 55 ms 27 ms 14 ms gw.dhcp212-198-218.noos.fr [212.198.218.1]
3 <10 ms 14 ms 28 ms cortes-if2-vl26.noos.net [212.198.1.3]
4 14 ms 14 ms 13 ms cartier-pc1-26.noos.net [212.198.1.6]
5 27 ms 14 ms <10 ms blackburn-ge001.noos.net [195.132.16.76]
6 14 ms 13 ms <10 ms alvarado-ge-0200.noos.net [195.132.16.186]
7 27 ms 41 ms 14 ms above.freeix.net [213.228.3.234]
8 55 ms 28 ms 13 ms 208-184-231-57.above.net [208.184.231.57]
9 82 ms 83 ms 83 ms so-6-3-0.cr1.lga1.us.mfnx.net [216.200.127.69]
10 96 ms 96 ms 82 ms so-1-0-0.cr1.lga3.us.mfnx.net [64.125.30.18]
11 83 ms 83 ms 137 ms 216.200.56.54.has.no.reverse [216.200.56.54]
12 97 ms 109 ms 97 ms pilosoft-lis.gw.lightning.net [209.51.161.70]
13 123 ms 96 ms 138 ms 216.66.12.12
Trace complete.
Tell me more about lag
Pinging towers.angband.com [216.66.12.12] with 32 bytes of data:
Reply from 216.66.12.12: bytes=32 time=1722ms TTL=234
Reply from 216.66.12.12: bytes=32 time=2047ms TTL=234
Request timed out.
Reply from 216.66.12.12: bytes=32 time=1391ms TTL=234
Ping statistics for 216.66.12.12:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 1391ms, Maximum = 2047ms, Average = 1290ms
except it doesnt seem to be working for me now heh, open mouth insert foot. they're either suppressing icmp replies or my school's firewall is filtering it
oh, and 'ping towers.angband.com' works just as well, without all the damn *** spam
*hacks jc-lawrence.noment.net and sets up a packet sniffer
:P jk
You think thats Lag Julius? Dam, your Lucky. Recently im lucky to get below 400!
Still, mine is a stupid ISP not so much towers.
But it dont help.
what the fuck, why didnt that work properly?.... i spent 5 minutes writing that up... hmph :P
Tracing route to towers.angband.com [216.66.12.12]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 10.0.0.138
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out. 6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out. 16 * * * Request timed out.
17 339 ms * * 216.66.12.12
18 * 359 ms * 216.66.12.12
19 * 372 ms 307 ms 216.66.12.12
Trace complete.
Mmm packet loss.
Um, I think the log shows exactly how he did it, Wasach. At least you have your label correct.
perhaps you'd like to share how you did that with us ignant bitches?
A good connection will have under 200ms ping rates....as you can see most of mine are clearly above that. Part of the problem seems to extend directly from the server, which is the final 'route'. Blah.
This lag is killing me...literally.
I once had 3500ms ping rates... needless to say, I couldn't play at all...
What is it?