No pk- Just nice traffics
posted by Kogan
2001-03-13 17:40:21
<- Back Down to comments Down to last comment
Hm. Anyone ever seen such a thing? Didn't know this really works!!
Normally it sould go like this:

traceroute to fire.pvv.org (129.241.210.221), 30 hops max, 40 byte packets
 1  140.78.40.31 (140.78.40.31)  2.324 ms  2.669 ms  2.603 ms
 2  Linz.ACO.net (193.171.22.17)  1.577 ms  2.371 ms  1.825 ms
 3  Vienna-RBS.ACO.net (193.171.25.9)  5.195 ms  6.938 ms  7.316 ms
 4  aconet.at.ten-155.net (212.1.192.225)  7.184 ms  9.028 ms  6.864 ms
 5  at-se.se.ten-155.net (212.1.192.22)  50.538 ms  49.579 ms  50.423 ms
 6  ne-gw.nordu.net (212.1.196.162)  49.477 ms  49.166 ms  50.451 ms
 7  e-gw.nordu.net (193.10.252.209)  51.558 ms  51.919 ms  49.959 ms
 8  no-gw.nordu.net (193.10.68.30)  57.246 ms  56.258 ms  57.353 ms
 9  oslo-gw1.uninett.no (193.10.68.50)  68.593 ms  59.653 ms  57.761 ms
10  trd-gw.uninett.no (128.39.0.250)  69.654 ms *  65.264 ms
11  ntnu-gw2.ntnu.no (158.38.0.222)  66.564 ms  65.203 ms  68.25 ms
12  sb-gw.ntnu.no (129.241.76.130)  64.495 ms  67.237 ms  66.762 ms
13  fire.pvv.org (129.241.210.221)  65.163 ms  64.046 ms  63.967 ms


But this time it went this:
traceroute to fire.pvv.org (129.241.210.221), 30 hops max, 40 byte packets
 1  140.78.40.31 (140.78.40.31)  2.711 ms  3.847 ms  2.325 ms
 2  Linz.ACO.net (193.171.22.17)  2.438 ms  2.817 ms  4.654 ms
 3  Vienna-RBS.ACO.net (193.171.25.9)  11.789 ms  11.762 ms  11.332 ms
 4  * aconet.at.ten-155.net (212.1.192.225)  11.693 ms  10.146 ms
 5  at-de.de.ten-155.net (212.1.192.6)  18.22 ms  17.615 ms  24.242 ms
 6  ch-de.ch.ten-155.net (212.1.192.29)  49.329 ms  52.97 ms  54.843 ms
 7  ch-de.de.ten-155.net (212.1.192.30)  57.473 ms  61.682 ms  67.667 ms
 8  ch-de.ch.ten-155.net (212.1.192.29)  111.216 ms  106.048 ms  89.327 ms
 9  ch-de.de.ten-155.net (212.1.192.30)  94.118 ms  104.635 ms  100.538 ms
10  ch-de.ch.ten-155.net (212.1.192.29)  236.128 ms  99.014 ms  103.496 ms
11  ch-de.de.ten-155.net (212.1.192.30)  113.828 ms  103.404 ms  107.961 ms
12  ch-de.ch.ten-155.net (212.1.192.29)  138.368 ms  137.251 ms  146.266 ms
13  ch-de.de.ten-155.net (212.1.192.30)  210.452 ms  187.302 ms  149.964 ms
14  ch-de.ch.ten-155.net (212.1.192.29)  200.109 ms  209.11 ms  205.958 ms
15  ch-de.de.ten-155.net (212.1.192.30)  223.421 ms *  238.561 ms
16  * ch-de.ch.ten-155.net (212.1.192.29)  187.717 ms  192.94 ms
17  ch-de.de.ten-155.net (212.1.192.30)  202.419 ms  250.952 ms  278.417 ms
18  ch-de.ch.ten-155.net (212.1.192.29)  317.215 ms  261.308 ms  288.151 ms
19  ch-de.de.ten-155.net (212.1.192.30)  221.157 ms  251.622 ms  286.796 ms
20  ch-de.ch.ten-155.net (212.1.192.29)  259.652 ms  354.217 ms  333.121 ms
21  ch-de.de.ten-155.net (212.1.192.30)  392.5 ms  373.896 ms *
22  ch-de.ch.ten-155.net (212.1.192.29)  426.461 ms  447.593 ms  344.121 ms
23  ch-de.de.ten-155.net (212.1.192.30)  340.442 ms  294.764 ms  292.849 ms
24  ch-de.ch.ten-155.net (212.1.192.29)  318.214 ms  423.368 ms  405.916 ms
25  ch-de.de.ten-155.net (212.1.192.30)  403.347 ms  356.151 ms *
26  ch-de.ch.ten-155.net (212.1.192.29)  262.399 ms  250.42 ms  238.463 ms
27  ch-de.de.ten-155.net (212.1.192.30)  208.467 ms  260.074 ms  347.718 ms
28  ch-de.ch.ten-155.net (212.1.192.29)  435.65 ms  535.651 ms  475.887 ms
29  ch-de.de.ten-155.net (212.1.192.30)  368.811 ms  400.313 ms  381.197 ms
30  ch-de.ch.ten-155.net (212.1.192.29)  503.538 ms  419.087 ms  490.882 ms
31  fire.pvv.org (129.241.210.221)  502.163 ms  400.046 ms  463.967 ms
Top of Page Down to last comment


Griffin2001-03-13 17:43:24
rofl...

and 4 players playing from that lab !
- but with THAT link now the darkies FINALLY have a lil' chance ! *ggg*
Feiht2001-03-13 17:46:07
And? this happends a lot due to bad rip or router configurations. I wounder why the hell you come trough to mume.
Kogan2001-03-13 18:24:02
Dunno. 1st time i've ever seen this.
Shadrach2001-03-13 20:23:34
Die in your own shit Kogan
Haxor2001-03-13 22:50:30
now I know ip addy's I can destroy their link!
Vorlin2001-03-13 22:51:30
My guess is that he came through to mume at the end because the problem was resolved. I've seen this a couple of times when I bothered to tracert a bad/frozen link, though it's one of the few link fuckups that's never happened to me with mume, only other muds.
Daevia2001-03-13 23:00:10
Smart move showing people your IP. :)
Kreil2001-03-14 04:17:42
Heh nod Daevia :)
I would be concerned a tad about that.. looks like you had a routing loop there on the second try.. *cringe* Who the hell's maintaining your routers! :)
Arhar2001-03-14 13:39:14
Some root hase crooked arms, when Routers not properly configured. 1mobdeath i got to this shit.
Jahara2001-03-14 15:26:11
Pretty when you bounce between 2 servers ^_^
Comment this:
Your name:


Your comment:

Avaliable characters:
<- Back Post a CommentTop of Page Up to first comment

© Copyright 1999-2018 mume.net