Packetloss, Disconnections, Slow speeds.

[PetFish]

Hey Idnetters,

I am on the ADSL SuperMax Package and apart from the problems when the Olympics were on, I have not had much trouble with my connection until yesterday/today, where I am now getting Packetloss, Disconnections and Slow speeds.

As far as I am aware the has been no change/additions to the equipment in my home.

My router is Netgear DG834G:

DownStream Connection Speed   8128 kbps
UpStream Connection Speed   832 kbps
VPI   0
VCI   38

Port   Status   TxPkts   RxPkts   Collisions   Tx B/s   Rx B/s   Up Time
WAN   PPPoA   302   231   0   187   172   00:03:04

ADSL Link   Downstream   Upstream
Connection Speed   8128 kbps   832 kbps
Line Attenuation   8 db   1.5 db
Noise Margin   6 db   13 db
MTU 1458

Since writing this I have disconnected twice

I have contacted IDNet and they have suggested I change filters, which I have done, as they have done a check on my line and cannot find a problem. My router is also plugged into the master socket, but it is not the type with the dual detatchable face plate. It is a single faceplate.

Below are some tracerts and pings.

[root@localhost ~]# tracert bbc.co.uk
traceroute to bbc.co.uk (212.58.224.131), 30 hops max, 40 byte packets
1  www.routerlogin.com (192.168.0.1)  0.630 ms  0.932 ms  1.233 ms
2  telehouse-gw2-lo1.idnet.net (212.69.63.51)  17.597 ms  18.019 ms  19.775 ms
3  telehouse-gw3-g0-1-400.idnet.net (212.69.63.243)  20.470 ms  20.814 ms  22.360 ms
4  rt-lonap-b.thdo.bbc.co.uk (193.203.5.91)  23.792 ms * *
5  212.58.238.133 (212.58.238.133)  26.719 ms  27.442 ms  28.660 ms
6  rdirwww-vip.thdo.bbc.co.uk (212.58.224.131)  29.402 ms  24.124 ms  25.541 ms

[root@localhost ~]# ping bbc.co.uk
PING bbc.co.uk (212.58.224.131) 56(84) bytes of data.
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=1 ttl=122 time=17.6 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=2 ttl=122 time=22.4 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=3 ttl=122 time=16.1 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=4 ttl=122 time=18.4 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=5 ttl=122 time=36.4 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=6 ttl=122 time=17.2 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=7 ttl=122 time=27.9 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=8 ttl=122 time=21.3 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=9 ttl=122 time=19.2 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=11 ttl=122 time=19.5 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=12 ttl=122 time=16.4 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=13 ttl=122 time=16.2 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=14 ttl=122 time=16.3 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=15 ttl=122 time=19.5 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=16 ttl=122 time=27.5 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=19 ttl=122 time=16.1 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=20 ttl=122 time=30.2 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=21 ttl=122 time=24.6 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=22 ttl=122 time=17.0 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=23 ttl=122 time=24.2 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=24 ttl=122 time=15.7 ms
^C
--- bbc.co.uk ping statistics ---
25 packets transmitted, 21 received, 16% packet loss, time 24782ms
rtt min/avg/max/mdev = 15.731/20.986/36.458/5.508 ms

[root@localhost ~]# ping idnet.net
PING idnet.net (212.69.36.10) 56(84) bytes of data.
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=1 ttl=59 time=40.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=2 ttl=59 time=47.2 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=3 ttl=59 time=34.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=4 ttl=59 time=49.1 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=5 ttl=59 time=43.0 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=7 ttl=59 time=50.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=8 ttl=59 time=51.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=9 ttl=59 time=42.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=10 ttl=59 time=49.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=11 ttl=59 time=47.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=12 ttl=59 time=50.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=13 ttl=59 time=42.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=14 ttl=59 time=45.7 ms
^C
--- idnet.net ping statistics ---
15 packets transmitted, 13 received, 13% packet loss, time 14243ms
rtt min/avg/max/mdev = 34.529/45.801/51.838/4.690 ms

[root@localhost ~]# tracert idnet.net
traceroute to idnet.net (212.69.36.10), 30 hops max, 40 byte packets
1  www.routerlogin.com (192.168.0.1)  0.728 ms  1.024 ms  1.312 ms
2  telehouse-gw2-lo1.idnet.net (212.69.63.51)  40.581 ms *  42.128 ms
3  * * *
4  * * *
5  * * *
6  * * *
7  * * *
8  www.idnet.net (212.69.36.10)  51.344 ms  52.704 ms  52.932 ms

[root@localhost ~]# tracert idnet.net
traceroute to idnet.net (212.69.36.10), 30 hops max, 40 byte packets
1  www.routerlogin.com (192.168.0.1)  0.600 ms  0.881 ms  1.157 ms
2  telehouse-gw2-lo1.idnet.net (212.69.63.51)  50.935 ms *  50.998 ms
3  telehouse-gw3-g0-1-400.idnet.net (212.69.63.243)  51.804 ms  53.242 ms  53.641 ms
4  redbus-gw2-g0-1-331.idnet.net (212.69.63.5)  56.884 ms  57.311 ms  57.540 ms
5  redbus-gw1-fa2-0-300.idnet.net (212.69.63.225)  58.586 ms  59.790 ms  61.203 ms
6  www.idnet.net (212.69.36.10)  56.491 ms  56.670 ms  58.614 ms
[root@localhost ~]#

Any help would be appriciated.
Many Thanks

[Sebby]

Hmm, well the weird thing is that the router is reporting a downstream attenuation of 8dB, which is highly doubtful, but that's not really an issue. The SNRM is okay, although if the attenuation is really that low, I'd say you should have more of a margin. But even so, things should still be fine.

When you say you're experiencing disconnects, is the router losing sync with the exchange, or is it just the PPP (internet) session that's dropping?

Also, which version DG834G do you have, and what firmware version?

[PetFish]

Thanks for your reply.

DG834G v3
Firmware  V4.01.37

The connection drops totally, sometimes with the Connection Speed status page reporting 0 kbps (Down)   0 kbps (Up), other time sticking to the original speeds, other times the status page says connected with 0 up and 0 down.

:/

[Sebby]

It sounds like you're suffering from bursts of noise. Do you have a master socket with a removable lower plate? If so, could you carefully remove it, plug the router into the socket behind the plate, and re-post your stats?

[PetFish]

No I dont have the one with the removable plate - but my router is plugged into the first socket that the cable comes in to - unfortunatly there are serveral extensions in the house - the main wires coming into the house are first spliced with an extension that goes downstairs, then that comes back upto the master socket which is then divided into another extension upstairs. lol

But my problem is that the house has been setup up like this for several years and has only just started to cause a problem. I think I will have to get the BT engineers out :/

I am going to leave routerstats running and post the downstream margin image later today. So far it is fluctuating between 6 and 10 db. 

Also I cannot get the bt speedtester to work - but will try that again later too .

Cheers

[Rik]

I had a similar wiring arrangement dating from voice days. One day I simply had no ADSL anymore until it was simplified. Lots of noise pickup and a gradual deterioration in joints in my case.

[Sebby]

No I dont have the one with the removable plate - but my router is plugged into the first socket that the cable comes in to - unfortunatly there are serveral extensions in the house - the main wires coming into the house are first spliced with an extension that goes downstairs, then that comes back upto the master socket which is then divided into another extension upstairs. lol

I would remove the ring wire (connected to terminal 3) from each socket - that is likely to make a lot of difference.

The problem with noise is that it can appear/disappear/reappear when seemingly nothing has changed. The ring wire picks up noise, and it's actually not needed anymore, so you can go ahead a and remove them. It must be from every socket.

[PetFish]

Well peeps - IDNet Tech support and BT Engineers have managed to sort it out some how - And fingers crossed that will be the end of my disconnects, and packetloss.

Sebby thanks very much for your help and Rik. 

I think in a few days time I will look into removing the ring wire from my cicuit.

Cheers peeps :x

[Rik]

Good result. 

[Sebby]

Glad to hear it.