How long for the connection to settle after migration?

[splat]

Hi Rik,
NM readings are much the same now after moving router to a faceplate socket so no flat cable extension. Also makes no difference to download speed or ping. Wireless also no different to patch cord.
Only other thought I have at mo is that router was on a powersaver, powering down whenever pc was turned off.  Could this be causing the instability? Permanently on now with direct feed.
Will give support a ring tomorrow.
Splat

[splat]

bt speedtest this morning shows same as before:
Test1 comprises of [sic] Best Effort Test:  -provides background information.
    IP profile for your line is - 1750 kbps
    DSL connection rate: 448 kbps(UP-STREAM)  8064 kbps(DOWN-STREAM)
    Actual IP throughput achieved during the test was - 1643 kbps

Router status (after restarting last night in new direct-to-faceplate position:
Data Rate
Stream Type    Actual Data Rate
Up Stream    448 (Kbps.)
Down Stream    8064 (Kbps.)
Operation Data
Operation Data    Upstream    Downstream
Noise Margin    25 dB    7 dB
Attenuation    6 dB    6 dB

Defect Indication
Indicator Name    Near End Indicator    Far End Indicator
Fast Path FEC Correction    0    0
Interleaved Path FEC Correction    612    473
Fast Path CRC Error    0    0
Interleaved Path CRC Error    2    19
Loss of Signal Defect    0    ---
Fast Path HEC Error    0    0
Interleaved Path HEC Error    0    0

Log shows:
2008.03.14 07:49:29 192.168.1.2 login success
2008.03.14 07:31:58 sending ACK to 192.168.1.2
2008.03.14 07:31:58 sending OFFER to 192.168.1.2
2008.03.14 07:31:58 sending OFFER to 192.168.1.2
2008.03.14 06:24:44 NTP Date/Time updated.
2008.03.14 00:55:42 sending ACK to 192.168.1.3
2008.03.14 00:55:41 sending OFFER to 192.168.1.3
2008.03.14 00:52:48 192.168.1.4 logout

No mention of CHAP though and can't see how to change the protocol anywhere - is this important?

[Sebby]

There's something very strange going on here. Your attenuation is so low and yet your noise margin is just about good on the downstream; I'd expect it to be a lot better...

I forgot what's gone on in this thread (bad memory these days!). Did we get you to try the test socket?

It looks like there is some instability going on, despite a good line, causing the profile to drop and fail to recover.

[Rik]

Hi Splat

I agree with Sebby, your stats don't make sense. For a 6db attenuation, you should be going flat out with a healthy noise margin. Your profile, though shows classic signs of an unstable line. Have you tried another router?

The log is just showing local login details, so no mention of CHAP.

[splat]

Hi Rik and Sebby,
Router was on a powersaver until the night before Friday's post so shutdwon each nite. IDnet support believed this was causing the instability which led to profile stuck down at 1750 kbps. Router stats were taken after overnight left on, unused. No change in the bt speedtest data below taken 48hrs after the change of router position and permanently on.  The low attenuation is because we live about 80 meters from the exchange.

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

Router log for last 2 days:
2008.03.16 17:37:50 192.168.1.3 login success
2008.03.16 12:55:07 NTP Date/Time updated.
2008.03.16 12:35:35 sending ACK to 192.168.1.3
2008.03.16 12:35:35 sending OFFER to 192.168.1.3
2008.03.16 11:17:54 sending ACK to 192.168.1.3
2008.03.16 06:51:45 NTP Date/Time updated.
2008.03.16 00:48:23 NTP Date/Time updated.
2008.03.15 23:17:26 sending ACK to 192.168.1.3
2008.03.15 23:17:24 sending ACK to 192.168.1.3
2008.03.15 23:17:22 sending ACK to 192.168.1.3
2008.03.15 23:17:20 sending ACK to 192.168.1.3
2008.03.15 23:17:18 sending ACK to 192.168.1.3
2008.03.15 23:17:16 sending OFFER to 192.168.1.3
2008.03.15 23:17:14 sending OFFER to 192.168.1.3
2008.03.15 23:17:12 sending OFFER to 192.168.1.3
2008.03.15 21:12:27 sending ACK to 192.168.1.3
2008.03.15 18:45:00 NTP Date/Time updated.
2008.03.15 16:05:24 sending ACK to 192.168.1.3
2008.03.15 16:05:22 sending ACK to 192.168.1.3
2008.03.15 16:05:20 sending OFFER to 192.168.1.3
2008.03.15 16:05:18 sending OFFER to 192.168.1.3
2008.03.15 16:05:16 sending OFFER to 192.168.1.3
2008.03.15 15:07:57 sending ACK to 192.168.1.3
2008.03.15 15:07:55 sending ACK to 192.168.1.3
2008.03.15 15:07:53 sending ACK to 192.168.1.3
2008.03.15 15:07:51 sending ACK to 192.168.1.3
2008.03.15 15:07:49 sending ACK to 192.168.1.3
2008.03.15 15:07:47 sending OFFER to 192.168.1.3
2008.03.15 15:07:45 sending OFFER to 192.168.1.3
2008.03.15 15:07:43 sending OFFER to 192.168.1.3
2008.03.15 13:38:55 sending ACK to 192.168.1.3
2008.03.15 13:38:54 sending OFFER to 192.168.1.3
2008.03.15 12:41:37 NTP Date/Time updated.
2008.03.15 12:35:41 sending ACK to 192.168.1.3
2008.03.15 12:35:41 sending OFFER to 192.168.1.3
2008.03.15 12:05:00 sending ACK to 192.168.1.3
2008.03.15 12:04:59 sending OFFER to 192.168.1.3
2008.03.15 12:04:11 sending ACK to 192.168.1.3
2008.03.15 12:04:11 sending OFFER to 192.168.1.3
2008.03.15 09:25:47 sending ACK to 192.168.1.3
2008.03.15 09:25:46 sending OFFER to 192.168.1.3
2008.03.15 09:25:46 sending OFFER to 192.168.1.3
2008.03.15 09:15:07 sending ACK to 192.168.1.3
2008.03.15 06:38:15 NTP Date/Time updated.
2008.03.15 00:34:53 NTP Date/Time updated.

Router ADSL status excerpt:
Operation Data    Upstream    Downstream
Noise Margin    25 dB    8 dB
Attenuation    6 dB    6 dB

Defect Indication
Indicator Name    Near End Indicator    Far End Indicator
Fast Path FEC Correction    0    0
Interleaved Path FEC Correction    8024    61824
Fast Path CRC Error    0    0
Interleaved Path CRC Error    11    2048
Loss of Signal Defect    0    ---
Fast Path HEC Error    0    0
Interleaved Path HEC Error    68    0

Only got one router - is testing in the test position just a matter of using the main socket into the house?
Splat

[Rik]

Hi Splat

The test socket is only applicable if you have an NTE5 master socket, the type where the bottom portion of the faceplate can be removed. Otherwise, all sockets are pretty much equal. The powersaver could well look like instability to the exchange, so you will need to wait another 24-72 hours, then your profile will lift. If it doesn't and IDNet are seeing a stable connection, they can intervene.

[Sebby]

Yep, give it 5 days in total I'd say, and if there's no change, get onto IDNet. If it continues to happen after that, there must be some instability, which we can look into.

[splat]