Anyone Using an Asus DSL-AC68U

Well I've only had mine a week or so, but yeah I feel for those who've had it through the months where it barely worked properly at all.

I mean my connection doesn't drop and it feels stable but that amount of CRC errors is worrisome.

Hopefully ASUS aren't finished with firmware updates now :(
 
I would imagine it's almost half way through it's firmware support period because technology in this area is moving so fast.

Having tried 2 of these last year with no real progress I'm surprised they haven't pulled it from UK shelves and offered those affected full refunds.
 
Last edited:
I'm surprised they didn't have a sit down and figure out what was going on with such poor feedback of the DSL-N66U but instead they popped this one out with very similar issues.

I think another part of the issue is that there are loads of settings a general user can change which doesn't help matters. People will mess about with settings when they see a bit of instability and totally ruin their profile without realising. I'm guilty of fiddling but always have a note of the original settings I had previously.

I still feel a two box method is the way forward at present after trying a few of the combo boxes this month. I think the best thing to do for me anyway is revert to that for now and maybe look into a combo unit further down the line (1-2 years).
 
I've been running a Fritz box 7490 since January with barely a hiccup.

With the ASUS I would probably get a few hundred CRC errors in a 24hr period along with a few dozen ES but with the Fritz box I'm averaging just 4 CRC and 1 ES every 24hr, even in really bad weather like today. The trouble with the ASUS is that you can't trust the stats because even when it seemed fairly stable DLM would still have a negative impact on your line regardless.
 
Last edited:
Mine is still apparently producing CRC spikes again. Looks like this problem hasn't been resolved after all :(. Worst of all there's no ASUS rep here now either so I think I'm going to abandon this device and stick it back in the box in the hope that one day they fix this mess, or when G.INP arrives for ECi cabinets (if BT Openreach ever do roll it out for ECI cabinets - feels like it's abandoned).

I'd try the Fritz!Box 7490 again but last time it kept periodically rebooting/crashing, and it doesn't officially seem to support multiple public IP addresses (or I can't figure out how to easily set it up on the device).
 
Under Network>Network Settings>IPV4 Settings there's this...



Wouldn't you then set the router IP to the last of your public IP block and associated subnet, disable DHCP and assign each of your devices one of the public IPs, with the router IP as the default gateway, and the subnet mask of the IP block.
 
Last edited:
Mine is still apparently producing CRC spikes again. Looks like this problem hasn't been resolved after all :(. Worst of all there's no ASUS rep here now either so I think I'm going to abandon this device and stick it back in the box in the hope that one day they fix this mess, or when G.INP arrives for ECi cabinets (if BT Openreach ever do roll it out for ECI cabinets - feels like it's abandoned).

I'm on G.INP and still get CRC errors in the thousands, even with stability adjustment at 10dB.
 
So how do I set this up to run from the HG612? Just in the WAN port settings?
I'm actually just tempted to return to my RT-N66U. That just worked flawlessly since install in January with the HG612. That way I can recoup my money from this and put it towards something that will work in the future.
 
Under Network>Network Settings>IPV4 Settings there's this...



Wouldn't you then set the router IP to the last of your public IP block and associated subnet, disable DHCP and assign each of your devices one of the public IPs, with the router IP as the default gateway, and the subnet mask of the IP block.

I'm going to give it another try when the internet here isn't in use, most likely late in the evening or early in the morning.

I did stumble across this too, which I translated to English - seemed like it might work with both LAN and public IP addresses at the same time (a bit like the HomeHub 4 did when I had used it when on BT Business).

EDIT: D'oh, forgot to post link - https://www.xs4all.nl/klantenservice/internet/instellen-subnet-vas-fritzbox-7390/.
 
Last edited:
The DSL-AC68U is pants on ADSL2+

This modem is pants on ADSL2+ (Firmware 5007)

Here are my logs for one of the MANY disconnects (almost daily).

2015-05-04 06:41:25 syslog: No response to 10 echo-requests
2015-05-04 06:41:25 syslog: Serial link appears to be disconnected.
2015-05-04 06:41:25 syslog: Connect time 4648.0 minutes.
2015-05-04 06:41:25 syslog: Sent 304772124 bytes, received 395489608 bytes.
2015-05-04 06:41:25 syslog: LCP down.
2015-05-04 06:41:26 kernel: Link State: PVC_0 logistic interface down.
2015-05-04 06:41:28 WAN Connection: Fail to connect with some issues.
2015-05-04 06:41:31 syslog: Connection terminated.
2015-05-04 06:41:31 kernel: mt7510_config
2015-05-04 06:41:31 kernel: tc3162_atm_close done
2015-05-04 06:41:31 syslog: Modem hangup
2015-05-04 06:41:31 syslog: LCP down.
2015-05-04 06:41:35 syslog: LCP is allowed to come up.
2015-05-04 06:41:35 syslog: qos.txtp.pcr = qos.rxtp.pcr = 0
2015-05-04 06:41:35 kernel: mt7510_atm_open
2015-05-04 06:41:35 kernel: vpi: 8
2015-05-04 06:41:35 kernel: vci: 35
2015-05-04 06:41:35 kernel: mt7510_atm_open vc 0:
2015-05-04 06:41:35 kernel: ATM over ADSL mode init
.......
2015-05-04 06:41:43 kernel: enter pppoatm_init_hook function
2015-05-04 06:41:43 kernel: mt7510_init_MPOA
2015-05-04 06:41:43 kernel: Init VC 0 MPOA Function
2015-05-04 06:41:43 kernel: MPOA Mode: MODE_ROUTER
2015-05-04 06:41:43 kernel: encapType: CON_PPPOA
2015-05-04 06:41:43 kernel: MuxType: MUX_VC
2015-05-04 06:41:43 kernel: Mode: MODE_ROUTER
2015-05-04 06:41:43 kernel: pppoatm_init_hook: success
2015-05-04 06:41:43 syslog: Using interface ppp0
2015-05-04 06:41:43 syslog: Connect: ppp0 <--> 8.35
2015-05-04 06:41:43 syslog: PAP authentication succeeded
2015-05-04 06:41:43 syslog: local IP address 87.203.xxx.xx
2015-05-04 06:41:43 syslog: remote IP address 80.106.xxx.xx
2015-05-04 06:41:43 syslog: primary DNS address 212.205.212.205
2015-05-04 06:41:43 syslog: secondary DNS address 195.170.0.1

Note the failed attempt at 2015-05-04 06:41:25 to ping a host, which we have NO control over

I captured the above syslog by setting up my Raspberry Pi as a syslog watcher.

Sorry the post is VERY late (compared to log time stamps), but my account took a long while to be created.

At the advice of ASUS it was sent back as not fit for purpose

I am 250 metres from the exchange and I get 20Mb/s download speeds using the EE BrightBox, which does not have the daily disconnects.
 
Jees, that's terrible!

It does seem as if ASUS have given up on this product. A while ago I thought progress was being made, but clearly it isn't entirely fixed and with the rep gone and nobody replacing him it does seem like we and other owners of this product have been abandoned. If I can get the Fritz!Box 7490 working with my public IPv4 subnet from Zen then I'll use that and put the DSL-AC68U in storage, I'll know later tonight if it works out or not. Hopefully the crashes/random reboots I got will also stop then.
 
Just an update to say that simoncraddock you appear to be right. Your information and that information I stumbled into appears to be the solution. Also port forwarding all UDP and TCP ports (1-65535) was needed to be done for each public IPv4 address (which essentially makes the Fritz!Box firewall non-existent for TCP and UDP incoming traffic for the public IPv4 addresses).

Furthermore, it looks like the router supports both LAN and WAN IP's at the same time, if that makes sense. Most routers can't do this due to NAT complications - so if this is really the case then I can eliminate needing two routers (one which solely works with WAN IP's, and the other which works with LAN IP's).

Attainable rate seems a bit less, currently around 75Mbps.
 
Back
Top Bottom