Lithium CTF Nights

[Golgo13]

Here are some traceroutes samples from my connection. i attempted to vary the servers my host pinged, to reflect dedicated vs listen servers vs close servers to far servers, here are the results:

1) PacketFlinger :RA2: East Dedicated (didn't even know Claire put up a Ra2 server yet, but i will bookmark it now)

Traceroute to host.colocrossing.com [172.245.43.127]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  xxx.xxx.xx.x
  2    30 ms    29 ms    30 ms  10.32.147.1
  3    31 ms    31 ms    31 ms  P0-2-3-0.NYCMNY-LCR-22.verizon-gni.net [130.81.4
5.20]
  4    31 ms    30 ms    30 ms  ae2-0.NY5030-BB-RTR1.verizon-gni.net [130.81.199
.178]
  5    32 ms    31 ms    31 ms  0.xe-10-1-0.BR1.NYC1.ALTER.NET [152.63.18.225]
  6     *       39 ms    32 ms  ae11.edge2.NewYork.Level3.net [4.68.62.41]
  7    32 ms    32 ms    32 ms  vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
  8    32 ms    32 ms    32 ms  ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
  9    32 ms    32 ms    59 ms  ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]

 10    31 ms    31 ms    31 ms  ae-4-90.edge3.NewYork1.Level3.net [4.69.155.209]

 11    50 ms    35 ms    41 ms  CHOOPA-LLC.edge3.NewYork1.Level3.net [4.31.21.58
]
 12    36 ms    36 ms    36 ms  vl150-as3.pnj1.choopa.net [108.61.93.250]
 13    33 ms    33 ms    33 ms  108.61.16.82.choopa.net [108.61.16.82]
 14    36 ms    35 ms    35 ms  host.colocrossing.com [199.188.100.22]
 15    37 ms    35 ms    36 ms  host.colocrossing.com [172.245.43.127]

Trace complete.

----------------------------------------------------------------------------------------------------------------------------------
2) Normandy D-Day Listen server (closest listen available)


Tracing route to c-24-63-162-49.hsd1.ma.comcast.net [24.63.162.49]
over a maximum of 30 hops:

  1     2 ms     2 ms     1 ms 
  2    30 ms    29 ms    30 ms  10.32.147.1
  3    32 ms    31 ms    31 ms  P0-2-3-0.NYCMNY-LCR-22.verizon-gni.net [130.81.4
5.20]
  4    44 ms    30 ms    30 ms  ae0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.209
.126]
  5    31 ms    31 ms    31 ms  0.xe-1-2-0.XL4.NYC1.ALTER.NET [152.63.5.241]
  6    31 ms    31 ms    30 ms  0.xe-9-3-0.GW13.NYC1.ALTER.NET [152.63.5.5]
  7    32 ms    32 ms    31 ms  comcast.com.customer.alter.net [152.179.220.126]

  8    33 ms    33 ms    35 ms  he-0-4-0-0-cr01.newyork.ny.ibone.comcast.net [68
.86.83.93]
  9    38 ms    39 ms    39 ms  he-3-12-0-0-ar01.needham.ma.boston.comcast.net [
68.86.95.30]
 10    40 ms    40 ms    40 ms  68.85.106.46
 11    40 ms    66 ms    39 ms  te-3-0-0-ten01.lowell.ma.boston.comcast.net [68.
85.161.222]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 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.

---------------------------------------------------------------------------------------------------------------------------------------------------------

3) PacketFlinger :RA2: West Dedicated (farthest USA west coast server)

Tracing route to 172.245.219.176 over a maximum of 30 hops

  1     3 ms     3 ms     2 ms 
  2    30 ms    30 ms    29 ms  10.32.147.1
  3    33 ms    30 ms    33 ms  P0-2-3-0.NYCMNY-LCR-21.verizon-gni.net [130.81.4
5.22]
  4    31 ms    30 ms    30 ms  130.81.199.10
  5    31 ms    31 ms    32 ms  0.xe-9-0-0.BR2.NYC4.ALTER.NET [152.63.20.189]
  6    32 ms    31 ms    31 ms  TenGE2-1.br01.nyc01.pccwbtn.net [63.218.9.25]
  7    98 ms    99 ms    98 ms  dbtransit.ge9-6.br02.lax05.pccwbtn.net [63.218.7
3.174]
  8   103 ms   102 ms   103 ms  colo-lax8 [96.44.180.50]
  9    98 ms    98 ms    98 ms  67.215.251.214.static.quadranet.com [67.215.251.
214]
 10    98 ms    98 ms    98 ms  host.colocrossing.com [172.245.220.66]
 11    99 ms    98 ms    98 ms  172.245.219.176

Trace complete.

7. P1-0.NYCMNY-NYCXNYCR-ERXG02.verizon-gni.net  0.8%   119   46.3  51.8  46.0 107.1  12.9
 8. pool-71-190-xxx-xxx.nycmny.east.verizon.net  0.0%   119   72.5  78.2  71.6 107.4  12.9

That is how i concluded the comparison of my server with a dedicated.


-----------------------------------------------------------------------------------------------------------------------------------

 Host                                           Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. fragbait.tastyspleen.net                     0.0%   120    0.2   0.3   0.2   5.8   0.6
 2. ae13.dar02.sr01.dal01.networklayer.com       0.0%   120    0.2   0.6   0.1  17.1   2.5
 3. ae14.bbr01.eq01.dal03.networklayer.com       0.0%   120    8.4   0.4   0.2  10.7   1.3
 4. ae-6.r07.dllstx09.us.bb.gin.ntt.net          0.0%   120    0.8   0.9   0.6   2.5   0.4
 5. 0.ae12.BR2.DFW13.ALTER.NET                   0.0%   120    0.5   2.8   0.4  66.1   8.3
 6. B200.NYCMNY-LCR-21.verizon-gni.net           0.0%   119   44.6  43.5  41.4  60.5   2.1
 7. P1-0.NYCMNY-NYCXNYCR-ERXG02.verizon-gni.net  0.8%   119   46.3  51.8  46.0 107.1  12.9
 8. pool-71-190-xxx-xxx.nycmny.east.verizon.net  0.0%   119   72.5  78.2  71.6 107.4  12.9

P.S. now that i look at the graph you posted, i'm not even sure what i'm looking at. packet loss says 0.8%. i don't know what the glowing numbers mean, also i thought it was a regular traceroute until now Lol. woops. (somewhat advanced diagnostic traceroute it seems)

[Barton]

Well besides switching ISPs you could try your luck with using VPNs for better routing.

[Golgo13]

Well besides switching ISPs you could try your luck with using VPNs for better routing.

don't even know how to configure VPN's. i already have a constant IP now and it took me a long time to get that setup. i don't feel like changing it again.

[yahoo]

I think vpn wont solve the issue assuming that the network problem is on his isp's end. Also it would increase his latency /ping.

[ex]

The only thing that will really help is to buy a dedicated line.  With a line used solely for the purpose of running a server, you'll have far less complaints about ping/lag.  But of course, you'll need to get a lot of money together.  I think a t1 still runs you about $300 a month (for a cheap one) IIRC.

[[BTF]Sigma]

https://www.leetservers.com/secure/cart.php?pid=255

Have you thought about using a hosting service with a server location very close to you and manage it remotely?

*The link should be the order maker for a Quake 2 server. Doesn't look too expensive per month as an alternative to a dedicated line.

[haunted]

Sigma that is a terrible idea, stop trolling.

[[BTF]Sigma]

Sigma that is a terrible idea, stop trolling.

[fdrjk]

fader connected once with a 60 ping. he was able to play very well with it.

i want to add to this statement that me pinging 60 to new york from maryland is pretty bad. i ping 16 to new jersey (t4). i wouldnt be surprised if someone like ex or adren or anyone else who lives just a little more out west pinged more than 100.

[Golgo13]

fader connected once with a 60 ping. he was able to play very well with it.

i want to add to this statement that me pinging 60 to new york from maryland is pretty bad. i ping 16 to new jersey (t4). i wouldnt be surprised if someone like ex or adren or anyone else who lives just a little more out west pinged more than 100.

yea i'm gonna need a screenshot on that. i never seen you ping less than 20. maybe 30 to 40.

[fdrjk]

lol seriously? everybody knows i ping less than 20 on t4, but here you go anyway

unless my connection is really fucking up like it is now and i ping more than i normally do, so this is from a demo i had recorded a couple days ago.



and heres a tracert to your server, which isnt that far away from t4 geographically.

[Golgo13]

well looking at the tracert there is a blip in the middle of the trace. i don't know what that is attributed to. the hop at the last interval could be attributed to my router. i don't know. as for the 20 ping , i keep forgetting because you change names all the time.

so i don't remember the pings. geographically, t4 is closer than NewYork.  also i heard that congested cities are the worst to host servers on. so i think it's verizons DSL network structure. cable connections spike alot also. (i don't get spiking on DSL) even if it's alot slower.

[fdrjk]

for your information i ping the same and maybe a little lower to claire's server in new york, mostly because his server is a lot better and more stable than yours

[Golgo13]

having a server that is paid for is undeniably advantageous. oh well.

[ex]

Dude, why don't you just ask quadz for a NY server?  Tourney4 and t4-noalias are in NY.  He could probably throw up another one for you there since you don't wanna ping like shit to Texas.