The BT profiles are defined by sync ranges, i.e. if you sync at x that'll be in the range for profile y. If you sync within the range for a lower profile, as far as I am aware, the sync will result in a move to the lower profile (moves in the other direction can take 5 days).

If you re-sync at the same or higher rate this is not seen as a poor sync event unless the resyncs happen at a rate of 10 times or more per hour.

Might be worth bunging a screen dump of your router stats to a site such as imageshack and posting a link.

I'm not sure about getting stats from your router.

See if http://192.168.0.1/setup.cgi?todo=debug enable debugs (replace the 192.168.0.1 with your router's address).

If that works go to a command prompt (Windows start->cmd, I think) and launch telnet.

e.g.

telnet 192.168.0.1

On my Netgear (different model) I can then

cat /proc/avalanche/modem_stats

to get the error stats.

Think I've got telnet working now...
I tried your telnet command but got no such file. Bit of searching came up with the command "adslctl info --stats"

It gives the following....


BusyBox v1.00 (2008.10.21-10:23+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# adslctl info --stats
adslctl: ADSL driver and PHY status
Status: ShowtimeRetrain Reason: 0
Channel: INTR, Upstream rate = 448 Kbps, Downstream rate = 6880 Kbps
Link Power State: L0
Mode: G.DMT
Channel: Interleave
Trellis: ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 14.2 25.0
Attn(dB): 24.0 14.5
Pwr(dBm): 19.8 12.3
Max(Kbps): 7648 1216
Rate (Kbps): 6880 448
G.dmt framing
K: 216(0) 15
R: 16 8
S: 1 8
D: 32 4
ADSL2 framing
MSGc: 1 1
B: 216 15
M: 1 8
T: 1 1
R: 16 8
S: 1.0737 8.5000
L: 1736 128
D: 32 4
Counters
SF: 864408 864418
SFErr: 10 1
RS: 58779774 7346550
RSCorr: 3655 15
RSUnCorr: 208 0

HEC: 9 1
OCD: 1 1
LCD: 0 0
Total Cells: 238446185 0
Data Cells: 903690 0
Drop Cells: 0
Bit Errors: 0 0

ES: 3 0
SES: 0 0
UAS: 14 0
AS: 14695

INP: 1.17 1.00
PER: 1.87 1.85
delay: 8.58 8.50
OR: 29.80 30.11

Bitswap: 0 0

Total time = 4 hours 5 min 15 sec
SF = 864408
CRC = 10
LOS = 0
LOF = 0
ES = 3
Latest 1 day time = 4 hours 5 min 15 sec
SF = 864408
CRC = 10
LOS = 0
LOF = 0
ES = 3
Latest 15 minutes time = 5 min 15 sec
SF = 18526
CRC = 0
LOS = 0
LOF = 0
ES = 0
Previous 15 minutes time = 15 min 0 sec
SF = 52923
CRC = 0
LOS = 0
LOF = 0
ES = 0
Previous 1 day time = 0 sec
SF = 0
CRC = 0
LOS = 0
LOF = 0
ES = 0
15 minutes interval [-30 min to -15 min] time = 15 min 0 sec
SF = 52923
CRC = 0
LOS = 0
LOF = 0
ES = 0
15 minutes interval [-45 min to -30 min] time = 15 min 0 sec
SF = 52982
CRC = 0
LOS = 0
LOF = 0
ES = 0
15 minutes interval [-60 min to -45 min] time = 15 min 0 sec
SF = 52923
CRC = 0
LOS = 0
LOF = 0
ES = 0
Showtime Drop Reason: 0
Last Retrain Reason: 0
#
#

There seem to be two variants of Netgear firmware, you have the other one. I think your firmware is supported by the DMT tool, so you could play around with that.

Check http://dmt.mhilfe.de/ to see if your model is supported. If it is I think you may be able to adjust the target SNR margin down to see if you can get increased sync rates. At your own risk though.

Your line is interleaved (as opposed to fast path) and thus uses Reed Solomon techniques to correct single bit errors in transmitted data (same technique as is used to auto correct CD read errors).

RSCorr: 3655 15
RSUnCorr: 208 0

Means that 3655/15 packets (down/up) had errors auto corrected (out of a total 58779774/7346550 down/up packets),

208 downstream packets couldn't be corrected, which probably caused an error at a higher protocol layer (TCP) requiring data retransmission.

That number of errors is insignificant considering your 4 hour uptime.

In reply to a post by XRaySpeX:

Such detail is unnecessary, unless you are a Signals Specialist.

...or a masochist.

In reply to a post by john2007:

...or a masochist.

Yes, I refrained from saying that

In reply to a post by john2007:

I think your firmware is supported by the DMT tool, so you could play around with that. If it is I think you may be able to adjust the target SNR margin down to see if you can get increased sync rates. At your own risk though.

Or, you don't need to use DMT; you can do it all thro' TELNET - see Netgear DG834GT & DG834 v4- Override Target SNR

I sort of guessed you wouldn't need DMT but I've never had a router with compatible firmware to practice on.

Thanks John, glad to hear my errors are insignificant
I'll keep monitoring for a few days.
Am I right in assuminmg that the error counts will reset if the router resets?
Daft question of course they will
How can I log these errors so I know how many there were leading up to an event like a reboot?

Had a look at http://dmt.mhilfe.de/ , noit sure I fancy messing if the support is all in German. I speak a bit but not enough to get techie with it

In reply to a post by john2007:

In reply to a post by XRaySpeX:

Such detail is unnecessary, unless you are a Signals Specialist.

...or a masochist.

Whip me, whip me

That sound more interesting. Thanks XRaySpeX