Strange Problem

[jlbweb]

Hi,

Have been an avid reader of this board for some time but have never needed to post before - always been able to find an answer!

However... recently I have been experiencing a new (to me) problem with my connection. I have the usual noise margin problem which although not fixed is managed by mossywells excellent little app. Now for some reason at irregular periods I lose internet connection but I also lose access to the router - I cannot log into the admin to reboot and mossywells prog cant reboot it either.
I have a wired connection to the router so wireless is not the issue - the only solution that I have found is to walk downstairs and yank the power lead out. It then re synchronises and is fine for an undeterminable period of time anywhere between 15 mins and a few days.

I have noticed in my visits to pull the power lead out that the router is warm bordering on hot but I dont know if it was like this before - it is in the open air .

I have a funny feeling it may be time for a new router however if anyone has any suggestions I would be pleased to hear them.

I have posted my detailed stats in case they are useful - these were taken when I can get access to the router (obviously) I can’t obtain any when the problem has occurred.

Cheers in anticipation

Jon


/usr/sbin/adslctl: ADSL driver and PHY status
Status: Showtime Channel: INTR, Upstream rate = 768 Kbps, Downstream rate = 4448 Kbps
Link Power State: L0
Mode: G.DMT
Channel: Interleave
Trellis: ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 6.7 14.0
Attn(dB): 52.0 30.5
Pwr(dBm): 19.3 9.4
Max(Kbps): 4992 1184
Rate (Kbps): 4448 768
G.dmt framing
K: 140(0) 25
R: 16 16
S: 1 8
D: 64 8
ADSL2 framing
MSGc: 1 1
B: 140 25
M: 1 8
T: 1 1
R: 16 16
S: 1.1134 8.6153
L: 1128 208
D: 64 8
Counters
SF: 53458 53456
SFErr: 15390 0
RS: 3635198 454376
RSCorr: 2676283 4
RSUnCorr: 63169 0

HEC: 13324 0
OCD: 0 0
LCD: 0 0
Total Cells: 9474582 0
Data Cells: 110176 0
Drop Cells: 0
Bit Errors: 0 0

ES: 526 0
SES: 341 0
UAS: 26 0
Total time = 15 min 43 sec
SF = 53458
CRC = 15390
LOS = 569
LOF = 0
ES = 526
Latest 1 day time = 15 min 43 sec
SF = 53458
CRC = 15390
LOS = 569
LOF = 0
ES = 526
Latest 15 minutes time = 43 sec
SF = 2529
CRC = 2487
LOS = 1
LOF = 0
ES = 43
Previous 15 minutes time = 15 min 0 sec
SF = 50929
CRC = 12903
LOS = 568
LOF = 0
ES = 483
Previous 1 day time = 0 sec
SF = 0
CRC = 0
LOS = 0
LOF = 0
ES = 0

[reddwarfcrew]

Well you have absolutely massive errors on your line and the symptoms you have descirbed are when the NM drops to an unacceptably low level. I dont use the bounce util, but I did think it was designed for this scenario and auto reboot the roiuter when the noise level drops to low and it doesn't get a rely from the 'test site' it pings.

It could be that your errors are so bad that even the bounce util cant cope with it.

The errors are the CRC fig vs the SF fig. The CRC fig should be (i think) about 0.1% of the SF fig at most. As you can see, yours is more like 25%!!!!!!

Have you tried connecting the roiuter to the test socket underneath the bt master socket faceplate?

[Koala5]

You say you have spent some time trying tips from the forum.

1: Have you turned off uPNP in the router menu which is a known bug.

2: During the 15 minute period below you had almost 100% line "CRC" errors, ideally they shoudn't exceed 0.1% of the SF's transmitted, so yours are very high. Have you tried the test socket etc etc etc.

Latest 15 minutes time = 43 sec
SF = 2529
CRC = 2487
LOS = 1
LOF = 0
ES = 43

[reddwarfcrew]

snap!

[jlbweb]

The router is currently plugged into the master socket.

I am going to try and see if I get the same problems without the router being connected to the phone line which should tell me if it is related to that. As I said git feeling is that it is a router problem.

Mossywells ap does reboot quite regularly however as I have said when this problem kicks in there is absolutely no access to the router to perform a soft reboot or get any line stats.

[reddwarfcrew]

Not the master socket... the test socket underneath the faceplate of the master socket, You need to unscrew the faceplate.

[jlbweb]

Sorry - yes unpn if off.

More stats -

/usr/sbin/adslctl: ADSL driver and PHY status
Status: Showtime Channel: INTR, Upstream rate = 768 Kbps, Downstream rate = 5216 Kbps
Link Power State: L0
Mode: G.DMT
Channel: Interleave
Trellis: ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 5.4 14.0
Attn(dB): 52.0 30.5
Pwr(dBm): 19.4 10.8
Max(Kbps): 5792 1152
Rate (Kbps): 5216 768
G.dmt framing
K: 164(0) 25
R: 16 16
S: 1 8
D: 64 8
ADSL2 framing
MSGc: 1 1
B: 164 25
M: 1 8
T: 1 1
R: 16 16
S: 1.0969 8.6153
L: 1320 208
D: 64 8
Counters
SF: 34168 34166
SFErr: 7 0
RS: 2323464 290411
RSCorr: 535038 14
RSUnCorr: 226 0

HEC: 6 0
OCD: 0 0
LCD: 0 0
Total Cells: 7143982 0
Data Cells: 28863 0
Drop Cells: 0
Bit Errors: 0 0

ES: 7 0
SES: 5 0
UAS: 26 0
Total time = 10 min 14 sec
SF = 34168
CRC = 7
LOS = 92
LOF = 0
ES = 7

[reddwarfcrew]

your noise is less than 6db. yOu will hit problems when it goes below 7db.

Try the TEST socket and also you can use mognuts util to set your NM much higher (say 10db).

[jlbweb]

Ok - am in the test socket now - will let you know when it has been on a while.

I have always had problems with nm and reboots hence mossywells app - I can live with that. I just dont understand the sudden and very random lock outs from the router.

Thanks for your speeds and useful help.

Jon

[reddwarfcrew]

can you post some stats now and then some stats in about 1hr (assuming it lasts that long!!)