View Full Version : Need a favour ! Pings to the cable modem
The Jackal
10-02-2007, 01:01
Can someone provide me a sample set of pings to 192.168.100.1 preferably via a machine connected as close as possible to cable modem.
I may have missed the boat now as it appears that the Cable Network has become less loaded but earlier on I was seeing erratic pings to the cable modem !
Reminiscent to those seen on stressed hardware.
It should be a relatively constant hop.
64 bytes from 192.168.100.1: icmp_seq=146 ttl=63 time=2.64 ms
64 bytes from 192.168.100.1: icmp_seq=147 ttl=63 time=2.53 ms
64 bytes from 192.168.100.1: icmp_seq=148 ttl=63 time=2.58 ms
64 bytes from 192.168.100.1: icmp_seq=149 ttl=63 time=2.54 ms
64 bytes from 192.168.100.1: icmp_seq=150 ttl=63 time=2.53 ms
64 bytes from 192.168.100.1: icmp_seq=151 ttl=63 time=2.52 ms
64 bytes from 192.168.100.1: icmp_seq=152 ttl=63 time=2.52 ms
64 bytes from 192.168.100.1: icmp_seq=153 ttl=63 time=2.55 ms
64 bytes from 192.168.100.1: icmp_seq=154 ttl=63 time=2.54 ms
64 bytes from 192.168.100.1: icmp_seq=155 ttl=63 time=2.55 ms
64 bytes from 192.168.100.1: icmp_seq=156 ttl=63 time=2.53 ms
64 bytes from 192.168.100.1: icmp_seq=157 ttl=63 time=2.65 ms
64 bytes from 192.168.100.1: icmp_seq=158 ttl=63 time=2.54 ms
64 bytes from 192.168.100.1: icmp_seq=159 ttl=63 time=2.56 ms
64 bytes from 192.168.100.1: icmp_seq=160 ttl=63 time=2.52 ms
64 bytes from 192.168.100.1: icmp_seq=161 ttl=63 time=8.14 ms
64 bytes from 192.168.100.1: icmp_seq=162 ttl=63 time=2.55 ms
64 bytes from 192.168.100.1: icmp_seq=163 ttl=63 time=2.54 ms
64 bytes from 192.168.100.1: icmp_seq=164 ttl=63 time=2.54 ms
64 bytes from 192.168.100.1: icmp_seq=165 ttl=63 time=2.54 ms
64 bytes from 192.168.100.1: icmp_seq=166 ttl=63 time=2.57 ms
64 bytes from 192.168.100.1: icmp_seq=167 ttl=63 time=2.66 ms
64 bytes from 192.168.100.1: icmp_seq=168 ttl=63 time=2.54 ms
---------- Post added at 01:01 ---------- Previous post was at 00:59 ----------
Oh well we've missed the boat and the network is running a bit more fluid now... albeit at 1am...
root@ultra:~# ping www.bbc.co.uk
PING www.bbc.net.uk (212.58.224.35) 56(84) bytes of data.
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=1 ttl=247 time=12.4 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=2 ttl=247 time=15.5 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=3 ttl=247 time=20.8 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=4 ttl=247 time=14.5 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=5 ttl=247 time=12.0 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=6 ttl=247 time=28.0 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=7 ttl=247 time=25.1 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=8 ttl=247 time=12.7 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=9 ttl=247 time=12.5 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=10 ttl=247 time=17.8 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=11 ttl=247 time=22.1 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=12 ttl=247 time=15.5 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=13 ttl=247 time=16.0 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=14 ttl=247 time=13.1 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=15 ttl=247 time=17.1 ms
64 bytes from www5.thdo.bbc.co.uk (212.58.224.35): icmp_seq=16 ttl=247 time=16.3 ms
Is that a wireless connection to the modem?
The Jackal
10-02-2007, 11:43
No mate direct via ethernet
---------- Post added at 11:43 ---------- Previous post was at 11:39 ----------
Heres how it looks over wireless an addititional 2ms lag which is acceptable
ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=63 time=4.73 ms
64 bytes from 192.168.100.1: icmp_seq=2 ttl=63 time=4.67 ms
64 bytes from 192.168.100.1: icmp_seq=3 ttl=63 time=4.67 ms
64 bytes from 192.168.100.1: icmp_seq=4 ttl=63 time=4.70 ms
64 bytes from 192.168.100.1: icmp_seq=5 ttl=63 time=4.71 ms
64 bytes from 192.168.100.1: icmp_seq=6 ttl=63 time=4.77 ms
64 bytes from 192.168.100.1: icmp_seq=7 ttl=63 time=4.67 ms
64 bytes from 192.168.100.1: icmp_seq=8 ttl=63 time=4.67 ms
64 bytes from 192.168.100.1: icmp_seq=9 ttl=63 time=4.65 ms
64 bytes from 192.168.100.1: icmp_seq=10 ttl=63 time=4.70 ms
To my modem:
C:\Documents and Settings\X>ping -t 192.168.100.1
Pinging 192.168.100.1 with 32 bytes of data:
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Ping statistics for 192.168.100.1:
Packets: Sent = 51, Received = 51, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 6ms, Average = 2ms
To bbc.co.uk:
C:\Documents and Settings\X>ping -t bbc.co.uk
Pinging bbc.co.uk [212.58.224.131] with 32 bytes of data:
Reply from 212.58.224.131: bytes=32 time=24ms TTL=111
Reply from 212.58.224.131: bytes=32 time=21ms TTL=111
Reply from 212.58.224.131: bytes=32 time=20ms TTL=111
Reply from 212.58.224.131: bytes=32 time=24ms TTL=111
Reply from 212.58.224.131: bytes=32 time=23ms TTL=111
Reply from 212.58.224.131: bytes=32 time=24ms TTL=111
Reply from 212.58.224.131: bytes=32 time=20ms TTL=111
Reply from 212.58.224.131: bytes=32 time=22ms TTL=111
Reply from 212.58.224.131: bytes=32 time=21ms TTL=111
Reply from 212.58.224.131: bytes=32 time=20ms TTL=111
Reply from 212.58.224.131: bytes=32 time=21ms TTL=111
Reply from 212.58.224.131: bytes=32 time=23ms TTL=111
Reply from 212.58.224.131: bytes=32 time=27ms TTL=111
Reply from 212.58.224.131: bytes=32 time=21ms TTL=111
Reply from 212.58.224.131: bytes=32 time=20ms TTL=111
Reply from 212.58.224.131: bytes=32 time=37ms TTL=111
Reply from 212.58.224.131: bytes=32 time=19ms TTL=111
Reply from 212.58.224.131: bytes=32 time=21ms TTL=111
Reply from 212.58.224.131: bytes=32 time=22ms TTL=111
Reply from 212.58.224.131: bytes=32 time=21ms TTL=111
Reply from 212.58.224.131: bytes=32 time=22ms TTL=111
Reply from 212.58.224.131: bytes=32 time=21ms TTL=111
Reply from 212.58.224.131: bytes=32 time=23ms TTL=111
Reply from 212.58.224.131: bytes=32 time=20ms TTL=111
Reply from 212.58.224.131: bytes=32 time=20ms TTL=111
Reply from 212.58.224.131: bytes=32 time=32ms TTL=111
Reply from 212.58.224.131: bytes=32 time=32ms TTL=111
Reply from 212.58.224.131: bytes=32 time=19ms TTL=111
Reply from 212.58.224.131: bytes=32 time=21ms TTL=111
Reply from 212.58.224.131: bytes=32 time=21ms TTL=111
Reply from 212.58.224.131: bytes=32 time=20ms TTL=111
Reply from 212.58.224.131: bytes=32 time=20ms TTL=111
Reply from 212.58.224.131: bytes=32 time=20ms TTL=111
Reply from 212.58.224.131: bytes=32 time=22ms TTL=111
Reply from 212.58.224.131: bytes=32 time=22ms TTL=111
Reply from 212.58.224.131: bytes=32 time=22ms TTL=111
Reply from 212.58.224.131: bytes=32 time=23ms TTL=111
Reply from 212.58.224.131: bytes=32 time=19ms TTL=111
Reply from 212.58.224.131: bytes=32 time=22ms TTL=111
Reply from 212.58.224.131: bytes=32 time=21ms TTL=111
Reply from 212.58.224.131: bytes=32 time=23ms TTL=111
Reply from 212.58.224.131: bytes=32 time=21ms TTL=111
Reply from 212.58.224.131: bytes=32 time=21ms TTL=111
Reply from 212.58.224.131: bytes=32 time=24ms TTL=111
Reply from 212.58.224.131: bytes=32 time=23ms TTL=111
Ping statistics for 212.58.224.131:
Packets: Sent = 45, Received = 45, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 37ms, Average = 22ms
The 2ms to the modem is because it's traveling to a netgear router then down a frozen Cat5e down to the first floor and then into the modem. And yes, the CAT5 is frozen...:disturbed:
The Jackal
10-02-2007, 11:54
thanks Druchii for that. you too have got a couple of spikes.
If you run that same ping to 192.168.100.1 do you see spikes and what is you maximum ?
87 packets transmitted, 87 received, 0% packet loss, time 86210ms
rtt min/avg/max/mdev = 2.511/2.602/3.347/0.150 ms
At the moment the network seems ok and I get rare spikes but when the cable network is saturated I see a hell of a lot of spikes 2ms -> 4ms to some +500ms !
---------- Post added at 11:54 ---------- Previous post was at 11:52 ----------
[/code]The 2ms to the modem is because it's traveling to a netgear router then down a frozen Cat5e down to the first floor and then into the modem. And yes, the CAT5 is frozen...:disturbed:
I think we'll still get 2ms even we connect a 1m cable directly to the cable modem this is the norm value I have been seeing for years.
HOWEVER what is not the norm are these spikes which I have recently identified as being problematic
thanks Druchii for that. you too have got a couple of spikes.
If you run that same ping to 192.168.100.1 do you see spikes and what is you maximum ?
87 packets transmitted, 87 received, 0% packet loss, time 86210ms
rtt min/avg/max/mdev = 2.511/2.602/3.347/0.150 ms
At the moment the network seems ok and I get rare spikes but when the cable network is saturated I see a hell of a lot of spikes 2ms -> 4ms to some +500ms !
---------- Post added at 11:54 ---------- Previous post was at 11:52 ----------
I think we'll still get 2ms even we connect a 1m cable directly to the cable modem this is the norm value I have been seeing for years.
HOWEVER what is not the norm are these spikes which I have recently identified as being problematic
The first ping set was to 192.168.100.1 :) I rarely see spikes to my modem, but to the local UBR i see bad spikes every now and again, then again it's just the normal network congestion as it's pretty rare.
If you want i'll do a quick ping set to the local ubr?
The Jackal
10-02-2007, 11:57
The first ping set was to 192.168.100.1 :) I rarely see spikes to my modem, but to the local UBR i see bad spikes every now and again, then again it's just the normal network congestion as it's pretty rare.
If you want i'll do a quick ping set to the local ubr?
nawwww network is quiet at the moment wont prove nothing a ping set at say 9-10pm this evening would probably show it it better (if you remember that is :)
nawwww network is quiet at the moment wont prove nothing a ping set at say 9-10pm this evening would probably show it it better (if you remember that is :)
I'll set a reminder ;)
EDIT: Better yet, i'll set a batch script to fire off at 9pm =D
The Jackal
10-02-2007, 12:02
Gave me an idea :
Here are the pings to my UBR from home
PING 62.30.144.220 (62.30.144.220) 56(84) bytes of data.
64 bytes from 62.30.144.220: icmp_seq=1 ttl=254 time=14.4 ms
64 bytes from 62.30.144.220: icmp_seq=2 ttl=254 time=12.4 ms
64 bytes from 62.30.144.220: icmp_seq=3 ttl=254 time=12.9 ms
64 bytes from 62.30.144.220: icmp_seq=4 ttl=254 time=27.4 ms
64 bytes from 62.30.144.220: icmp_seq=5 ttl=254 time=43.5 ms
64 bytes from 62.30.144.220: icmp_seq=6 ttl=254 time=12.0 ms
64 bytes from 62.30.144.220: icmp_seq=7 ttl=254 time=9.73 ms
64 bytes from 62.30.144.220: icmp_seq=8 ttl=254 time=16.1 ms
64 bytes from 62.30.144.220: icmp_seq=9 ttl=254 time=21.5 ms
64 bytes from 62.30.144.220: icmp_seq=10 ttl=254 time=8.30 ms
64 bytes from 62.30.144.220: icmp_seq=11 ttl=254 time=12.2 ms
64 bytes from 62.30.144.220: icmp_seq=12 ttl=254 time=9.17 ms
64 bytes from 62.30.144.220: icmp_seq=13 ttl=254 time=13.0 ms
64 bytes from 62.30.144.220: icmp_seq=14 ttl=254 time=47.6 ms
64 bytes from 62.30.144.220: icmp_seq=15 ttl=254 time=11.3 ms
64 bytes from 62.30.144.220: icmp_seq=16 ttl=254 time=16.0 ms
64 bytes from 62.30.144.220: icmp_seq=17 ttl=254 time=15.1 ms
64 bytes from 62.30.144.220: icmp_seq=18 ttl=254 time=46.5 ms
64 bytes from 62.30.144.220: icmp_seq=19 ttl=254 time=12.6 ms
64 bytes from 62.30.144.220: icmp_seq=20 ttl=254 time=12.6 ms
64 bytes from 62.30.144.220: icmp_seq=21 ttl=254 time=18.2 ms
Here are the pings to the UBR from a datacentre in London :
64 bytes from 62.30.144.220: icmp_seq=1 ttl=244 time=3.30 ms
64 bytes from 62.30.144.220: icmp_seq=2 ttl=244 time=2.78 ms
64 bytes from 62.30.144.220: icmp_seq=3 ttl=244 time=2.85 ms
64 bytes from 62.30.144.220: icmp_seq=4 ttl=244 time=3.46 ms
64 bytes from 62.30.144.220: icmp_seq=5 ttl=244 time=3.23 ms
64 bytes from 62.30.144.220: icmp_seq=6 ttl=244 time=3.27 ms
64 bytes from 62.30.144.220: icmp_seq=7 ttl=244 time=3.39 ms
64 bytes from 62.30.144.220: icmp_seq=8 ttl=244 time=3.57 ms
64 bytes from 62.30.144.220: icmp_seq=9 ttl=244 time=3.00 ms
64 bytes from 62.30.144.220: icmp_seq=10 ttl=244 time=3.17 ms
64 bytes from 62.30.144.220: icmp_seq=11 ttl=244 time=2.81 ms
64 bytes from 62.30.144.220: icmp_seq=12 ttl=244 time=3.34 ms
64 bytes from 62.30.144.220: icmp_seq=13 ttl=244 time=3.21 ms
64 bytes from 62.30.144.220: icmp_seq=14 ttl=244 time=3.40 ms
64 bytes from 62.30.144.220: icmp_seq=15 ttl=244 time=3.15 ms
64 bytes from 62.30.144.220: icmp_seq=16 ttl=244 time=2.84 ms
64 bytes from 62.30.144.220: icmp_seq=17 ttl=244 time=3.11 ms
64 bytes from 62.30.144.220: icmp_seq=18 ttl=244 time=2.93 ms
64 bytes from 62.30.144.220: icmp_seq=19 ttl=244 time=3.06 ms
64 bytes from 62.30.144.220: icmp_seq=20 ttl=244 time=2.90 ms
64 bytes from 62.30.144.220: icmp_seq=21 ttl=244 time=3.23 ms
64 bytes from 62.30.144.220: icmp_seq=22 ttl=244 time=3.07 ms
Odd, it's faster to hit the UBR from outside the network compared to from the inside...
The Jackal
10-02-2007, 12:06
Odd, it's faster to hit the UBR from outside the network compared to from the inside...
Not odd at all it just goes to show where the bottleneck is : Internal
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Maybe I should take a mattress/kettle and start living in a datacenter ? :rolleyes:
Not odd at all it just goes to show where the bottleneck is : Internal
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Maybe I should take a mattress/kettle and start living in a datacenter ? :rolleyes:
What are you running through to get to the UBR then? How many routers/switches/miles of CAT5 (ok, not miles but still :p:)
Datacentre would be nice and warm though... :p:
The Jackal
10-02-2007, 12:16
What are you running through to get to the UBR then? How many routers/switches/miles of CAT5 (ok, not miles but still :p:)
What do you mean ? How do I find out ?
Interestingly I can't seem to log onto the cable modem :rolleyes: http://192.168.100.1/
Hmmmm could it be a fault with my cable modem ? I have had it for like 5 odd years
What do you mean ? How do I find out ?
Interestingly I can't seem to log onto the cable modem :rolleyes: http://192.168.100.1/
Hmmmm could it be a fault with my cable modem ? I have had it for like 5 odd years
Do you have a proxy specified? If so, turn it off and see if you can access it. You could also unplug it for a minute or two, and then power it up again :) Might clear something with it and make it a happy bunny, or, it could kill it i guess in the very worst case...
I meant in your own home, how many til it hits the modem itself, generally it's one leap from the modem to the UBR.
Interestingly I can't seem to log onto the cable modem :rolleyes: http://192.168.100.1/
Hmmmm could it be a fault with my cable modem ? I have had it for like 5 odd years
What happens when you try?
The Jackal
10-02-2007, 12:26
What happens when you try?
Connection timeout :
Anyway I just physically unplugged it and rebooted it and can see the config pages again :
Do these settings look ok ?
Frequency 331000000 Hz Locked
Signal to Noise Ratio 36 dB
Power Level -8 dBmV
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
Upstream Value
Channel ID 2
Frequency 21300000 Hz Ranged
Power Level 44 dBmV
They should be fine, here is mine for comparison:
Frequency 331000000 Hz
Signal To Noise Ratio 39.0 dB
Power Level 0.4 dBmV
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
Upstream Value
Channel ID 3
Frequency 34000000 Hz
Power 46.0 dBmV
cybernetic_tiger
10-02-2007, 13:42
You must remember that when pinging your uBR that ICMP echoes have the lowest priority possible and as such will be dropped / delayed in high traffic periods or if your seg is over subscribed.
However... this is NOT true for your cable modem, pings should always be fairly consistant especially if you are hardwired. Are you using a router and if so what type? And as has been asked before; how are you physically connected to the cable modem?
What other symptoms are you experiencing? What other testing have you carried out other than ping tests?
Also what cable modem do you have?
The Jackal
11-02-2007, 02:03
You must remember that when pinging your uBR that ICMP echoes have the lowest priority possible and as such will be dropped / delayed in high traffic periods or if your seg is over subscribed.
However... this is NOT true for your cable modem, pings should always be fairly consistant especially if you are hardwired. Are you using a router and if so what type? And as has been asked before; how are you physically connected to the cable modem?
What other symptoms are you experiencing? What other testing have you carried out other than ping tests?
Also what cable modem do you have?
Yay someone in the know ! :)
Thanks for highlighting the QoS aspect. :tu:
" However... this is NOT true for your cable modem, pings should always be fairly consistant especially if you are hardwired. "
And yes yes yes. That is the strange bit I have been used to consistent pings to the router until recently when I was digging for a ' cause ' to some of my external network problems I started probing my internal network and was suprised to see spikes to the cable modem during peak time *STRANGE*.
To answer your questions.
1 - my router is connected to the cable modem via a dedicated length of cat5e (I'm going to go downstairs now and unplug it and use a different host and different cable to see if I experience the same problems)
2 - Router itself is hand built by myself and is around 4 years old. Its basically an embedded linux board with 3 eth ports. Primary OS is linux based which I built by taking aspects of busybox and merging them / recompiling with glibc2.2 base (an old redhat version). The OS is sucked off a piece of compact flash and straight into physical memory where I have written Shmop and Semaphore based applications and monitors. All in all a solid piece of kit.
3 - Then again it could be the router/cable so I'm off to disconnect it :)
janipewter
11-02-2007, 08:35
Frequency 339000000 Hz Locked
Signal to Noise Ratio 37 dB
Power Level 14 dBmV
Channel ID 1
Frequency 25800000 Hz
Ranged Power Level 44 dBmV
I wonder why it won't let me use the 331000000Hz frequency anymore, it used to work fine but now when I set it to that and reboot the modem, it fails to boot and then reboots again, back to 339000000Hz. Anyone know what the problem could be?
Edit: why do I have a MUCH higher power level than the other two posters in here?
cybernetic_tiger
11-02-2007, 16:07
Hi janipewter,
Your power level is a bit too high but it does not appear to be affecting SNR, as for the frquency I would not worry too much about that at this point,
If you PM me your postcode and 1st line of your address I will take a look when I get into work tonite, if you would like proof of my employment PM me your E-Mail address and I will send you an e-mail from my nice shiney new @virginmedia.co.uk address,
CT
vBulletin® v3.8.11, Copyright ©2000-2024, vBulletin Solutions Inc.