Anyone Using an Asus DSL-AC68U

DjaKB6r.png


After 2 days uptime, no disconnects at all.. maxing out download/upload rate
crcs seem about average on upload and download lol but no issues here and this is not even the test firmware i cant wait to try it out but i think im going to hold out for the final version :D im 100% sure i wont get bit by the DLM with these low crc`s.
 
PlumpMonkey said:
I finally switched back to this modem this morning in order to gather the debug logs as requested by ASUS. Inspired by "sumowesley" I performed a full factory reset before making the required settings change and this morning it seems a lot more stable. Accoring the the DSL log page it has been up for two hours 9 minutes with 0 CRC errors.

Interestingly the debug tool output they have given me is showing something else....

Code: 
Tx_CRC[0]  = 0
Tx_FEC[0]  = 0
Tx_ERR_SEC = 0
Tx_FEC_SEC = 0
Rx_CRC[0]  = 4
Rx_FEC[0]  = 12330715
Rx_ERR_SEC = 1
Rx_FEC_SEC = 6053
Near-end total: los=0, sef=0, lpr=0
Far-end  total: los=1, sef=1, lpr=0
VDSL2 Sync-Up Time:  0 Day(s)  1:45:21

The FEC count is increasing rapidly. But as yet Ive not noticed any kind of issus with using the connection.

I need to run this debug tool for 24 hours so lets see what happens!
Click to expand...

Debug tool? That looks like it gives you more information about statistics, e.g. error seconds. Is that something they only have access to?

--

Also from a post I did on another forum yesterday:
Posting some more graphs from my device - http://imgur.com/a/KuMmt

What mostly peaks my curiousity is the major fluctuation on the SNR for both US and DS between 16:30~ to 21:00~. I haven't noticed this before. I imagine this could either be something interfering with the connection and relates to the CRC errors I have, or possibly a fault beginning to show itself, or perhaps it's just the ASUS's modem? Obviously without a Hlog and QLN there's no real easy for anyone here to analyse this I'd assume.

I'm really hoping the MK3 SSFP will arrive tomorrow at the very least, as soon as it does I'll probably run the ASUS for another 24-48 hours to observe if it has helped or not. After that, if it hasn't helped or a problem may still exist, then I'll switch to the HG612, start logging and then make a thread in the FTTC issues section. I hope it's not another possibility of a battery contact again.

EDIT: Seems I had a disconnection shortly after that (a major CRC spike again). Since reconnection my power has changed, SNRM is a tad lower on downstream (though I believe stabilised), and less errors occurring at the moment. Also around 11:45am I did a reconnection myself (switching from MK1 to MK2 SSFP as I was comparing).

--

I've gone back to the HG612 temporarily, so far I can't identify anything odd on the QLN and Hlog, although the trickle of CRC's still exist. I'm trying my best to get the speed banding lifted before I re-attempt using the ASUS again. I've had a MK3 SSFP arrive this morning and have also switched to that. I'm waiting on the ferrite toroid.
 
Ixel said:
Debug tool? That looks like it gives you more information about statistics, e.g. error seconds. Is that something they only have access to?
Click to expand...

It was a tool they provided me to gather some more logs. Its not very user friendly. You basically have to put the modem into a bridge mode which then causes port 4 of the Lan connections to spew out raw debug. You then have to install a couple of tools on your PC and connect it up to port 4 to capture it so it uses up a ethernet port on your PC for the duration of the test. Thankfully I have dual ethernet ports on my PC.

Its spewing out pages and pages of numbers every few seconds. In amongst that is the FEC count.

Interestingly though the output from here is now wildly different to the modem status page. The modem status page is now at 4hrs 3 mins uptime and 0 CRC errors, but the debug is saying

Code: 
Tx_CRC[0]  = 0
Tx_FEC[0]  = 1
Tx_ERR_SEC = 0
Tx_FEC_SEC = 1
Rx_CRC[0]  = 4
Rx_FEC[0]  = 25806647
Rx_ERR_SEC = 1
Rx_FEC_SEC = 12745
Near-end total: los=0, sef=0, lpr=0
Far-end  total: los=1, sef=1, lpr=0
VDSL2 Sync-Up Time:  0 Day(s)  3:36:53

Still, its looking way better. The last time I tested this firmware it wouldnt stay up more than about 2-3 hours and would generate CRC errors every minute or two.... Maybe the full factory reset helped.
 
It is good news Asus are using a test setup to gain more information as too what the router/modem is up too, well done for being the guinea pig. Some good I hope will come from it. Though I will wait until a proper firmware is released and bypass this beta one before I flash mine...
 
I see. Sounds interesting, might be useful. Is it possible to PM me a copy of the tool/instructions? If not then I'll try and ask ASUS for it.

It frustrates me how the GUI and /tmp/adsl/info_stats.txt don't show ES counts. Would make it so I could graph and count ES more accurately.
 
Studying the TC Console, it appears to open up access to the modem's operating system/firmware via LAN port 4. Telnet access becomes available on IP 169.254.0.1. I've tried logging in with the username admin and password admin but they don't seem to work (PuTTY). I'm guessing I'm missing something.

EDIT: I'm in, the login was admin:1234

Code: 
tc>ls
bin      dev      lib      mnt      proc     sys      userfs   var
boaroot  etc      linuxrc  opt      sbin     tmp      usr
tc>uname -a
Linux tc 2.6.36 #50 SMP Wed Oct 22 17:57:22 CST 2014 mips unknown
tc>cat /proc/cpuinfo
system type             : Ralink MT751020 SOC
processor               : 0
cpu model               : MIPS 34Kc V5.5
BogoMIPS                : 430.89
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 64
extra interrupt vector  : yes
hardware watchpoint     : yes, count: 4, address/irw mask: [0x0ffc, 0x0490, 0x0ff8, 0x0ffb]
ASEs implemented        : mips16 dsp mt
shadow register sets    : 1
core                    : 0
VCED exceptions         : not available
VCEI exceptions         : not available

processor               : 1
cpu model               : (null) V5.5
BogoMIPS                : 323.58
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 64
extra interrupt vector  : yes
hardware watchpoint     : yes, count: 4, address/irw mask: [0x0ffc, 0x0490, 0x0ff8, 0x0ffb]
ASEs implemented        : mips16 dsp mt
shadow register sets    : 1
core                    : 0
VCED exceptions         : not available
VCEI exceptions         : not available

processor               : 2
cpu model               : (null) V5.5
BogoMIPS                : 323.58
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 64
extra interrupt vector  : yes
hardware watchpoint     : yes, count: 4, address/irw mask: [0x0ffc, 0x0490, 0x0ff8, 0x0ffb]
ASEs implemented        : mips16 dsp mt
shadow register sets    : 1
core                    : 0
VCED exceptions         : not available
VCEI exceptions         : not available

processor               : 3
cpu model               : (null) V5.5
BogoMIPS                : 323.58
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 64
extra interrupt vector  : yes
hardware watchpoint     : yes, count: 4, address/irw mask: [0x0ffc, 0x0490, 0x0ff8, 0x0ffb]
ASEs implemented        : mips16 dsp mt
shadow register sets    : 1
core                    : 0
VCED exceptions         : not available
VCEI exceptions         : not available

tc>

There's also a web interface on 169.254.0.1 - same login. See screenshot: http://i.imgur.com/MfdSduP.png
 
Last edited:
someone should ask them or who ever chats to asus if they can also add more statistics in the dsl log when they release the new firmware as they might do it, worth a try :D

would love to see error seconds count in there.
 
A quick update

I have been running the test firmware since last Wednesday. First 20 hours or so went really well (63Mbps, 0 CRC down, 0 CRC up).

Line reset took place at 4:29am on the Friday(assumed BT given the time) and then there have been a couple of resets since that one. Line is still connected OK and miles better than before but some CRC activity has been taking place albeit small:
tcdrQqh.png
 
Sure wish my line was stable as that, for some odd reason I'm getting CRC blips (1-2 CRC) every 5-10 minutes, even on the HG612 :(. I've tried a ferrite toroid with 5 turns this morning and no difference at the moment, I might try 7 turns if the hole permits.

EDIT: Looking at your speed vs attainable, looks like you're just speed banded and not interleaved, but can't be certain. I'm on 49/19 (was 49/15 a week or so ago after the ASUS wobbly of multiple re-sync). I'm trying to get back to 80/20, I remain on fastpath though which is good. If I was interleaved then the ES would most likely reduce and convince DLM to make the speed banding rise.
 
Last edited:
I'm using this Router with an ADSL2 line (wont get fibre till next year if BT can be believed), its running fine for about 10 hours a time then I get a message saing the WAN cable is unplugged, however it says that the ADSL status is UP but I have no internet connection (DSL light is on but the internet light is off).

In the log it says hung up and so im assuming its an issue with getting details from BT as the line is showing no errors.

Anybody know if I should be using something different for my ADSL2 settings or account name?

Im using this currently;

username: [email protected]
password: BT (if required)
VCP: 0
VCI: 38
VPI/VCI standard
MTU: 1500 (or closest value to that)
 
xiNP7Ng.png


none test firmware 5+ days uptime no drops in dsl sync.
max speed 80up/20down *75downreal*19downreal....

crcs are still low for the time i have been up no issues here and line seems to be working fine but cant wait to give the final firmware a try when they have ironed out the beta to see if i can reduce the crc`s even more, with the crcs im currently getting i dont have issues with dlm anymore.


sumowesley
looking at your stats you seem to have much lower snr down and snr up than i do but your still having issues, in dsl sync as well as lower speeds, i don't understand that lol
 
Last edited:
Sync and speeds etc.

sumowesley
looking at your stats you seem to have much lower snr down and snr up than i do but your still having issues, in dsl sync as well as lower speeds, i don't understand that lol
Click to expand...

I think I'm still on the tail end of some DLM speed limitations so it may be a few days yet before I get speeds back up to full. I seems to have peaked at 68Mbps on the HH5 when all was well so I should be there or thereabouts. Not sure about the syncs - I've had three that I haven't been responsible for which is many fewer than the previous version of firmware.

This is such a functional piece of kit I'm really pleased that it has been relatively stable for the last few days. Long may it continue.
 
Well got this two days ago and i think it is a great router however there does seem to be something iffy.

It replaced a home hub 5 and so far i have noticed better wireless both in range and speed but that was to be expected my internet also feels abit snappier? if that makes sense also the amount you can do in the router settings is truely amazing and you seem to have complete control over everything.

Having had it setup for two days the first day i saw a minor increase in download and upload and a lower ping and then in the morning of the second day it reset and i have lost about 10% of my internet i am now sitting at 58mb down 18 up and my ping has gone from 14-15 in speedtest's to 30 :(

Having checked the dsl log i have only had 30 errors in 24 hours so compared to other's i think this is good? but i am abit surprised by the drop in speed and i can only think it is the dlm realising that i dont have a home hub 5 anymore so i must be punished :(
 
It probably has been resetting without you realising and DLM has taken exception to it.

Ive had to swap mine back out after testing the beta firmware and some settings from Asus because it was still resetting 1-2 times a day. DLM whacked me with the naughty stick and now Im at 41/20 where the home hub used to work at about 69/20. Its probably going to take 2+ weeks of using the Homehub before DLM forgives me from this much of a drop.

In my experience this modem should be avoided for VDSL. Others have had some luck with the new firmware though.
 
PlumpMonkey said:
It probably has been resetting without you realising and DLM has taken exception to it.

Ive had to swap mine back out after testing the beta firmware and some settings from Asus because it was still resetting 1-2 times a day. DLM whacked me with the naughty stick and now Im at 41/20 where the home hub used to work at about 69/20. Its probably going to take 2+ weeks of using the Homehub before DLM forgives me from this much of a drop.

In my experience this modem should be avoided for VDSL. Others have had some luck with the new firmware though.
Click to expand...

I was dropped from 74/20 to 49/15. I'm now up to 49/20, but unfortunately DLM shows no indication of putting me back to 74/20 or higher, or even increasing the downstream rate, despite using the ECI /r for a while now. The multiple re-syncs on the official latest firmware caused DLM to speed band me severely (like you).
 
I think I've been lucky this time around - with the beta firmware, I was getting more CRCs than with the Billion 8800NL but nothing too bad, however between midnight and 8am yesterday there was a burst of about 4000 downstream CRCs. Was fully expecting to be DLMd, but have stayed on fastpath when I was expecting to be interleaved this morning.

It's still not right, but it looks like a step in the right direction from ASUS.
 
You must log in or register to reply here.
Back
Top Bottom