ASUS DSL - AC68U Modem Hangup

Hi, just bought a brand new ASUS DSL-AC68U modem/router for new Zen fibre.
Unfortunately it is continually disconnecting from the net,sometimes it will go 5 mins others a few hours.

I am putting some stats up, can anybody tell me from those if it's a hardware issue or a line issue.

Thanks.



Sep 10 23:04:12 WAN Connection: WAN was restored.
Sep 10 23:17:18 WAN Connection: Ethernet link down.
Sep 10 23:17:18 stop_nat_rules: apply the redirect_rules!
Sep 10 23:17:33 WAN Connection: WAN was restored.
Sep 10 23:17:33 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
Sep 10 23:17:52 pppd[631]: Serial link appears to be disconnected.
Sep 10 23:17:53 WAN Connection: Fail to connect with some issues.
Sep 10 23:17:53 stop_nat_rules: apply the redirect_rules!
Sep 10 23:17:58 pppd[631]: Connection terminated.
Sep 10 23:17:58 pppd[631]: Modem hangup
Sep 10 23:18:04 WAN Connection: Ethernet link down.
Sep 10 23:18:09 pppd[631]: Connected to 00:30:88:00:00:07 via interface vlan100
Sep 10 23:18:09 pppd[631]: Connect: ppp0 <--> vlan100
Sep 10 23:18:09 pppd[631]: CHAP authentication succeeded
Sep 10 23:18:09 pppd[631]: peer from calling number 00:30:88:00:00:07 authorized
Sep 10 23:18:09 pppd[631]: local IP address 217.155.204.160
Sep 10 23:18:09 pppd[631]: remote IP address 62.3.84.17
Sep 10 23:18:09 pppd[631]: primary DNS address 212.23.6.100
Sep 10 23:18:09 pppd[631]: secondary DNS address 212.23.3.100
Sep 10 23:18:10 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
Sep 10 23:18:10 rc_service: ip-up 2007:notify_rc stop_upnp
Sep 10 23:18:10 rc_service: ip-up 2007:notify_rc start_upnp
Sep 10 23:18:10 rc_service: waitting "stop_upnp" via ip-up ...
Sep 10 23:18:10 miniupnpd[1894]: received signal 15, good-bye
Sep 10 23:18:10 WAN Connection: WAN was restored.
Sep 10 23:18:11 miniupnpd[2042]: HTTP listening on port 39905
Sep 10 23:18:11 miniupnpd[2042]: Listening for NAT-PMP traffic on port 5351
Sep 10 23:59:23 WAN Connection: Ethernet link down.
Sep 10 23:59:23 stop_nat_rules: apply the redirect_rules!
Sep 10 23:59:53 WAN Connection: WAN was restored.
Sep 10 23:59:53 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
Sep 11 00:00:17 pppd[631]: Serial link appears to be disconnected.
Sep 11 00:00:18 WAN Connection: Fail to connect with some issues.
Sep 11 00:00:18 stop_nat_rules: apply the redirect_rules!
Sep 11 00:00:23 WAN Connection: Ethernet link down.
Sep 11 00:00:23 pppd[631]: Connection terminated.
Sep 11 00:00:24 pppd[631]: Modem hangup
Sep 11 00:00:34 pppd[631]: Connected to 00:30:88:00:00:07 via interface vlan100
Sep 11 00:00:34 pppd[631]: Connect: ppp0 <--> vlan100
Sep 11 00:00:35 pppd[631]: CHAP authentication succeeded
Sep 11 00:00:35 pppd[631]: peer from calling number 00:30:88:00:00:07 authorized
Sep 11 00:00:35 pppd[631]: local IP address 217.155.204.160
Sep 11 00:00:35 pppd[631]: remote IP address 62.3.84.19
Sep 11 00:00:35 pppd[631]: primary DNS address 212.23.6.100
Sep 11 00:00:35 pppd[631]: secondary DNS address 212.23.3.100
Sep 11 00:00:35 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
Sep 11 00:00:35 rc_service: ip-up 2334:notify_rc stop_upnp
Sep 11 00:00:35 rc_service: ip-up 2334:notify_rc start_upnp
Sep 11 00:00:35 rc_service: waitting "stop_upnp" via ip-up ...
Sep 11 00:00:35 miniupnpd[2042]: received signal 15, good-bye
Sep 11 00:00:37 miniupnpd[2368]: HTTP listening on port 56254
Sep 11 00:00:37 miniupnpd[2368]: Listening for NAT-PMP traffic on port 5351
Sep 11 00:00:38 WAN Connection: WAN was restored.
Sep 11 02:31:12 WAN Connection: Ethernet link down.
Sep 11 02:31:12 stop_nat_rules: apply the redirect_rules!
Sep 11 02:31:37 WAN Connection: WAN was restored.
Sep 11 02:31:37 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
Sep 11 02:31:48 pppd[631]: Serial link appears to be disconnected.
Sep 11 02:31:52 WAN Connection: Fail to connect with some issues.
Sep 11 02:31:52 stop_nat_rules: apply the redirect_rules!
Sep 11 02:31:54 pppd[631]: Connection terminated.
Sep 11 02:31:54 pppd[631]: Modem hangup
Sep 11 02:31:57 WAN Connection: Ethernet link down.
Sep 11 02:32:04 pppd[631]: Connected to 00:30:88:00:00:07 via interface vlan100
Sep 11 02:32:04 pppd[631]: Connect: ppp0 <--> vlan100
Sep 11 02:32:05 pppd[631]: CHAP authentication succeeded
Sep 11 02:32:05 pppd[631]: peer from calling number 00:30:88:00:00:07 authorized
Sep 11 02:32:05 pppd[631]: local IP address 217.155.204.160
Sep 11 02:32:05 pppd[631]: remote IP address 62.3.84.23
Sep 11 02:32:05 pppd[631]: primary DNS address 212.23.6.100
Sep 11 02:32:05 pppd[631]: secondary DNS address 212.23.3.100
Sep 11 02:32:05 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
Sep 11 02:32:05 rc_service: ip-up 3441:notify_rc stop_upnp
Sep 11 02:32:05 rc_service: ip-up 3441:notify_rc start_upnp
Sep 11 02:32:05 rc_service: waitting "stop_upnp" via ip-up ...
Sep 11 02:32:05 miniupnpd[2368]: received signal 15, good-bye
Sep 11 02:32:07 miniupnpd[3475]: HTTP listening on port 40857
Sep 11 02:32:07 miniupnpd[3475]: Listening for NAT-PMP traffic on port 5351
Sep 11 02:32:07 WAN Connection: WAN was restored.
Sep 11 02:39:08 WAN Connection: Ethernet link down.
Sep 11 02:39:08 stop_nat_rules: apply the redirect_rules!
Sep 11 02:39:23 pppd[631]: Serial link appears to be disconnected.
Sep 11 02:39:29 pppd[631]: Connection terminated.
Sep 11 02:39:29 pppd[631]: Modem hangup
Sep 11 02:39:55 pppd[631]: Connected to 00:30:88:00:00:07 via interface vlan100
Sep 11 02:39:55 pppd[631]: Connect: ppp0 <--> vlan100
Sep 11 02:39:55 pppd[631]: CHAP authentication succeeded
Sep 11 02:39:55 pppd[631]: peer from calling number 00:30:88:00:00:07 authorized
Sep 11 02:39:55 pppd[631]: local IP address 217.155.204.160
Sep 11 02:39:55 pppd[631]: remote IP address 62.3.84.19
Sep 11 02:39:55 pppd[631]: primary DNS address 212.23.6.100
Sep 11 02:39:55 pppd[631]: secondary DNS address 212.23.3.100
Sep 11 02:39:56 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
Sep 11 02:39:56 rc_service: ip-up 3544:notify_rc stop_upnp
Sep 11 02:39:56 miniupnpd[3475]: received signal 15, good-bye
Sep 11 02:39:56 rc_service: ip-up 3544:notify_rc start_upnp
Sep 11 02:39:56 miniupnpd[3576]: HTTP listening on port 38946
Sep 11 02:39:56 miniupnpd[3576]: Listening for NAT-PMP traffic on port 5351
Sep 11 02:39:58 WAN Connection: WAN was restored.

Chase down firmware updates, the original DSL-55 review unit was a dog until newer firmware arrived.

With no reason given the modem hangup it is hard to say, not uncommon for xDSL microcode to need tweaking on modems.

In reply to a post by MrSaffron:

Chase down firmware updates, the original DSL-55 review unit was a dog until newer firmware arrived.

With no reason given the modem hangup it is hard to say, not uncommon for xDSL microcode to need tweaking on modems.

Thanks,I have already got the newest firmware and I haven't a clue how to tweak it.

If I knew if it was the hardware or the actual phone line it would be a start.

There should be a router stats type page, if the noise margin (SNR) figure is totally stable then probably not the line that's the issue, if the SNR margin is wandering around and particularly low once the sun has set then how the modem is handling the noise looks to be the issue.

Microcode you cannot tweak that is down to the Asus developers, are there any VDSL config options available to you at all.

In reply to a post by MrSaffron:

There should be a router stats type page, if the noise margin (SNR) figure is totally stable then probably not the line that's the issue, if the SNR margin is wandering around and particularly low once the sun has set then how the modem is handling the noise looks to be the issue.

Microcode you cannot tweak that is down to the Asus developers, are there any VDSL config options available to you at all.

I have a table called DSL log and that is showing SNR both up and down as 5.9 d.B it refreshes every few seconds and only changes to 6.0 now and again.

As regards config options there are so many I think assuming this problem carries on my best bet will be ringing Asus support so I can change anything they recommend.

At the moment it hasn.t cut off for about 4 hours so improving.

Does it have an option for the VDSL profile? E.g. 8c, 17a, 30a? Needs to be 17a or something that includes that.

PPPoE?

Edited by RobertoS (Thu 11-Sep-14 17:21:11)

In reply to a post by John99:

In reply to a post by MrSaffron:

Chase down firmware updates, the original DSL-55 review unit was a dog until newer firmware arrived.

With no reason given the modem hangup it is hard to say, not uncommon for xDSL microcode to need tweaking on modems.

Thanks,I have already got the newest firmware and I haven't a clue how to tweak it.

If I knew if it was the hardware or the actual phone line it would be a start.

You could use the BT Openreach supplied VDSL modem to test the line, that should tell you if it's a line fault.

In reply to a post by RobertoS:

Does it have an option for the VDSL profile? E.g. 8c, 17a, 30a? Needs to be 17a or something that includes that.

PPPoE?

Thanks for that.

Yes I sent a feedback request via the router settings page and I had an e-mail within an hour telling me to change 3 settings and it's put the SNR up to 9.6 dB which may have cured it, time will tell,

Any chance you could detail what the fix was? I'm having the exact same problem with mine.

PM to you.