next »

[Please Support Us!]

Please Support Us!

Please help keep (=WDG=) alive

• Server rules
• Forum rules
• Join us
  
• Clan members
• About the clan
• Server stats
• WDG YouTube Channel
• WDG Downloads
• IRC Webchat

Steam groups:

• WDG community
• WDG clan group
• WDG Battlelog Platoon

Our allies:

• [NuB] TF2 clan
• Velocity Gamers Hub
• Destination Gamer

GoG Links:

• Wix Discord
• Wix IRC channel

TF2 Links:

• Official TF2 Blog
• TF2 Steam Forum
• The Fort 2

October 2025

Mo	Tu	We	Th	Fr	Sa	Su
		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31
	Birthdays
Chaos (40)
	Upcoming Events
Upcoming Birthdays: Chaos (40)

[Cheez]

Right on chaos' advice, I've decided to post here. Basically i'm on virgin, none of my housemates are here atm and I haven't been raping the connection so they shouldn't be throttling me. Anyway, my ping goes crazy (usually in spikes of around 10-20 seconds but its not usually great in between there) This is a traceroute to a UK tf2 server:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Sam>tracert 81.19.221.201

Tracing route to ne1.nervousenergy.co.uk [81.19.221.201]
over a maximum of 30 hops:

  1     2 ms    <1 ms    <1 ms  192.168.1.1
  2   423 ms   267 ms   495 ms  10.11.68.1
  3   350 ms    92 ms    14 ms  aztw-geam-1b-ge142.network.virginmedia.net [80.1
.243.153]
  4   233 ms    15 ms   220 ms  aztw-core-1b-ae0-0.network.virginmedia.net [80.1
.241.13]
  5    77 ms    79 ms    82 ms  brhm-bb-1b-as1-0.network.virginmedia.net [213.10
5.175.161]
  6    46 ms     *      308 ms  winn-bb-1a-so-220-0.network.virginmedia.net [62.
253.188.145]
  7   594 ms    25 ms    22 ms  popl-bb-1b-as5-0.network.virginmedia.net [212.43
.162.194]
  8   218 ms   265 ms   277 ms  popl-tmr-2-ae5-0.network.virginmedia.net [213.10
5.159.6]
  9   388 ms   498 ms   548 ms  tele-ic-2-as0-0.network.virginmedia.net [62.253.
184.6]
 10   672 ms   970 ms  1090 ms  ntl.killercreation.co.uk [212.250.14.18]
 11  1391 ms     *     1715 ms  rt-2-cent.killercreation.co.uk [217.146.94.2]
 12  2094 ms  2125 ms  1818 ms  ne1.nervousenergy.co.uk [81.19.221.201]

Trace complete.

Any advice would be awesome

[claws]

Right on chaos' advice, I've decided to post here. Basically i'm on virgin, none of my housemates are here atm and I haven't been raping the connection so they shouldn't be throttling me. Anyway, my ping goes crazy (usually in spikes of around 10-20 seconds but its not usually great in between there) This is a traceroute to a UK tf2 server:

  1     2 ms    <1 ms    <1 ms  192.168.1.1
  2   423 ms   267 ms   495 ms  10.11.68.1

Hop 2 looks terrible : that's an internal address. How are you connected to your router, what kind of router is it, etc.

[Cheez]

I'm wired up to the router, this is my router: http://homestore.cisco.com/en-us/routers/Linksys-WRT54GL-Wireless-G-Router_stcVVproductId53934619VVcatId552009VVviewprod.htm.
I think the first hop is me to the router? So the wire is no problem but I don't know anything about the other hops tbh. That router is then connected to the virgin modem and that is connected thing in the wall

[Power]

Yeah, the problem will be with the communication between the router and the modem. If you didn't yet, disconnect both of them from power, wait a couple of seconds and reconnect them (modem first would be best). If it doesn't help it might be that one of those two devices is broken. Try going straight into the modem (will need a crossover cable, I believe?) and test it again.

[Cheez]

Did the disconnect and reconnect and its still the same. Haven't got a crossover cable I don't think, might get one if thats what I need. But I should of said, its not this bad all the time, if it was one of the modem or router wouldn't it be bad all the time?

[Power]

Well the problem might very well be with Virgin, but unless you get rid of those horrible ping times to your modem it doesn't matter what happens behind it. Try "ping -t 10.11.68.1" and see if it's consistently bad (you can stop it by pressing CTRL+C).

[Cheez]

It won't let me ping that mate, comes up with 'Request timed out'

[Power]

Hmm might have changed with the reset. Try pinging some internet adress or server again and then do that with the first 10.x.x.x IP that shows up.

[Cheez]

Did another traceroute and the same 10.11.68.1 came up but it still won't let me ping it directly. (Cheers for the help btw mate)

[Power]

Maybe your modem drops all ping requests as a security measure. Well, then try pinging the node after it (or the whole route if that doesn't work either), but with -t added. Basically makes the ping run forever, instead of just four times. If the response time is consistantly that bad it's probably your hardware (or the line makes the modem malfunction in some way).

[Cheez]

This is a ping to the node after:

C:\Users\Sam>ping -t 80.1.243.153

Pinging 80.1.243.153 with 32 bytes of data:
Reply from 80.1.243.153: bytes=32 time=25ms TTL=253
Reply from 80.1.243.153: bytes=32 time=50ms TTL=253
Reply from 80.1.243.153: bytes=32 time=109ms TTL=253
Reply from 80.1.243.153: bytes=32 time=29ms TTL=253
Reply from 80.1.243.153: bytes=32 time=71ms TTL=253
Reply from 80.1.243.153: bytes=32 time=416ms TTL=253
Reply from 80.1.243.153: bytes=32 time=36ms TTL=253
Request timed out.
Reply from 80.1.243.153: bytes=32 time=128ms TTL=253
Reply from 80.1.243.153: bytes=32 time=176ms TTL=253
Reply from 80.1.243.153: bytes=32 time=62ms TTL=253
Reply from 80.1.243.153: bytes=32 time=44ms TTL=253
Reply from 80.1.243.153: bytes=32 time=105ms TTL=253
Reply from 80.1.243.153: bytes=32 time=43ms TTL=253
Reply from 80.1.243.153: bytes=32 time=270ms TTL=253
Reply from 80.1.243.153: bytes=32 time=28ms TTL=253
Reply from 80.1.243.153: bytes=32 time=101ms TTL=253
Reply from 80.1.243.153: bytes=32 time=197ms TTL=253
Reply from 80.1.243.153: bytes=32 time=14ms TTL=253
Reply from 80.1.243.153: bytes=32 time=108ms TTL=253
Reply from 80.1.243.153: bytes=32 time=14ms TTL=253
Reply from 80.1.243.153: bytes=32 time=34ms TTL=253
Reply from 80.1.243.153: bytes=32 time=56ms TTL=253
Reply from 80.1.243.153: bytes=32 time=165ms TTL=253
Reply from 80.1.243.153: bytes=32 time=12ms TTL=253
Reply from 80.1.243.153: bytes=32 time=23ms TTL=253
Reply from 80.1.243.153: bytes=32 time=217ms TTL=253
Reply from 80.1.243.153: bytes=32 time=14ms TTL=253
Reply from 80.1.243.153: bytes=32 time=189ms TTL=253
Reply from 80.1.243.153: bytes=32 time=45ms TTL=253
Reply from 80.1.243.153: bytes=32 time=32ms TTL=253
Reply from 80.1.243.153: bytes=32 time=13ms TTL=253
Reply from 80.1.243.153: bytes=32 time=108ms TTL=253
Reply from 80.1.243.153: bytes=32 time=185ms TTL=253

Ping statistics for 80.1.243.153:
    Packets: Sent = 34, Received = 33, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 416ms, Average = 94ms

[claws]

Woah. Which virgin modem do you have?

[Power]

Yes, still way too jumpy for the first WAN node, but the problem is probably at your modem already. If you can't connect to the modem directly (does it have multiple network slots or just one?) there isn't a whole lot that you could test for faults left. Just to be safe, try a different slot on your router, too (though that is probably not the problem).

I don't know anything about the modem Virgin sends out, but does it have a webserver for configuration on it? Usually reachable by entering its IP in your browser like this http:\\10.11.68.1 (maybe http:\\10.11.68.1:80 but usually not necessary). If there is anything under that adress, see if there are any system logs or error reports accessible.

If the line or the modem is borked there isn't much to do to fix it, unfortunately. Sometimes it helps unplugging the modem from power and phone line over night and let it resync in the next day, but that depends on the technology Virgin uses (helped with one provider and not with another in my case).

[Cheez]

Ambit 256 claws.

[Cheez]

The modem has just the one network slot, think I have tried connecting directly to it before and my internet didn't work. Tried a different slot on the router and as you thought it didn't make a difference. And that address doesn't bring up anything for me power.