dont know what to do next.

[Martie07]

Ok, my Internet was fine when it was run completly by telewest and now something has gone seriously wrong.

Im getting 25-50% loss on packets, even to my modem!. i know what most of you will be thinking, that its my pc. Well, ive tried it on my Windows XP OS, Vista and my Linux centos os. (same pc partitioned).

I called virgin media and they suggested my cat6e network cable was messed up, so i tried a different one. pings to my modem can be anything from <1ms to 49. i have a Webstar DPX100 on a 4Mb service.

What i dont understand is also the sudden rise in ping times, i used to get 12-13 ping to my servers i own in london, i now get 38. its completly random and will be good for one second and horrible the next. Im going to attach a screenshot of some pings to my servers. I really dont know what to tell virgin because they always say its my computer or the issue is normal. Here is some infomation.

Tested Operating systems: Linux Centos, Windows XP, Vista
Network hookup: ethernet rj45 cat6e
Modem: DPX100
Location: Westbromwitch, Sandwell-urb01
Multiple Network cards used for testing.

Id like to change my modem as i really feel there is something wrong with it, ive had it like 4 years and its never acted like this before but it is now.... Picture #3 is actually my cable modem ip adress i pinged.

You guys think its worth calling virgin? i hate how they talk to me like im an idiot :(

ADMIN EDIT - (Russ) IMAGES WITH IP ADDRESS REMOVED

[Martie07]

My modem log

Time Level Description
2007-02-21 02:40:02 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-02-21 02:16:56 information Ignore SW upgrade via provisioning: same image!
2007-02-21 02:16:54 notice Interface index:4 LinkUp
2007-02-21 02:16:54 notice Interface index:3 LinkUp
2007-02-21 02:16:54 notice Interface index:2 LinkUp
2007-02-21 02:16:54 notice SNMP COLD_START(SNMP Nmaccess mode)
2007-02-21 02:16:54 notice Cable Modem Status set to Registration Complete
2007-02-21 02:16:54 information Received REG-RSP from CMTS
2007-02-21 02:16:53 information Sending Registration Request
2007-02-21 02:16:53 information Processing Configuration File
2007-02-21 00:48:33 information DHCP: IP complete
2007-02-21 00:48:33 warning DHCP WARNING - Non-critical field invalid in response
2007-02-21 00:48:33 warning DHCP WARNING - Non-critical field invalid in response
2007-02-21 00:48:32 debug DHCP_coldstart() successfully
2007-02-21 00:48:31 information Beginning ranging process. Initial Power=35.00 dBmV
2007-02-21 00:48:31 information Got a map with the new UCD change count, and changed upstream parms
2007-02-21 00:48:26 information Sync recovery loop is locked
2007-02-21 00:48:22 information Scan Downstream Frequency...
2007-02-21 00:48:20 error BPI FLASH: The Mfg CA certificate not found!
2007-02-21 00:48:26 information Ignore SW upgrade via provisioning: same image!
2007-02-21 00:48:24 notice Interface index:4 LinkUp
2007-02-21 00:48:24 notice Interface index:3 LinkUp
2007-02-21 00:48:24 notice Interface index:2 LinkUp
2007-02-21 00:48:24 notice SNMP COLD_START(SNMP Nmaccess mode)
2007-02-21 00:48:24 notice Cable Modem Status set to Registration Complete
2007-02-21 00:48:24 information Received REG-RSP from CMTS
2007-02-21 00:48:23 information Sending Registration Request
2007-02-21 00:48:23 information Processing Configuration File
2007-02-20 23:51:14 information DHCP: IP complete
2007-02-20 23:51:14 warning DHCP WARNING - Non-critical field invalid in response
2007-02-20 23:51:14 warning DHCP WARNING - Non-critical field invalid in response
2007-02-20 23:51:14 debug DHCP_coldstart() successfully
2007-02-20 23:51:12 information Beginning ranging process. Initial Power=35.00 dBmV
2007-02-20 23:51:12 information Got a map with the new UCD change count, and changed upstream parms
2007-02-20 23:51:09 information Sync recovery loop is locked
2007-02-20 23:51:05 information Scan Downstream Frequency...
2007-02-20 23:51:03 error BPI FLASH: The Mfg CA certificate not found!
2007-02-20 22:12:02 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-02-20 21:23:36 warning DHCP RENEW WARNING - Field invalid in response
2007-02-20 21:23:36 warning DHCP RENEW WARNING - Field invalid in response
2007-02-20 21:23:36 warning DHCP RENEW WARNING - Field invalid in response
2007-02-20 14:39:14 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-02-20 12:48:21 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-02-19 22:27:36 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-02-19 19:46:01 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-02-19 16:22:32 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-02-18 21:23:29 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-02-18 20:49:03 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-02-18 15:11:35 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-02-18 15:11:34 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out

I forgot to add the reaso i am so fedup with my pings are because i am a gamer and also own a gameserver company so i easily get fedup. Abnother thing i have thought about is getting internet access from my servers using an ADSL setup. anyone know how to go about this for my own use?

Thanks in advance!!

[The Jackal]

Abnother thing i have thought about is getting internet access from my servers using an ADSL setup. anyone know how to go about this for my own use?

Thanks in advance!!

Now why didn't I think of that instead of being stuck with this telewest / VM crap. :rolleyes:

Then again do you really want a single point of failure for not only your home connection but also your game host ?

Best have a host(s) in telehouse and host(s) elsewhere like cold harbour etc both on primary transits. Think I'll utilize this too.

[Martie07]

Well my Linux servers are in IP House and my windows are in Redbus. i never thought about it because i dont know how its done. any ideas?

Id keep my telewest line and use my private adsl line for gaming.

[The Jackal]

ps u're internal lan pings look bad test it thoroughly by disconnecting the router and placing a machine on that cat6 cable and see what the pings are like.

For me personally I have also experienced similar fluctuations ie pinging the cable modem but this tends to happen during peak hours - it's as if the cable modem exhibits signs of overloading.

---------- Post added at 05:42 ---------- Previous post was at 05:40 ----------

Well my Linux servers are in IP House and my windows are in Redbus. i never thought about it because i dont know how its done. any ideas?

Ask your colo master if they have links into BTs exchange/pop.

[Martie07]

no routor, direct connected :)

[Toilet-Duck]

Getting the exact same problem here in Tyne And Wear since a few weeks ago, used to have a stable ping of 15 and below now getting pings of 28 - 45..

I also notice loss and choke when playing games such as cs 1.6, however after around 11pm my pings go back to a stable 15 ping with no loss and choke :confused:....

[Martie07]

just called VM and they admitted their switch down the bottom of the street is overloaded, because some users are hammering their uploads and causing really high latency.

they also said they dont know if/when they are going to fix it so now looking for alternatives.

[Martie07]

i have been pinging my modem and been getting ping anything up to 40ms again. this time it wasnt "192.168.100.1" IP. it was the actual cable modem ip beginning with 10.*. Is this a problem or normal when you ping the true IP?

EDIT: im trying to use my STB as a modem to rule out my normal modem as the issue but i cant get connectivity. im guessing this is because of a MAC address issue? DHCP is set to return path.

[janipewter]

this time it wasnt "192.168.100.1" IP. it was the actual cable modem ip beginning with 10.*. Is this a problem or normal when you ping the true IP?

The 10.* IP isn't your cable modem, it's the ubr I think.

[Martie07]

i got it off my modem webstats page. said cable modem ip, but i guess it could be that?

[janipewter]

Cable modem IP is usually 192.168.100.1 isn't it?

[Martie07]

thats what i thought, and thats how i access it so it has to be. just dont know what the 10.* ip is on my stats page.

[Martie07]

Pings are a hell of alot better, but its early in the morning so it cant be my modem, must be congestion. should i worry about all those modem errors?

[cybernetic_tiger]

thats what i thought, and thats how i access it so it has to be. just dont know what the 10.* ip is on my stats page.

The 10. address on your status page is the external IP address of your cable modem, this is the address used by TW to connect to your modem. If you are pinging the cable modem from your PC you should ping 192.168.100.1 this will rule out the WAN. If your pings are still eratic try removing the coax and retesting.

As for the ADSL, you would need to be setup as an OLO within BTW (http://www.btwholesale.com) and setup an interconnect route (or more than one for resiliency) you will also need a radius server for authentication and to assign DHCP addresses and also a router which will be able to setup the PPTP / VPDN session.

Another option is to get business ADSL from TW (the routers that handle ADSL sessions are in London) and as such you would get pretty much the same result as going the ADSL route yourself but you will still have the lag of the BT network to live with, If you want me to ping your server from the TW core and give you an idea of the lag across the TW portion PM me :-P hehe

[Martie07]

i sent you a PM. im interested in trying this TW ADSL. but that would be VM ADSL right? cant see it on their site sop i will call them.

you said the lag of BT to deal with, you mean if i host my own setup with btwholesale right? as i understand telewest have their own phone lines underground dont they?

[cybernetic_tiger]

i sent you a PM. im interested in trying this TW ADSL. but that would be VM ADSL right? cant see it on their site sop i will call them.

you said the lag of BT to deal with, you mean if i host my own setup with btwholesale right? as i understand telewest have their own phone lines underground dont they?

You can't get ADSL through your TW phone line, you would have to have a BT line installed to take that option. VM ADSL terminates on the NTL network, TW Business ADSL terminates on the TW core network.

[Martie07]

Hmm, ive googled around but i dont know how to get TW ADSL.

[MikeyB]

Hmm, ive googled around but i dont know how to get TW ADSL.

http://allyours.virginmedia.com/html/internet/noncable.html

[Martie07]

thought that was different from the Telewest business adsl? sounded like he was talking about 2 different services.

Right now my internet is fine, just did some traces to my server, and the the UBR i am on.

Pinging 193.238.*.* with 32 bytes of data:

Reply from 193.238.*.*: bytes=32 time=13ms TTL=121
Reply from 193.238.*.*: bytes=32 time=12ms TTL=121
Reply from 193.238.*.*: bytes=32 time=13ms TTL=121
Reply from 193.238.*.*: bytes=32 time=12ms TTL=121
Reply from 193.238.*.*: bytes=32 time=18ms TTL=121
Reply from 193.238.*.*: bytes=32 time=18ms TTL=121
Reply from 193.238.*.*: bytes=32 time=13ms TTL=121
Reply from 193.238.*.*: bytes=32 time=12ms TTL=121
Reply from 193.238.*.*: bytes=32 time=17ms TTL=121
Reply from 193.238.*.*: bytes=32 time=14ms TTL=121

Ping statistics for 193.238.*.*:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 18ms, Average = 14ms

Pinging ubr01-sa.blueyonder.co.uk [62.31.176.254] with 32 bytes of data:

Reply from 62.31.176.254: bytes=32 time=6ms TTL=255
Reply from 62.31.176.254: bytes=32 time=7ms TTL=255
Reply from 62.31.176.254: bytes=32 time=6ms TTL=255
Reply from 62.31.176.254: bytes=32 time=10ms TTL=255
Reply from 62.31.176.254: bytes=32 time=7ms TTL=255
Reply from 62.31.176.254: bytes=32 time=6ms TTL=255
Reply from 62.31.176.254: bytes=32 time=6ms TTL=255
Reply from 62.31.176.254: bytes=32 time=7ms TTL=255
Reply from 62.31.176.254: bytes=32 time=13ms TTL=255
Reply from 62.31.176.254: bytes=32 time=6ms TTL=255

Ping statistics for 62.31.176.254:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 13ms, Average = 7ms

Good ping to the UBR also. going to see what its like at around 12/1pm.

[Toto]

Cable modem IP is usually 192.168.100.1 isn't it?

No, thats a router IP address, your CM will start with a 10.

[Martie07]

5:45pm

ping 193.238.*.* -n 10

Pinging 193.238.*.* with 32 bytes of data:

Reply from 193.238.*.*: bytes=32 time=13ms TTL=121
Reply from 193.238.*.*: bytes=32 time=28ms TTL=121
Reply from 193.238.*.*: bytes=32 time=24ms TTL=121
Reply from 193.238.*.*: bytes=32 time=23ms TTL=121
Reply from 193.238.*.*: bytes=32 time=23ms TTL=121
Reply from 193.238.*.*: bytes=32 time=19ms TTL=121
Reply from 193.238.*.*: bytes=32 time=55ms TTL=121
Reply from 193.238.*.*: bytes=32 time=23ms TTL=121
Reply from 193.238.*.*: bytes=32 time=39ms TTL=121
Reply from 193.238.*.*: bytes=32 time=17ms TTL=121

Ping statistics for 193.238.*.*:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 55ms, Average = 26ms

ping ubr01-sa.blueyonder.co.uk -n 10

Pinging ubr01-sa.blueyonder.co.uk [62.31.176.254] with 32 bytes of data:

Reply from 62.31.176.254: bytes=32 time=10ms TTL=255
Reply from 62.31.176.254: bytes=32 time=13ms TTL=255
Reply from 62.31.176.254: bytes=32 time=8ms TTL=255
Reply from 62.31.176.254: bytes=32 time=16ms TTL=255
Reply from 62.31.176.254: bytes=32 time=6ms TTL=255
Reply from 62.31.176.254: bytes=32 time=24ms TTL=255
Reply from 62.31.176.254: bytes=32 time=8ms TTL=255
Reply from 62.31.176.254: bytes=32 time=19ms TTL=255
Reply from 62.31.176.254: bytes=32 time=17ms TTL=255
Reply from 62.31.176.254: bytes=32 time=30ms TTL=255

Ping statistics for 62.31.176.254:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 30ms, Average = 15ms

[Graham M]

No, thats a router IP address, your CM will start with a 10.

The CM can be accessed by the 192.168.*.* address

[cybernetic_tiger]

thought that was different from the Telewest business adsl? sounded like he was talking about 2 different services.



You are correct they are two different services, I think you would be better off with your CM than with ADSL much lower ping times and lower contention ratio but if you want to look into a business line call 0800 953 2800 and ask to speak to sales.

[Martie07]

well i get up to 100ms response to london in the daytime, i dont see how adsl can be much worse?

[The Jackal]

well i get up to 100ms response to london in the daytime, i dont see how adsl can be much worse?

On an idle connection ?

Maybe you have a signal/cable issue. A faulty coax cable can lose 6db which was the case when an engineer came round to my place the other day - seems like I must have snagged the coax at some point :erm:

[cybernetic_tiger]

I have just tested your connection Martie07 and utilisation is over 94% for your upstream, I have located the heavy user and am taking steps to remove them from the NW.

[Martie07]

Thank you Cybernetic.

Here is my pings right now around 1:45pm

ping 193.238.*.* -n 10

Pinging 193.238.*.* with 32 bytes of data:

Reply from 193.238.*.*: bytes=32 time=54ms TTL=121
Reply from 193.238.*.*: bytes=32 time=48ms TTL=121
Reply from 193.238.*.*: bytes=32 time=52ms TTL=121
Reply from 193.238.*.*: bytes=32 time=43ms TTL=121
Reply from 193.238.*.*: bytes=32 time=96ms TTL=121
Reply from 193.238.*.*: bytes=32 time=57ms TTL=121
Reply from 193.238.*.*: bytes=32 time=56ms TTL=121
Reply from 193.238.*.*: bytes=32 time=115ms TTL=121
Reply from 193.238.*.*: bytes=32 time=54ms TTL=121
Reply from 193.238.*.*: bytes=32 time=89ms TTL=121

Ping statistics for 193.238.*.*:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 115ms, Average = 66ms


ping bbc.co.uk -n 10

Pinging bbc.co.uk [212.58.224.131] with 32 bytes of data:

Reply from 212.58.224.131: bytes=32 time=71ms TTL=119
Reply from 212.58.224.131: bytes=32 time=60ms TTL=119
Reply from 212.58.224.131: bytes=32 time=66ms TTL=119
Reply from 212.58.224.131: bytes=32 time=97ms TTL=119
Reply from 212.58.224.131: bytes=32 time=174ms TTL=119
Reply from 212.58.224.131: bytes=32 time=59ms TTL=119
Reply from 212.58.224.131: bytes=32 time=116ms TTL=119
Reply from 212.58.224.131: bytes=32 time=179ms TTL=119
Reply from 212.58.224.131: bytes=32 time=79ms TTL=119
Reply from 212.58.224.131: bytes=32 time=43ms TTL=119

Ping statistics for 212.58.224.131:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 179ms, Average = 94ms

[cybernetic_tiger]

Change made at 14:48, please retest...

[Martie07]

so far its a hell of alot better. getting 12/14ms average, spikes to 27 but its ok.

I will see what its like tomorrow daytime. what change did you make cybernetic_tiger? PM me if possible.

8:45pm ish

ping 193.238.*.* -n 10

Pinging 193.238.*.* with 32 bytes of data:

Reply from 193.238.*.*: bytes=32 time=14ms TTL=121
Reply from 193.238.*.*: bytes=32 time=15ms TTL=121
Reply from 193.238.*.*: bytes=32 time=19ms TTL=121
Reply from 193.238.*.*: bytes=32 time=22ms TTL=121
Reply from 193.238.*.*: bytes=32 time=19ms TTL=121
Reply from 193.238.*.*: bytes=32 time=21ms TTL=121
Reply from 193.238.*.*: bytes=32 time=14ms TTL=121
Reply from 193.238.*.*: bytes=32 time=15ms TTL=121
Reply from 193.238.*.*: bytes=32 time=15ms TTL=121
Reply from 193.238.*.*: bytes=32 time=14ms TTL=121

Ping statistics for 193.238.*.*:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 22ms, Average = 16ms


ping ubr01-sa.blueyonder.co.uk -n 10

Pinging ubr01-sa.blueyonder.co.uk [62.31.176.254] with 32 bytes of data:

Reply from 62.31.176.254: bytes=32 time=8ms TTL=255
Reply from 62.31.176.254: bytes=32 time=17ms TTL=255
Reply from 62.31.176.254: bytes=32 time=7ms TTL=255
Reply from 62.31.176.254: bytes=32 time=10ms TTL=255
Reply from 62.31.176.254: bytes=32 time=7ms TTL=255
Reply from 62.31.176.254: bytes=32 time=9ms TTL=255
Reply from 62.31.176.254: bytes=32 time=17ms TTL=255
Reply from 62.31.176.254: bytes=32 time=6ms TTL=255
Reply from 62.31.176.254: bytes=32 time=7ms TTL=255
Reply from 62.31.176.254: bytes=32 time=7ms TTL=255

Ping statistics for 62.31.176.254:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 17ms, Average = 9ms

Thanks alot, will keep you posted on how its going.

[Martie07]

cybernetic_tiger seems to have fixed it! thanks alot man!

:)

[NTLVictim]

Now, all we need to do is clone Cyber and distribute him/her across all of VM's customer service departments, and we'll be made....

[The Jackal]

Well my Linux servers are in IP House and my windows are in Redbus. i never thought about it because i dont know how its done. any ideas?

Id keep my telewest line and use my private adsl line for gaming.


Did you look into this option ?

I've thought I'd look into it today and learned about the in and outs of what is involved and can if I want set myself up to sell adsl - albeit quality ADSL routed directing from a 1st tier transit.

CRC-3RR0R Broadband coming soon to a store near you.
Any takers ?