Hi again, yes you are correct it is my work network blocking the port because I can use the app on my phone to access it over 4g but not over my workplace wireless. So the next step is to set the camera up to the correct port and I think I will have it. Cheers for all your help...
Anyone Using an Asus DSL-AC68U
- Thread starter Socrates470BC
- Start date
Even i am not in UK ... any link for this Kitz traffic tool?? thanks
Here you go.
http://www.kitz.co.uk/adsl/DLM.htm
On the left hand side panel there is a DLM tool also.
http://www.kitz.co.uk/adsl/DLM.htm
On the left hand side panel there is a DLM tool also.
Thanks for sharing these mate.
Had G.INP enabled on my Huawei cab this morning, speed up by about 5Mb and 1 error in 8 hours
Many Thanks
==============================================
For all if needs it
there is one more firmware (same as the one posted by me earlier) but now has dvla fix issue
plus
wifi timer fix issue
qos invalid name issue
olr_defer driver
It may quality for official
DSL-AC68U_3.0.0.4_378_6986-g2437e87_DSL_1.0.2.9.rar
https://www.asuswebstorage.com/navigate/s/13B3DABE6DF54FE1A6C27991C559CB51Y
I'll try this firmware later today but I have a feeling that on an ECI DSLAM (Lantiq/Infineon chipset) it will either not improve or be worse than the firmware without OLR defer test. At least on the initial dmt olr defer test firmware I found it to perform worse (in regards to CRC errors) than the original firmware without that.
If G.INP ever arrives to ECI DSLAM's in the UK on BT Openreach's network then this won't be a problem anymore I believe.
If G.INP ever arrives to ECI DSLAM's in the UK on BT Openreach's network then this won't be a problem anymore I believe.
Last edited:
Associate
- Joined
- 5 May 2015
- Posts
- 48
This is a note about the latest 6553 firmware.
After I upgraded I just left all the DSL settings at default and was DLM'd
the following morning and placed interleaved (due to the amount of resets I had done).
I then waited 10 days and was still not placed back on fastpath having accumulated only twp CRC errors up and one down.
I decided to set dynamic line adjustment to disabled and set ESNP to stable
and set G.INP to enabled as I had done in the previous (5007) firmware.
The dsl link was reset and four days later I was back on fastpath again, so I
am not convinced the dynamic line adjustment is actually functioning the way it was meant to and it certainly seems to work better for me with it turned off.
After I upgraded I just left all the DSL settings at default and was DLM'd
the following morning and placed interleaved (due to the amount of resets I had done).
I then waited 10 days and was still not placed back on fastpath having accumulated only twp CRC errors up and one down.
I decided to set dynamic line adjustment to disabled and set ESNP to stable
and set G.INP to enabled as I had done in the previous (5007) firmware.
The dsl link was reset and four days later I was back on fastpath again, so I
am not convinced the dynamic line adjustment is actually functioning the way it was meant to and it certainly seems to work better for me with it turned off.
Much better for me off too, when set to on my CRCs are highest they've been, even compared to high performance settings
Associate
- Joined
- 5 May 2015
- Posts
- 48
This may be nothing, but I checked my previous notes from the dsl logs
from when I used the default settings compared to my latest settings, having
turned off dynamic line adjustment and the signal to noise ratios have been considerably better since I turned it off both up and down.
from when I used the default settings compared to my latest settings, having
turned off dynamic line adjustment and the signal to noise ratios have been considerably better since I turned it off both up and down.
This device can't be fixed, as predicted fine for a few days then it resynced yesterday morning and since then getting error spikes that are sometimes in the thousands and cause a few seconds on lag in game. Could be plusnet and their shoddy gateways:
Associate
- Joined
- 5 May 2015
- Posts
- 48
I have never had error spikes on my line. using this firmware or the previous. To me it must be a combination of the quality of the line, the ISPThis device can't be fixed, as predicted fine for a few days then it resynced yesterday morning and since then getting error spikes that are sometimes in the thousands and cause a few seconds on lag in game. Could be plusnet and their shoddy gateways:
and the DSLAM (ECI or Huawei) that causes some people problems.
I don't think you can recommend a definitive dsl configuration for this device because of the variables involved.
I am however very pleased with the way it performs for me.
Has G.INP recently been enabled? On mine after G.INP was enabled I got an insane amount of errors, after turning off Dynamic Line Adjustment and rebooting it now shows Path mode for both upstream and downstream and I've had no errors
As an experiment I've completely overhauled how my devices are connected to the electricity supply.
Online UPS Port 1 (Set to 230v @ 50Hz):
- ASUS DSL-AC68U
Online UPS Port 6 (Set to 230v @ 50Hz):
- Home Server
Mains via mains conditioner:
- Desktop Computer
- Laptop
- Monitor
- Phone charger
- Other charger
Previously all those listed on mains were plugged into the same port as the ASUS on the online UPS. Effectively this also means every device lost power temporarily and so was fully reset (except the laptop as that has a battery in it of course).
I've also temporarily increased SNRM target to 18dB, and will decrease this every 1-2dB every 24 hours that indicates lower than usual or normal amount of CRC errors and/or error seconds.
Online UPS Port 1 (Set to 230v @ 50Hz):
- ASUS DSL-AC68U
Online UPS Port 6 (Set to 230v @ 50Hz):
- Home Server
Mains via mains conditioner:
- Desktop Computer
- Laptop
- Monitor
- Phone charger
- Other charger
Previously all those listed on mains were plugged into the same port as the ASUS on the online UPS. Effectively this also means every device lost power temporarily and so was fully reset (except the laptop as that has a battery in it of course).
I've also temporarily increased SNRM target to 18dB, and will decrease this every 1-2dB every 24 hours that indicates lower than usual or normal amount of CRC errors and/or error seconds.
Last edited:
I just don't get it!!!
Since switching to Fibre last month, I have been desperately disappointed at the "performance". At best, I get 6.3Mb d/l on an Attn of around 32db. (the router said that I had a max rate down of 11mb!!) It's a long line I know but my ADSL was at 57db with a D/L of 5Mb.
I have reset the router per the config per Ayahuasca's post above. What's amazing is that I had been getting a ping of around 55ms. With this config, I am getting a ping of 1ms! The downside is that I now have a D/L of around 3Mb and it has switched from interleaved to Fastpath. I am at a loss to understand the logic of this!
DSL Firmware Version 1.0.2.7
DSL Driver Version FwVer:5.5.1.129_B_A60901 HwVer:T14.F7_0.2
DSL Link Status
up
DSL Uptime
0 days 0 hours 17 minute(s) 17 seconds
DSL modulation
ITU G.993.2(VDSL2), G.998.4(G.INP)
ANNEX Mode
ANNEX B
SNR Down
5.5 dB
SNR Up
6.1 dB
Line Attenuation Down
32.9 dB
Line Attenuation Up
16.4 dB
Path Mode
FastPath
Data Rate Down
6861 kbps
Data Rate Up
883 kbps
MAX Rate Down
9028
MAX Rate Up
883
POWER Down
5.7 dbm
POWER Up
0.4 dbm
CRC Down
0
CRC Up
0
Funny how this view shows "Annex B" when the DSL settings are "Annex A"
Since switching to Fibre last month, I have been desperately disappointed at the "performance". At best, I get 6.3Mb d/l on an Attn of around 32db. (the router said that I had a max rate down of 11mb!!) It's a long line I know but my ADSL was at 57db with a D/L of 5Mb.
I have reset the router per the config per Ayahuasca's post above. What's amazing is that I had been getting a ping of around 55ms. With this config, I am getting a ping of 1ms! The downside is that I now have a D/L of around 3Mb and it has switched from interleaved to Fastpath. I am at a loss to understand the logic of this!
DSL Firmware Version 1.0.2.7
DSL Driver Version FwVer:5.5.1.129_B_A60901 HwVer:T14.F7_0.2
DSL Link Status
up
DSL Uptime
0 days 0 hours 17 minute(s) 17 seconds
DSL modulation
ITU G.993.2(VDSL2), G.998.4(G.INP)
ANNEX Mode
ANNEX B
SNR Down
5.5 dB
SNR Up
6.1 dB
Line Attenuation Down
32.9 dB
Line Attenuation Up
16.4 dB
Path Mode
FastPath
Data Rate Down
6861 kbps
Data Rate Up
883 kbps
MAX Rate Down
9028
MAX Rate Up
883
POWER Down
5.7 dbm
POWER Up
0.4 dbm
CRC Down
0
CRC Up
0
Funny how this view shows "Annex B" when the DSL settings are "Annex A"
Last edited:
While I can't really comment on the above, unfortunately, as I'm not sure what answer to give - I'll provide an update to my mentioned experiment yesterday.
CRC errors, ES and SES remain almost identical to the HG612. Interestingly DLM has given me back some of my lost downstream speed as of this morning too (raising my max sync rate from 67M to 74M - although I'm already on fastpath). I wonder if DLM looks at the SNRM and if it's above a certain amount it will raise the sync rate barrier?
I've reduced my SNRM target from 18dB to 16dB and will continue testing. If DLM does no further positive action (e.g. 74M to 80M) within the next couple of days then I'll try setting 18dB again just to see what happens (if anything).
EDIT: Actually I can provide some answers to the above post.
You're on G.INP, before you changed your DSL settings you must've had G.INP support disabled on the device. This would cause interleaved mode and a rather high ping (possibly combined with a reduced sync rate too).
Regarding the annex A and B, there's two types of annex in VDSL2.
BT uses frequency band plan Annex B Plan 998ADE17, however the setting should be Annex A in the actual DSL settings as that annex setting refers to whether it's running over POTS or ISDN (POTS being A, ISDN being B). At least from memory I'm pretty sure I'm right.
CRC errors, ES and SES remain almost identical to the HG612. Interestingly DLM has given me back some of my lost downstream speed as of this morning too (raising my max sync rate from 67M to 74M - although I'm already on fastpath). I wonder if DLM looks at the SNRM and if it's above a certain amount it will raise the sync rate barrier?
I've reduced my SNRM target from 18dB to 16dB and will continue testing. If DLM does no further positive action (e.g. 74M to 80M) within the next couple of days then I'll try setting 18dB again just to see what happens (if anything).
EDIT: Actually I can provide some answers to the above post.
You're on G.INP, before you changed your DSL settings you must've had G.INP support disabled on the device. This would cause interleaved mode and a rather high ping (possibly combined with a reduced sync rate too).
Regarding the annex A and B, there's two types of annex in VDSL2.
BT uses frequency band plan Annex B Plan 998ADE17, however the setting should be Annex A in the actual DSL settings as that annex setting refers to whether it's running over POTS or ISDN (POTS being A, ISDN being B). At least from memory I'm pretty sure I'm right.
Last edited:
That's helpful, thanks but why would the speed have dropped so drastically form what was already an appalling speed given the ATTN? BTW, I am on Sky, UK.