Asus DSL AC68U Dropping connection randomly

[teeejay]

Hey guys,

I hope, that I posted this in a right section, if not, I do apologize.

as the title states, I've got this modem/router combo. My previous modem/router was Comtrend VR-3026e (internal antenna, basic stuff from the ISP, which is O2).

I wanted to buy some higher end model, because wi-fi connection from Comtrend was terrible, so I moved onto Asus one and wi-fi improvement was night and day difference. (before it I tried extenders etc. but it did not work well)

Problem: In a totally random times, it drops the connection, it does not last for more than 30 sec. I will post you system log:

Drop times: 00:20:40, 00:21:20, 11:38:19, 13:12:57, 13:13:42, 13:55:29, 14:55:58, 15:42:10, 18:49:17

Also: I called to my ISP, provided him my system log with times, when the connection was lost and I was told that there is nothing in their log, that the connection is perfectly stable. I called there twice on a different occasions.

1. Jan 24 00:02:30 miniupnpd[13061]: upnp_event_process_notify: connect(192.168.1.39:2869): Connection timed out
2. Jan 24 00:20:40 WAN Connection: Ethernet link down.
3. Jan 24 00:20:40 stop_nat_rules: apply the redirect_rules!
4. Jan 24 00:21:15 WAN Connection: WAN was restored.
5. Jan 24 00:21:15 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
6. Jan 24 00:21:17 pppd[488]: Serial link appears to be disconnected.
7. Jan 24 00:21:17 pppd[488]: Connection terminated.
8. Jan 24 00:21:20 WAN Connection: Fail to connect with some issues.
9. Jan 24 00:21:20 stop_nat_rules: apply the redirect_rules!
10. Jan 24 00:21:27 pppd[488]: Connected to 00:30:88:1d:ff:dc via interface vlan100
11. Jan 24 00:21:27 pppd[488]: Connect: ppp0 <--> vlan100
12. Jan 24 00:21:27 pppd[488]: PAP authentication succeeded
13. Jan 24 00:21:27 pppd[488]: peer from calling number 00:30:88:1D:FFC authorized
14. Jan 24 00:21:27 pppd[488]: local IP address
15. Jan 24 00:21:27 pppd[488]: remote IP address
16. Jan 24 00:21:27 pppd[488]: primary DNS address
17. Jan 24 00:21:27 pppd[488]: secondary DNS address
18. Jan 24 00:21:27 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
19. Jan 24 00:21:28 wan: finish adding multi routes
20. Jan 24 00:21:28 rc_service: ip-up 14736:notify_rc stop_upnp
21. Jan 24 00:21:28 rc_service: ip-up 14736:notify_rc start_upnp
22. Jan 24 00:21:28 rc_service: waitting "stop_upnp" via ip-up ...
23. Jan 24 00:21:28 miniupnpd[13061]: shutting down MiniUPnPd
24. Jan 24 00:21:29 ntp: start NTP update
25. Jan 24 00:21:30 miniupnpd[14768]: version 1.9 started
26. Jan 24 00:21:30 miniupnpd[14768]: HTTP listening on port 36841
27. Jan 24 00:21:30 miniupnpd[14768]: Listening for NAT-PMP/PCP traffic on port 5351
28. Jan 24 00:21:30 WAN Connection: WAN was restored.
29. Jan 24 00:59:57 ntp: start NTP update
30. Jan 24 01:59:59 ntp: start NTP update
31. Jan 24 03:00:01 ntp: start NTP update
32. Jan 24 03:59:57 ntp: start NTP update
33. Jan 24 04:59:57 ntp: start NTP update
34. Jan 24 05:59:59 ntp: start NTP update
35. Jan 24 06:59:57 ntp: start NTP update
36. Jan 24 07:59:57 ntp: start NTP update
37. Jan 24 08:59:59 ntp: start NTP update
38. Jan 24 10:00:01 ntp: start NTP update
39. Jan 24 10:59:57 ntp: start NTP update
40. Jan 24 11:38:19 WAN Connection: Ethernet link down.
41. Jan 24 11:38:19 stop_nat_rules: apply the redirect_rules!
42. Jan 24 11:38:43 WAN Connection: WAN was restored.
43. Jan 24 11:38:43 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
44. Jan 24 11:59:59 ntp: start NTP update
45. Jan 24 13:00:01 ntp: start NTP update
46. Jan 24 13:12:57 WAN Connection: Ethernet link down.
47. Jan 24 13:12:57 stop_nat_rules: apply the redirect_rules!
48. Jan 24 13:13:32 WAN Connection: WAN was restored.
49. Jan 24 13:13:32 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
50. Jan 24 13:13:41 pppd[488]: Serial link appears to be disconnected.
51. Jan 24 13:13:41 pppd[488]: Connection terminated.
52. Jan 24 13:13:42 WAN Connection: Fail to connect with some issues.
53. Jan 24 13:13:42 stop_nat_rules: apply the redirect_rules!
54. Jan 24 13:13:52 pppd[488]: Connected to 00:30:88:1d:ff:dc via interface vlan100
55. Jan 24 13:13:52 pppd[488]: Connect: ppp0 <--> vlan100
56. Jan 24 13:13:52 pppd[488]: PAP authentication succeeded
57. Jan 24 13:13:52 pppd[488]: peer from calling number 00:30:88:1D:FFC authorized
58. Jan 24 13:13:52 pppd[488]: local IP address
59. Jan 24 13:13:52 pppd[488]: remote IP address
60. Jan 24 13:13:52 pppd[488]: primary DNS address
61. Jan 24 13:13:52 pppd[488]: secondary DNS address
62. Jan 24 13:13:52 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
63. Jan 24 13:13:52 wan: finish adding multi routes
64. Jan 24 13:13:57 WAN Connection: WAN was restored.
65. Jan 24 13:13:58 rc_service: ip-up 19689:notify_rc stop_upnp
66. Jan 24 13:13:58 rc_service: ip-up 19689:notify_rc start_upnp
67. Jan 24 13:13:58 rc_service: waitting "stop_upnp" via ip-up ...
68. Jan 24 13:13:58 miniupnpd[14768]: shutting down MiniUPnPd
69. Jan 24 13:13:59 ntp: start NTP update
70. Jan 24 13:13:59 miniupnpd[19721]: version 1.9 started
71. Jan 24 13:13:59 miniupnpd[19721]: HTTP listening on port 38142
72. Jan 24 13:13:59 miniupnpd[19721]: Listening for NAT-PMP/PCP traffic on port 5351
73. Jan 24 13:39:20 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
74. Jan 24 13:39:21 kernel: sizeof forward param = 160
75. Jan 24 13:39:36 kernel: Stop the IPS/AppID engine...
76. Jan 24 13:39:37 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
77. Jan 24 13:39:57 rc_service: httpd 438:notify_rc start_webs_update
78. Jan 24 13:55:29 WAN Connection: Ethernet link down.
79. Jan 24 13:55:29 stop_nat_rules: apply the redirect_rules!
80. Jan 24 13:55:45 WAN Connection: WAN was restored.
81. Jan 24 13:55:45 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
82. Jan 24 13:59:57 ntp: start NTP update
83. Jan 24 14:55:58 WAN Connection: Ethernet link down.
84. Jan 24 14:55:58 stop_nat_rules: apply the redirect_rules!
85. Jan 24 14:56:23 WAN Connection: WAN was restored.
86. Jan 24 14:56:23 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
87. Jan 24 14:59:57 ntp: start NTP update
88. Jan 24 15:42:10 WAN Connection: Ethernet link down.
89. Jan 24 15:42:10 stop_nat_rules: apply the redirect_rules!
90. Jan 24 15:42:51 pppd[488]: Serial link appears to be disconnected.
91. Jan 24 15:42:56 WAN Connection: Fail to connect with some issues.
92. Jan 24 15:42:57 pppd[488]: Connection terminated.
93. Jan 24 15:42:58 pppd[488]: Modem hangup
94. Jan 24 15:43:44 pppd[488]: Timeout waiting for PADS packets
95. Jan 24 15:43:49 pppd[488]: Connected to 00:30:88:1d:ff:dc via interface vlan100
96. Jan 24 15:43:49 pppd[488]: Connect: ppp0 <--> vlan100
97. Jan 24 15:43:49 pppd[488]: PAP authentication succeeded
98. Jan 24 15:43:49 pppd[488]: peer from calling number 00:30:88:1D:FFC authorized
99. Jan 24 15:43:49 pppd[488]: local IP address
100. Jan 24 15:43:49 pppd[488]: remote IP address
101. Jan 24 15:43:49 pppd[488]: primary DNS address
102. Jan 24 15:43:49 pppd[488]: secondary DNS address
103. Jan 24 15:43:49 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
104. Jan 24 15:43:50 wan: finish adding multi routes
105. Jan 24 15:43:50 rc_service: ip-up 20868:notify_rc stop_upnp
106. Jan 24 15:43:50 rc_service: ip-up 20868:notify_rc start_upnp
107. Jan 24 15:43:50 rc_service: waitting "stop_upnp" via ip-up ...
108. Jan 24 15:43:50 miniupnpd[19721]: shutting down MiniUPnPd
109. Jan 24 15:43:50 WAN Connection: WAN was restored.
110. Jan 24 15:43:51 ntp: start NTP update
111. Jan 24 15:43:51 miniupnpd[20900]: version 1.9 started
112. Jan 24 15:43:51 miniupnpd[20900]: HTTP listening on port 50603
113. Jan 24 15:43:51 miniupnpd[20900]: Listening for NAT-PMP/PCP traffic on port 5351
114. Jan 24 15:59:57 ntp: start NTP update
115. Jan 24 16:59:57 ntp: start NTP update
116. Jan 24 17:59:57 ntp: start NTP update
117. Jan 24 18:49:17 WAN Connection: Ethernet link down.
118. Jan 24 18:49:17 stop_nat_rules: apply the redirect_rules!
119. Jan 24 18:49:52 WAN Connection: WAN was restored.
120. Jan 24 18:49:52 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan100)!
121. Jan 24 18:59:57 ntp: start NTP update

Since I am total newbie, when it comes to the networking, I wonder, if here is anyone willing to help me. For now, I tried to reconnect old comtrend.

 

[RMerlin]

Jan 24 00:20:40 WAN Connection: Ethernet link down.

This indicates that your modem rebooted itself. Check with your ISP, it's a problem with either the modem or your connection.

 

[teeejay]

This indicates that your modem rebooted itself. Check with your ISP, it's a problem with either the modem or your connection.

I reached out to my ISP and they said, that the connection is perfectly stable. That they encountered no disconnects in provided time. But also that they cannot see, that I have been disconnected in that time. So the issue must be modem itself.

I set it up in compliance with the guide on their site.

For now I am on Comtrend for 3 hours and it works perfectly fine.

So you would RMA the Asus router?

 

[RMerlin]

I reached out to my ISP and they said, that the connection is perfectly stable. That they encountered no disconnects in provided time. But also that they cannot see, that I have been disconnected in that time. So the issue must be modem itself.

I set it up in compliance with the guide on their site.

For now I am on Comtrend for 3 hours and it works perfectly fine.

So you would RMA the Asus router?

Do you have anything connected on the router/modem's WAN port? The system log seems to indicate that there is something connected to that port, and that it's being occasionally disconnected.

 

[teeejay]

Do you have anything connected on the router/modem's WAN port? The system log seems to indicate that there is something connected to that port, and that it's being occasionally disconnected.

No, the cable from WAN port (DSL) goes directly into the wall. But the same cable works on Comtrend, so I do not see, that it could be an issue.

And in the LAN ports are 2 computers plugged in.

 

[pete y testing]

hi

the asus dsl-ac68u is a mediatek chipset and can be problematic on long lines over about 2.5km from exchange

Op can you post the dsl stats from the dsl-ac68u including attenuation snt and attainable and actual rates of speed as this will give us some idea of your distance from the exchange , i think the info is ether in the admin or log sections

No, the cable from WAN port (DSL) goes directly into the wall.

what about other devices connected to the same phone line around the house are they all filtered , this includes alarms , faxes , phones , pay tv etc etc

 

[teeejay]

hi

the asus dsl-ac68u is a mediatek chipset and can be problematic on long lines over about 2.5km from exchange

Op can you post the dsl stats from the dsl-ac68u including attenuation snt and attainable and actual rates of speed as this will give us some idea of your distance from the exchange , i think the info is ether in the admin or log sections


what about other devices connected to the same phone line around the house are they all filtered , this includes alarms , faxes , phones , pay tv etc etc

My distance is 1200 m. Down 20,5 db, up 15 db. Speed is 40/4.

There are basically no other devices connected to the line.

 

[pete y testing]

My distance is 1200 m. Down 20,5 db, up 15 db. Speed is 40/4.

so your not an adsl and rather on some form of vdsl right

Speed is 40/4.

what is your plan speed that you pay for?

 

[teeejay]

so your not an adsl and rather on some form of vdsl right


what is your plan speed that you pay for?

I am on VDSL, I get what I pay for. 40/4 is guaranteed and I have it every time. Sometimes even higher than 40.