That makes sense, they didn't update my firmware though it's still the same version as before

Download speedachieved during the test was - 14.5 Mbps
For your connection, the acceptable range of speeds is 4 Mbps-21 Mbps.
IP Profile for your line is - 14.52 Mbps

Seems to be ticking over nicely - give it time and I'm sure you will have adequate speeds

It is, but I have a question about these kind of messages which have been appearing in the event log today, here are some from the last few minutes:

14:34:14, 27 Mar. (38306.730000) Admin login successful by 192.168.1.74 on HTTP
14:26:57, 27 Mar. BLOCKED 1 more packets (because of Packet invalid in connection)
14:26:57, 27 Mar. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.74:52253->173.194.34.174:443 on ppp0)
14:23:57, 27 Mar. BLOCKED 10 more packets (because of Packet invalid in connection)
14:23:56, 27 Mar. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.74:52224->217.41.223.75:443 on ppp0)
14:23:48, 27 Mar. BLOCKED 5 more packets (because of Packet invalid in connection)
14:23:47, 27 Mar. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.74:52204->31.13.72.17:443 on ppp0)
14:22:59, 27 Mar. BLOCKED 2 more packets (because of Packet invalid in connection)
14:22:58, 27 Mar. BLOCKED 13 more packets (because of Packet invalid in connection)
14:22:57, 27 Mar. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.74:52225->173.194.78.94:80 on ppp0)
14:22:49, 27 Mar. BLOCKED 1 more packets (because of Packet invalid in connection)
14:22:49, 27 Mar. IN: BLOCK [9] Packet invalid in connection (TCP 217.41.223.73:80->86.160.220.137:52187 on ppp0)
14:18:41, 27 Mar. IN: BLOCK [9] Packet invalid in connection (TCP 217.41.223.72:80->86.160.220.137:52123 on ppp0)
14:18:37, 27 Mar. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.74:52114->173.194.34.174:443 on ppp0)
14:17:32, 27 Mar. BLOCKED 13 more packets (because of Packet invalid in connection)
14:17:31, 27 Mar. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.74:52093->2.18.115.205:443 on ppp0)
14:16:50, 27 Mar. IN: BLOCK [9] Packet invalid in connection (TCP 87.248.214.50:443->86.160.220.137:52097 on ppp0)
14:16:46, 27 Mar. IN: BLOCK [9] Packet invalid in connection (TCP 87.248.214.50:443->86.160.220.137:52081 on ppp0)
14:14:54, 27 Mar. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.74:52016->173.194.34.160:443 on ppp0)
14:14:12, 27 Mar. BLOCKED 7 more packets (because of Packet invalid in connection)

Very occassionally this blocking of certain packets leads web pages to stop loading, but when refreshed they will load fine.

Does anyone know what these messages mean, and if they should be there?

Just had another re-sync:


ADSL Line Status

Connection Information

Line state: Connected
Connection time: 0 days, 00:03:03
Downstream: 15.99 Mbps
Upstream: 1.13 Mbps

ADSL Settings

VPI/VCI: 0/38
Type: PPPoA
Modulation: G.992.5 Annex A
Latency type: Interleaved
Noise margin (Down/Up): 9.0 dB / 6.1 dB
Line attenuation (Down/Up): 6.2 dB / 3.3 dB
Output power (Down/Up): 20.1 dBm / 11.5 dBm
FEC Events (Down/Up): 0 / 0
CRC Events (Down/Up): 0 / 0
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
HEC Events (Down/Up): 0 / 0
Error Seconds (Local/Remote): 4 / 0

and from the log:

15:28:31, 27 Mar. (41563.880000) DSL noise margin: 5.90 dB upstream, 9.10 dB downstream
15:28:29, 27 Mar. (41562.320000) DSL line rate: 1156 Kbps upstream, 16372 Kbps downstream

So my downstream sync has decreased (again), and the upstream sync has increased

How come the down sync keeps going down, even though it is within daylight hours ?

Edited by deleted (Wed 27-Mar-13 15:33:45)

Looks like your upstream sync is starting to settle down nicely, downstream SNRM at sync time increased a touch and hence a very small reduction in sync speed but nothing to worry about - possibly due to a little bit of noise on the line affecting the ADSL2+ frequencies at sync time.

I think I'm now at my maximum achievable upstream speeds

Would I be right in saying, my Target SNR Margin is still 9db but a small amount of noise added that extra .10db? (as DLM can only set 3,6,9,12 or 15db values)

Edited by deleted (Wed 27-Mar-13 16:22:05)

Others can answer about 21CN WBC and how it works - but to me it looks as if you are doing fine

My experience of ADSL2+ is confined to LLU which tends to be a different "kettle of fish"...

lol I'd be on LLU given the choice too

It looks like the increase in my upload speeds has resulted in a lower ping too my ping to google used to be around 30ms, it's now gone down to 20ms (over ethernet)

In reply to a post by matthewcl375:

Would I be right in saying, my Target SNR Margin is still 9db

Yes

but a small amount of noise added that extra .10db? (as DLM can only set 3,6,9,12 or 15db values)

The opposite. It is a noise margin (SNRM). So for it to go up 0.1dB the noise has gone down by 0.1dB.

Ok, so it was something else which caused the lower sync then...