Ping problems

Turin · May 23, 2009, 17:33:48

Oh sorry it's a Netgear DG834PN

Rik · May 23, 2009, 17:35:36

I'm not familiar with the firmware for that version, so I don't think the old way of extracting it will work:

Enter this in the browser address bar:

http://192.168.0.1/setup.cgi?todo=debug

which should result in a screen which just says 'Debug enable'.
(That's assuming that you haven't changed the router's IP address from the default).

Then exit from the web interface and open a command-line window. Type:

telnet 192.168.0.1

You should get a BusyBox welcome message to confirm that your telnet connection is established.

Now type:

cat /proc/avalanche/avsar_modem_stats

If this doesn't work, we need someone to help.

Rik · May 23, 2009, 17:37:38

There's a bit more on Kitz, but nothing specific about getting at the error count on the PN:

http://www.kitz.co.uk/routers/netgeardg834_interleaving.htm

Turin · May 23, 2009, 17:39:35

BusyBox v1.00 (2008.08.14-04:05+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# cat /proc/avalanche/avsar_modem_stats
cat: /proc/avalanche/avsar_modem_stats: No such file or directory
#

Rik · May 23, 2009, 17:41:12

Try this command from Kitz:

# adslctl info --stats

which should give you the following info:

Status: Showtime Channel: FAST, (or interleaved).

Turin · May 23, 2009, 17:43:55

Channel:Fast is what i get.

Steve · May 23, 2009, 17:44:39

/usr/sbin/adslctl info --stats on the DG834N

One of the advantages of the DGTeam firmware is that you can also get the adsl stats from the diagnostic page.

http://dgteam.ilbello.com/index.php?pid=6

Rik · May 23, 2009, 17:46:52

OK, that would seem to indicate exchange congestion then. To give you an idea of the sort of effect this can have, I moved to a business package for a month or so, which then gave me priority at the exchange. My ping 'base' went down from 23ms to 19ms, simply because of that priority, and that's on an uncongested exchange.

All I can suggest is that you talk to IDNet on Tuesday to see if they can find any more information about what's happening. They can look at your line and ping you directly, which will give them a better diagnostic than my wild guesses.

Rik · May 23, 2009, 17:47:05

Thanks, Steve.

Turin · May 23, 2009, 17:51:05

When this has happened before i've checked my exchange and it tell's me it's uncongested.That's what has got me so baffled.
Thanks for the input Steve

Rik · May 23, 2009, 17:53:27

Quote from: Turin on May 23, 2009, 17:51:05
When this has happened before i've checked my exchange and it tell's me it's uncongested.

The problem is that most of the online checkers are out of date, BT is slapdash at updating the dataa, and the sites which access it are getting out of date information.

Turin · May 23, 2009, 17:56:49

Quote from: Rik on May 23, 2009, 17:53:27
The problem is that most of the online checkers are out of date, BT is slapdash at updating the dataa, and the sites which access it are getting out of date information.

Good old BT strikes again

Is there anything more that can be done if that's the case?

Rik · May 23, 2009, 18:00:50

Not from here, it really needs IDNet to check the line and see what information they can get from BT. We can help with local wiring issues or router configuration, but we don't have access to IDNet's systems (probably just as well, I'd only break something.

)

Turin · May 23, 2009, 18:09:37

ok Rik,thanks for your time.I'll post back if it get's sorted.

Rik · May 23, 2009, 18:11:21

Thanks, I'll be interested to hear.

Turin · Jun 04, 2009, 08:49:27

Hey again,
well after talking with support who contacted BT.There is no problem with my line and I might see my speed drop at peak times.So i decided to put it down to contention and just keep a close eye on it.Ping's have improved lately but I'm still getting huge fluctuation's and not always at peak times

So I'm still in the dark really.
Just ran a speed test...

Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 5952 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 5500 kbps
Actual IP throughput achieved during the test was - 4692 kbps

As thing's have improved a bit I'm now just crossing my finger's it will keep improving

Gary · Jun 04, 2009, 09:14:46

Just did a test, now two days ago my throughput was in the region of 6800 (wifi) on this laptop

Today Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 2847 kbps

If you wish to discuss these results please contact your ISP.

Nothing has changed, unless its exchange congestion but thats one massive loss of throughput

I have tested at the master socket with similar results a few weeks ago all was fine.
Tomorrrow it could be back up again it varies wildly across the day

edit: exchange is not congested all reports show green for now.

Rik · Jun 04, 2009, 09:52:45

Talk to support, Gary. The online checkers are often completely wrong on congestion.

Gary · Jun 04, 2009, 10:10:35

Quote from: Rik on Jun 04, 2009, 09:52:45
Talk to support, Gary. The online checkers are often completely wrong on congestion.

Will do Rik

wecpcs · Jun 04, 2009, 16:57:08

Quote from: Gary on Jun 04, 2009, 09:14:46
Just did a test, now two days ago my throughput was in the region of 6800 (wifi) on this laptop

Today Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 2847 kbps

If you wish to discuss these results please contact your ISP.

Nothing has changed, unless its exchange congestion but thats one massive loss of throughput I have tested at the master socket with similar results a few weeks ago all was fine.
Tomorrrow it could be back up again it varies wildly across the day

edit: exchange is not congested all reports show green for now.

I have exactly the same DSL connection and profile as you and I was getting similar throughput speeds with a doubling of my ping, but support have just switched me to GW5 from GW6 and everything is back to normal with even a slightly improved ping.

Colin

Sebby · Jun 04, 2009, 17:36:25

Turin · Jun 08, 2009, 09:51:21

Well crossing my fingers didn't work,this was my connection at 10:30pm yesterday...

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=143ms TTL=59
Reply from 212.69.36.10: bytes=32 time=146ms TTL=59
Reply from 212.69.36.10: bytes=32 time=128ms TTL=59
Reply from 212.69.36.10: bytes=32 time=138ms TTL=59

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 128ms, Maximum = 146ms, Average = 138ms

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=96ms TTL=59
Reply from 212.69.36.10: bytes=32 time=102ms TTL=59
Reply from 212.69.36.10: bytes=32 time=72ms TTL=59
Reply from 212.69.36.10: bytes=32 time=100ms TTL=59

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 102ms, Average = 92ms

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=112ms TTL=59
Reply from 212.69.36.10: bytes=32 time=79ms TTL=59
Reply from 212.69.36.10: bytes=32 time=101ms TTL=59
Reply from 212.69.36.10: bytes=32 time=89ms TTL=59

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 112ms, Average = 95ms

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=52ms TTL=59
Reply from 212.69.36.10: bytes=32 time=62ms TTL=59
Reply from 212.69.36.10: bytes=32 time=61ms TTL=59

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 62ms, Average = 49ms

Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 5952 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 5000 kbps
Actual IP throughput achieved during the test was - 4188 kbps

If you wish to discuss these results please contact your ISP.

I also ran routerstats for a while and got this...

Any ideas?

Rik · Jun 08, 2009, 10:00:15

Your speed doesn't look bad, the RouterStats graph reveals nothing to worry about. If you're on gw6, then drop email a support, or phone them.

Turin · Jun 08, 2009, 10:04:00

I'm on gw5 so i guess i'll leave it

Rik · Jun 08, 2009, 10:05:23

What's your normal ping like? I'm running a range of 21-27ms this morning, average 24ms, also on gw5.