Anyone Using an Asus DSL-AC68U

Cheers chaps, shows new version now:

XgT3MC8.png
 
Just had my ADSL to FTTC regrade from Sky, left the sr102 on for the day of the change.

Previously had the ac68u connecting with o2 install details - no dice with VDSL unfortunately.

Went through the guide on the Sky forum written by Hiandy to the letter, wireshark on the router etc etc.

Still no connection I get sync fine, then it just sits there not even attempting to authenticate.

Rolled back the firmware to the older version suggested in the guide as well.

Any ideas at this stage are welcome, really missing the wireless performance/range
 
Unfortunately I can't comment on the Sky question, though someone else may be able to.

Does anyone have any feedback/comments so far on the latest firmware from ASUS? I'm tempted to try this some point this evening.
 
Well mine resynced again this morning and the my download has dropped for some reason despite my max down rate being way over 80mb.

Error wise it seems much better so far but my CRC errors I get seem to be caused by environmental factors rather than the line itself so I can go without any for a while then get 36,000 at once...
 
I've now put the DSL-AC68U back on. Initially (with default settings) am finding the usual trickle of CRC errors that I get on my line. I'll monitor it and update later on.
 
Ixel said:
I've now put the DSL-AC68U back on. Initially (with default settings) am finding the usual trickle of CRC errors that I get on my line. I'll monitor it and update later on.
Click to expand...
I got dlm'd around midday today and am now interleaved (only the 2nd time since I have used this device) but that was my fault for the resets I did last night to try to get the admin gui to show the correct version of firmware.
I am still syncing with good speeds 73 down and 19 up.
interleaved depth 2426.
I have only had 2 CRC errors (down) reported since 8:00am yesterday morning running under heavy load all day yesterday fastpath.
As far as I can see after a day and a half the firmware seems a lot more stable than any previous one.
As I said in an earlier post as well the USB port is functioning correctly now.
I will just leave it until it goes back to fastpath. (took 5 days last time) and
report back.
The device is running all default DSL modem settings.
 
Code: 
>tcapi get Info_Adsl ADSLUpTime;wan vdsl2 show mgcnt
59 min, 51 secs
near-end path0 fec:     0(0)
near-end path0 crc:     57(57)
near-end fec sec:       0(0)
near-end err sec:       46(46)
near-end ses sec:       0(0)
near-end los sec:       0(0)
near-end ua  sec:       0(0)
far-end path0 fec:      2(879358)
far-end path0 crc:      0(8834)
far-end fec sec:        1(29308)
far-end err sec:        0(7801)
far-end ses sec:        0(0)
far-end los sec:        0(1212)
far-end ua  sec:        0(48567)
>tcapi get Info_Adsl ADSLUpTime;wan vdsl2 show mgcnt
 1:15, 43 secs
near-end path0 fec:     0(0)
near-end path0 crc:     1153(79)
near-end fec sec:       0(0)
near-end err sec:       67(64)
near-end ses sec:       3(3)
near-end los sec:       0(0)
near-end ua  sec:       0(0)
far-end path0 fec:      3(879359)
far-end path0 crc:      0(8834)
far-end fec sec:        2(29309)
far-end err sec:        0(7801)
far-end ses sec:        0(0)
far-end los sec:        0(1212)
far-end ua  sec:        0(48567)

CRC error spike occurred. Nothing to cause a disconnection, yet, however. All default settings, so the dynamic line adjustment hasn't done anything yet.
 
I think a lot of peoples confidence has faded in this product. You don't really see much in the way of people constantly checking for issues on other bits of equipment.
Certainly for myself anyway, I tended to check more when using this device as compared to the HG612 or D6400. Those devices I just plugged in and left to get on with it.
 
Well, given the CRC errors spiked and didn't on other devices I used, I've disabled dynamic line adjustment and have set ESNP to 'stable'. I'll continue monitoring the connection occasionally.

EDIT: Currently it's better with ESNP set to 'stable'.
 
Last edited:
I tried the new firmware and i average 62 CRC errors an hour compared to the 54 on the old firmware. I noticed that it hadnt updated the firmware drivers so i reset the router. It is now showing the right firmware drivers etc so i am just sitting tight now and see what happens
 
Nearly 100,000 CRC down errors in a day and a half. Something is seriously wrong somewhere with my connection. The error spikes are that bad that connection drops for 10-15 seconds.
 
Nope, the error spike are random, I'll not get any for a few hours then I'll get thousands in a 10-15 second period which causes the connection to lag out but not drop.

Nothing has changed in the household between the time I was on BT Infinity and now with plusnet so I'm thinking this is an external issue which plusnet need to look at.

I'm now at 261,000 CRC down errors in just 48 hours...
 
Having read people having success on this firmware I decided to gove it another go.

Within 10 seconds the CRC errors started, only 1 or 2 every ten seconds or so, but after 7 minutes they started piling up at a ridiculous rate, I was getting around 7000 every time the screen refreshed.

I let it get to aroung 500,000 and pulled the plug.

I think I'm not going to try this as a modem any more!
 
You must log in or register to reply here.
Back
Top Bottom