Anyone Using an Asus DSL-AC68U

So can I take it third ping is the one you are referring to, as the secondtimes out, and this is my actual ping. Is it good?
 
So can I take it third ping is the one you are referring to, as the secondtimes out, and this is my actual ping. Is it good?

All relative really - the final ping to the BBC is still 18ms, and that might be good depending on where you live. If you're in London or surrounding, then it could indicate a level of interleaving (8ms is usual) on a base 10ms ping time.

However if you're in Manchester say then that 18ms might be right given the distance from London.
 
I live in a village on the outskirts of a large town over 2600 metres from the exchange, nearest cabinet about 200 metres away....
 
Every hop to the BBC if fastpath will normally be 10ms or less, for me its 7-8ms.

If you do a tracert to google.com, then every hop is again typically under 10ms except (for me at least) a couple which will typically be around 20-30ms tops if you are fastpath and considerably more if you are not.

Code:
tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.246.103]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms 192.168.1.1
  2     6 ms     6 ms     6 ms  217.32.146.73
  3     7 ms     6 ms     6 ms  217.32.146.126
  4     7 ms     7 ms     7 ms  217.32.147.202
  5     7 ms     6 ms     7 ms  217.41.168.43
  6     7 ms     7 ms     7 ms  217.41.168.107
  7     7 ms     7 ms     7 ms  109.159.249.80
  8     7 ms     7 ms     7 ms  109.159.249.9
  9     8 ms     8 ms     7 ms  213.121.193.99
 10     7 ms     7 ms     7 ms  194.74.65.42
 11     *        *        *     Request timed out.
 12     8 ms     9 ms     8 ms  ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
 13    10 ms    10 ms    10 ms  132.185.255.165
 14     9 ms     8 ms     8 ms  fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]

Trace complete.

Code:
tracert google.com

Tracing route to google.com [216.58.210.14]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms 192.168.1.1
  2     6 ms     6 ms     6 ms  217.32.146.73
  3    23 ms     6 ms     7 ms  217.32.146.126
  4     7 ms     7 ms     7 ms  213.120.156.210
  5     7 ms     7 ms     6 ms  217.41.168.43
  6     7 ms     7 ms     7 ms  217.41.168.107
  7     7 ms     6 ms     7 ms  109.159.249.94
  8     7 ms     7 ms     7 ms  109.159.249.21
  9     8 ms     8 ms     8 ms  213.121.193.105
 10    13 ms     9 ms     7 ms  109.159.253.67
 11     8 ms     8 ms     7 ms  209.85.244.184
 12     8 ms     7 ms     8 ms  209.85.250.169
 13     8 ms     8 ms     7 ms  216.58.210.14

Trace complete.
 
Thanks for your help, well if I am not on fastpath then I wonder why not as my tracert to the same site is below:

Tracing route to www.google.com [74.125.24.106]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 24 ms 24 ms 23 ms ip-84-38-37-36.easynet.co.uk [84.38.37.36]
4 34 ms 29 ms 35 ms 72.14.219.13
5 25 ms 25 ms 25 ms 209.85.255.78
6 26 ms 27 ms 26 ms 209.85.253.94
7 35 ms 41 ms 41 ms 209.85.251.190
8 37 ms 32 ms 32 ms 72.14.235.141
9 * * * Request timed out.
10 34 ms 35 ms 35 ms de-in-f106.1e100.net [74.125.24.106]

The main road the cabinet is on floods when it rains, presently flooded, although the cabinet is raised up away from this road. Is there anyone I can contact to get me back onto fastpath as I don't recall it being as bad as this with the BT router and my speedtests were just below 39Mbps, now they are averaging around 27Mbps, the BT Wholesale Performance test is a download of 26.63, upload 8.11 and a ping of 43. Should I try reconnecting the BT modem?
 
Last edited:
The AC68U arrived this afternoon, and here we go so far

Code:
ASUSWRT DSL-AC68U_3.0.0.4 Mon Jan 12 06:52:14 UTC 2015
admin@DSL-AC68U:/tmp/home/root# cat /tmp/adsl/info_adsl.txt
outDiscards=31682
inDiscards=745
outBytes=3380319979
inBytes=573547230
outPkts=5165434
inPkts=7757586
fwVer= FwVer:5.5.1.126_B_A60901 HwVer:T14.F7_0.2

lineState=up
Opmode=ITU G.993.2(VDSL2)
SNRMarginDown=5.9 dB
AttenDown=10.9 dB
SNRMarginUp=5.8 dB
AttenUp=3.0 dB
DataRateDown=59705 kbps
DataRateUp=19243 kbps
WanListMode=1
FECDown=630
FECUp=310
CRCDown=70
CRCUp=13
HECDown=0
HECUp=0
ADSLUpTime= 5:01, 14 secs
ADSLActiveTime=0 min, 17 secs
PowerDown=14.0 dbm
PowerUp=6.9 dbm
ATURID=26005443434e0000
ATUCID=b5004244434da485
AttainUp=19243
AttainDown=73000
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#

Have I missed anything, or does it not report actual error seconds for use in DLM terms?
 
Thanks for your help, well if I am not on fastpath then I wonder why not as my tracert to the same site is below:

Tracing route to www.google.com [74.125.24.106]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 24 ms 24 ms 23 ms ip-84-38-37-36.easynet.co.uk [84.38.37.36]
4 34 ms 29 ms 35 ms 72.14.219.13
5 25 ms 25 ms 25 ms 209.85.255.78
6 26 ms 27 ms 26 ms 209.85.253.94
7 35 ms 41 ms 41 ms 209.85.251.190
8 37 ms 32 ms 32 ms 72.14.235.141
9 * * * Request timed out.
10 34 ms 35 ms 35 ms de-in-f106.1e100.net [74.125.24.106]

The main road the cabinet is on floods when it rains, presently flooded, although the cabinet is raised up away from this road. Is there anyone I can contact to get me back onto fastpath as I don't recall it being as bad as this with the BT router and my speedtests were just below 39Mbps, now they are averaging around 27Mbps, the BT Wholesale Performance test is a download of 26.63, upload 8.11 and a ping of 43. Should I try reconnecting the BT modem?

You are interleaved either to the tune of 8ms or 16ms from that. If you were fastpath it would only be the odd hop up in the 30ms mark and none of it would likely be 40+ms.

The Bt speedtest (IE speedtest.btwholesale.com) will typically report pings around 20ms (give or take 5ish ms) if 8ms interleaved or fastpath (depends on time of the day, its mood lol and how much load/amount of tests its doing) ping of 40ms+ from it and you are almost definitely interleaved.

You could try going back to the BT modem for a week or so to see if things improve. Does not hurt to try.
 
Had my first reset yesterday afternoon, strange one:
eb 20 14:06:24 WAN Connection: Ethernet link down.
Feb 20 14:06:24 stop_nat_rules: apply the redirect_rules!
Feb 20 14:07:09 WAN Connection: Ethernet link up.
Feb 20 14:07:09 rc_service: wanduck 584:notify_rc restart_wan_if 0
Feb 20 14:07:15 WAN Connection: ISP's DHCP did not function properly.

Thing is my connection has been perfectly stable, no dlm resets for three months so I do not understand why I am interleaved. Going back to the bt router today. Anyone remember the setting I need to put into the asus to make it an AP to the modem.
 
Thanks, found it on page 6. If my stats improve I'll post them up, its just a shame after all this time to give up and that asus can't seem to be bothered to get this unit to work in the way it's been advertised. They are due one snotty email...
 
Last edited:
Stats with the OR Modem reconnected:
Tracing route to www.google.com [74.125.24.103]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 20 ms 20 ms 21 ms ip-84-38-37-34.easynet.co.uk [84.38.37.3
4 20 ms 20 ms 23 ms 72.14.219.13
5 19 ms 20 ms 27 ms 209.85.255.76
6 17 ms 15 ms 15 ms proxy.google.com [216.239.51.5]
7 36 ms 30 ms 36 ms 209.85.250.216
8 24 ms 25 ms 24 ms 66.249.95.3
9 * * * Request timed out.
10 28 ms 27 ms 28 ms de-in-f103.1e100.net [74.125.24.103]

Trace complete.

BTW Performance Test:
D/L=28.09
U/L=8.69
Ping-23.50
 
Do the tracert to 216.58.210.14 (google again but normally a faster server to the tune of 5-10ms)
Might also want to flush your DNS after which may help things by 1-2ms more ;)
 
Do the tracert to 216.58.210.14 (google again but normally a faster server to the tune of 5-10ms)
Might also want to flush your DNS after which may help things by 1-2ms more ;)

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\Users\Chris>tracert 216.58.210.14

Tracing route to lhr08s06-in-f14.1e100.net [216.58.210.14]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 20 ms 20 ms 21 ms ip-84-38-37-36.easynet.co.uk [84.38.37.36]
4 23 ms 23 ms 23 ms 72.14.219.13
5 23 ms 23 ms 22 ms 209.85.255.78
6 22 ms 23 ms 23 ms 209.85.250.169
7 20 ms 19 ms 19 ms lhr08s06-in-f14.1e100.net [216.58.210.14]
 
:) thats about the best you are gonna get till the interleaving is gone. You definitely have in the region of a 8-16ms interleave from that latest id guess nearer 8ms. I wonder why you go through the easynet network? Whos your ISP (i thought i read it was plusnet maybe wrongly).

Have you tried removing the Asus altogether and going back entirely to whatever ISP gear was supplied? It may or may not shave another 1-2ms off tracerts and pings.
 
My ISP is Sky, so that's why easynet comes up. No I haven't considered removing the Asus altogether as I'm assuming its performance with the Sky supplied Open Reach modem would be far better than the Sky supplied sagem 101. Yes I will wait for the dlm to, hopefully, re-establishes fastpath.
Thanks for all your suggestions though, you've been a great help...
 
My ISP is Sky, so that's why easynet comes up. No I haven't considered removing the Asus altogether as I'm assuming its performance with the Sky supplied Open Reach modem would be far better than the Sky supplied sagem 101. Yes I will wait for the dlm to, hopefully, re-establishes fastpath.
Thanks for all your suggestions though, you've been a great help...

Ah right that explains the easynet routing :) (dunno why i thought you were plusnet probably misread someone elses post earlier in the thread).

Maybe give the current Openreach modem and Asus as a router combo for a week if there is no improvement then try replacing the Asus with the Sky router. You are not interleaved that bad (id guess 8ms) so providing you get a weeks worth of solid uptime and are as near as can be error free then it should get removed pretty quick, could happen within 48 hours if really lucky. Three to Five days from my experience is typical and a week or 2 if any further issues occur.

Good luck hopefully it puts you back to fastpath soon :)
 
I think one of my pings or tracerts might have been to plusnet as I seem to get a better reading from there. I would be dissapointed if the asus/or modem combo wasn't better than using the sagem as the wireless and wired connections with the asus are so much better than with the sky supplied setup.
 
Can someone look at my stats i used to have much better speeds and ping than i get now.

9XGrQg7.png


EebLVwX.png


DSL Settings:

KLJ53CA.png


DSL Log:

XQmwc4J.png


Thanx in advance.
 
I think one of my pings or tracerts might have been to plusnet as I seem to get a better reading from there. I would be dissapointed if the asus/or modem combo wasn't better than using the sagem as the wireless and wired connections with the asus are so much better than with the sky supplied setup.

In theory it should be fine with the Asus as JUST a router, though theory with this device is not always the reality ;)
Can someone look at my stats i used to have much better speeds and ping than i get now.
.....
Thanx in advance.

I doubt there will be too much you can do as you are only achieving 6Mb up and 27Mb down. You are likely interleaved to the tune of 16ms-32ms. Unless you had vastly superior results before the Asus then i would not be shocked if its basically performing as best as your line can.
 
In theory it should be fine with the Asus as JUST a router, though theory with this device is not always the reality ;)


I doubt there will be too much you can do as you are only achieving 6Mb up and 27Mb down. You are likely interleaved to the tune of 16ms-32ms. Unless you had vastly superior results before the Asus then i would not be shocked if its basically performing as best as your line can.

Well before i was put on a new line just over a week ago i was getting 34mbps down and 8mbps up with a 8-10 ping.
 
Back
Top Bottom