Anyone Using an Asus DSL-AC68U

[babis3g]

ASUS DSL-AC68U Beta Firmware version 3.0.0.4.376_2187 (This product supports both Annex A and Annex B)
1. DSL firmware updated - v1.0.2.2.
2. DSL driver updated - v5.5.1.127.
3. Fixed WAN Connection Type - PPPoA related issues.
4. Add PPP Authentication options, AUTO/ PAP/ CHAP.
5. Modify ajax time for updating spectrum.
6. Now supports Rx AGC GAIN Adjustment (ADSL) setting(Advanced Settings > Administration > DSL Setting).
7. Fixed various UI related issues.
8. Now supports Non-starndard G.vector setting(Advanced Settings > Administration > DSL Setting).
9. Fixed Diagnostic debug log failed to transmit in certain case issue.
10. Fine tune DSL Log, update by ajax.
11. Upgrade OpenSSL library to 1.0.0q.
12. Fixed security vulnerability, BusyBox: CVE-2013-1813.
13. Fixed Internet connection failed to be established once Download Master installed then reboot.
14. Fixed sync issue with certain DSLAM.
15. Fixed Wireless Auto select channel related issues.

 

[cuke2u]

I think that's the one I have just removed...

 

[Randell Floyd]

I've just installed it, will report back any findings.

 

[Randell Floyd]

Now flashed and 30 minutes have passed. Note I've also changed some DSL settings which have resulted in some SNRMarginUp changes, which I'm not sure is worth anything.

lineState=up
Opmode=ITU G.993.2(VDSL2)
SNRMarginDown=5.6 dB
AttenDown=11.9 dB
SNRMarginUp=15.8 dB
AttenUp=3.8 dB
DataRateDown=60104 kbps
DataRateUp=19999 kbps
WanListMode=1
FECDown=34
FECUp=0
CRCDown=3
CRCUp=0
HECDown=0
HECUp=0
ADSLUpTime=8 min, 47 secs
ADSLActiveTime=0 min, 17 secs
PowerDown=14.0 dbm
PowerUp=10.0 dbm
ATURID=26005443434e0000
ATUCID=b5004244434da485
AttainUp=24237
AttainDown=71100
ShowtimeStart=17
TotalStart=34
ATURANSIRev=0
ATUCANSIRev=0
ATURANSIStd=0
ATUCANSIStd=0
InterleaveDepth=1
AdslStandard=VDSL2
AdslType=ANNEX_B
mtenStandard=G.dmt.bisplus
admin@DSL-AC68U:/tmp/home/root#

 

[Ixel]

Now flashed and 30 minutes have passed. Note I've also changed some DSL settings which have resulted in some SNRMarginUp changes, which I'm not sure is worth anything.

lineState=up
Opmode=ITU G.993.2(VDSL2)
SNRMarginDown=5.6 dB
AttenDown=11.9 dB
SNRMarginUp=15.8 dB
AttenUp=3.8 dB
DataRateDown=60104 kbps
DataRateUp=19999 kbps
WanListMode=1
FECDown=34
FECUp=0
CRCDown=3
CRCUp=0
HECDown=0
HECUp=0
ADSLUpTime=8 min, 47 secs
ADSLActiveTime=0 min, 17 secs
PowerDown=14.0 dbm
PowerUp=10.0 dbm
ATURID=26005443434e0000
ATUCID=b5004244434da485
AttainUp=24237
AttainDown=71100
ShowtimeStart=17
TotalStart=34
ATURANSIRev=0
ATUCANSIRev=0
ATURANSIStd=0
ATUCANSIStd=0
InterleaveDepth=1
AdslStandard=VDSL2
AdslType=ANNEX_B
mtenStandard=G.dmt.bisplus
admin@DSL-AC68U:/tmp/home/root#

I wouldn't disable UPBO, it not only increases crosstalk for longer lines but it also violates BT Openreach's SIN 498 (not ANFP).

 

[Randell Floyd]

I wouldn't disable UPBO, it not only increases crosstalk for longer lines but it also violates BT Openreach's SIN 498 (not ANFP).

Reverted to default now, apart from Rx AGC GAIN Adjustment (VDSL) set to High Performance.

It seems that maybe this firmware yields a faster Attain Up/Down for me in tune of 3-4mb than the last, yet I'm still seemingly stuck on 60mb for the time being.

edit:

My FEC errors where heading into the 11000's within 10 minutes, so factory reset and flashed the beta once more, this time leaving all settings alone.

 

[Randell Floyd]

Well I'm now back on 2160 as the beta produced 20,000 FEC and 1000 CRC in less than 10 minutes, that's similar to 6 days of heavy downloading on 2160.

 

[Ixel]

Interesting. I'm wondering if this firmware (2187 beta) is also producing greater instability too.

 

[Randell Floyd]

Interesting. I'm wondering if this firmware (2187 beta) is also producing greater instability too.

Either it was bad timing or it's defiantly a lot worse for me.

2160 for 40 minutes

lineState=up
Opmode=ITU G.993.2(VDSL2)
SNRMarginDown=5.3 dB
AttenDown=10.9 dB
SNRMarginUp=5.9 dB
AttenUp=3.0 dB
DataRateDown=59673 kbps
DataRateUp=19154 kbps
WanListMode=1
FECDown=4304
FECUp=13
CRCDown=120
CRCUp=1
HECDown=0
HECUp=0
ADSLUpTime=45 min, 38 secs
ADSLActiveTime=0 min, 17 secs
PowerDown=14.0 dbm
PowerUp=7.0 dbm
ATURID=26005443434e0000
ATUCID=b5004244434da485
AttainUp=19154
AttainDown=70292
ShowtimeStart=17
TotalStart=34
ATURANSIRev=0
ATUCANSIRev=0
ATURANSIStd=0
ATUCANSIStd=0
InterleaveDepth=1
AdslStandard=VDSL2
AdslType=ANNEX_B
mtenStandard=G.dmt.bisplus (Annex L)
admin@DSL-AC68U:/tmp/home/root#

The errors all came in a burst, which I think might have been when the Sony TV/PS4 where turned on, but I've no real proof of that.

 

[Ixel]

Back on 2160, haven't killed spectrum at the moment but I haven't touched the page either.

near-end path0 fec:     141237(141237)
near-end path0 crc:     0(0)
near-end fec sec:       1070(1070)
near-end err sec:       0(0)
near-end ses sec:       0(0)
near-end los sec:       0(0)
near-end ua  sec:       0(0)
far-end path0 fec:      3107(767275)
far-end path0 crc:      0(3052)
far-end fec sec:        50(17155)
far-end err sec:        0(2377)
far-end ses sec:        0(0)
far-end los sec:        0(1074)
far-end ua  sec:        0(44551)

fwVer= FwVer:5.5.1.126_B_A60901 HwVer:T14.F7_0.1
lineState=up
Opmode=ITU G.993.2(VDSL2)
SNRMarginDown=13.7 dB
AttenDown=10.4 dB
SNRMarginUp=6.9 dB
AttenUp=0.1 dB
DataRateDown=42125 kbps
DataRateUp=19999 kbps
WanListMode=0
FECDown=141237
FECUp=3107
CRCDown=0
CRCUp=0
HECDown=0
HECUp=0
ADSLUpTime= 7:03, 44 secs
ADSLActiveTime=0 min, 19 secs
PowerDown=12.1 dbm
PowerUp=4.4 dbm
AttainUp=26350
AttainDown=106120
ShowtimeStart=19
TotalStart=19
InterleaveDepth=1819
AdslStandard=VDSL2
AdslType=ANNEX_B

Perhaps 2160 is more stable than 2187 beta? I had way more FEC on 2187 beta.

 

[simoncraddock]

Give up chaps! Let's face it, Asus have had over 8 months tinkering with the firmware and still can't fix it.

 

[Ixel]

Give up chaps! Let's face it, Asus have had over 8 months tinkering with the firmware and still can't fix it.

I would use the FB 7490 but I can't. Mine just crashes at random times, my guess is due to the manual changes I did to the ar7 config to support my no NAT network. If I could get it to stop crashing and support multiple static IP's which can be directly routed to connected network devices then I'd use it.

 

[Tyke]

Love Asus routers, but the DSL just doesn't work for me. It dropped my Infinity 2 connection to interleaved after a few days, and connect speed dropped by 10Mbps. Now running a Billion 8800NL bridged into the Asus and back on fastpath!!!

 

[danivtec]

I have also given up and just using the unit as a router which is very good. DLM has hit my line due to the DSL side and currently using the open reach modem to get the line back up to speed.

 

[Ragnahex]

yup i finally gave up using the modem part of it today...... just not worth the time and effort i have put into it to just lose speed again and again

 

[Randell Floyd]

I'm mildly tempted to return it and get the Billion 8800AXL since it's seems the better out of the box stability option, it will also give the error seconds details.

I've not found the Wi-Fi on the Asus to be any better signal wise than TT super router which makes it an expensive no win.

 

[cuke2u]

I think things are improving now I've had the OR Modem connected for a few days:
Tracing route to lhr08s06-in-f14.1e100.net [216.58.210.14]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 11 ms 12 ms 12 ms ip-84-38-37-34.easynet.co.uk [84.38.37.34]
4 11 ms 10 ms 11 ms 72.14.219.13
5 10 ms 9 ms 10 ms 209.85.255.78
6 11 ms 11 ms 10 ms 209.85.250.169
7 13 ms 13 ms 13 ms lhr08s06-in-f14.1e100.net [216.58.210.14]

 

[bitsNbobs]

Tinkering with a older and different Asus router i spotted as used in my local small computer shop which i picked up yesterday ive noticed something else as to why there may be an issue with the DSL-AC68U for FTTC users but not ADSL users.

I do not want to get anyones hopes up but here is another potential fix if this model has the setting.

Find the MTU setting (if the DSL-68U has one, wish i had investigated the options in more detail before returning my faulty one).

For ADSL set this to 1500 for FTTC set this to a max of 1452.
Save changes
Shut computer used to enter modem/routers config down
Disconnect the modem cable from the phone socket and then reconnect (you want a full fresh resync)
Wait until it is fully resynced
Power back up computer and other devices

This may help the FEC and CRC issues NO promises but it is entirely possible. Before anyone says this should not matter, it can and does on FTTC, the MTU setting being wrong on any type of PPPoE can be very fussy with regards to error correction.

 

[babis3g]

Tinkering with a older and different Asus router i spotted as used in my local small computer shop which i picked up yesterday ive noticed something else as to why there may be an issue with the DSL-AC68U for FTTC users but not ADSL users.

I do not want to get anyones hopes up but here is another potential fix if this model has the setting.

Find the MTU setting (if the DSL-68U has one, wish i had investigated the options in more detail before returning my faulty one).

For ADSL set this to 1500 for FTTC set this to a max of 1452.
Save changes
Shut computer used to enter modem/routers config down
Disconnect the modem cable from the phone socket and then reconnect (you want a full fresh resync)
Wait until it is fully resynced
Power back up computer and other devices

This may help the FEC and CRC issues NO promises but it is entirely possible. Before anyone says this should not matter, it can and does on FTTC, the MTU setting being wrong on any type of PPPoE can be very fussy with regards to error correction.

interesting, if i see any user with vdsl fec/crc errors issues at asus forum i will ask for a try to see if will help ...
can not confirm, adsl here and is very good for me (pppoa vc,mux - mtu 1462 which getting maximum speed possible) compare it with pppoe llc snap 1492

To the original suggestion ... You reckon just changing mtu at the modem with out rebooting pc will not matter? (vdsl users)

EDIT

i know by now from my current settings what errors about i have ... will change mtu to see if will make difference (even with adsl)

 

[spoonbard]

Tinkering with a older and different Asus router i spotted as used in my local small computer shop which i picked up yesterday ive noticed something else as to why there may be an issue with the DSL-AC68U for FTTC users but not ADSL users.

I do not want to get anyones hopes up but here is another potential fix if this model has the setting.

Find the MTU setting (if the DSL-68U has one, wish i had investigated the options in more detail before returning my faulty one).

For ADSL set this to 1500 for FTTC set this to a max of 1452.
Save changes
Shut computer used to enter modem/routers config down
Disconnect the modem cable from the phone socket and then reconnect (you want a full fresh resync)
Wait until it is fully resynced
Power back up computer and other devices

This may help the FEC and CRC issues NO promises but it is entirely possible. Before anyone says this should not matter, it can and does on FTTC, the MTU setting being wrong on any type of PPPoE can be very fussy with regards to error correction.

I ended up just going ahead and getting a DSL-AC68U because I found one cheaper than its router-only twin, which I would have been buying anyway. I immediately installed the latest firmware and did a factory-reset, and have since kept all the settings on their defaults.

I'm on an FTTC connection (Zen Unlimited Fibre 1), and I tried setting it up as a modem/router earlier today. It logged 3000 CRC down errors in the first 10 mins, and carried on producing them at that rate.

I've just followed your instructions, and I've only had 106 in 25 mins - if it carries on at this pace, I'll have ~6100 in 24 hours. If I've been reading this thread correctly, that's a pretty acceptable figure, right?

I'll keep it running and report back with more details!