What's new

dsl-ac68u keeps crashing

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

tuxki

New Around Here
Hello

Every Day my connection crashes and I don't know how to fix it. I assume, it's because of the "status: 0, reason: Class xx frame received from nonauthenticated station (6)" error leading to:

pppd[386]: Serial link appears to be disconnected.
WAN Connection: Fail to connect with some issues.
nat: apply redirect rules
pppd[386]: Connection terminated.
pppd[386]: Modem hangup

What does it mean and how can I fix it?

Info:
DSL-AC68U
DSL Firmware Version 1.0.4.9
DSL Driver Version FwVer:5.5.2.11_B_A60901 HwVer:T14.F7_0.2

AiMesh router
Current Version : 3.0.0.4.384_81981-g632ffdf

Code:
Jan 21 18:08:33 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 1 ###, status: Successful (0)
Jan 21 18:08:33 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 1 ###, status: Successful (0)
Jan 21 19:53:21 syslog: wlceventd_proc_event(459): eth2: Deauth_ind ### Client 2 ###, status: 0, reason: Disassociated due to inactivity (4)
Jan 21 21:53:38 syslog: wlceventd_proc_event(476): eth1: Disassoc ### Client 3 ###, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 21 21:53:38 syslog: wlceventd_proc_event(459): eth1: Deauth_ind ### Client 3 ###, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Jan 21 22:13:42 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 3 ###, status: Successful (0)
Jan 21 22:13:42 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 3 ###, status: Successful (0)
Jan 21 23:53:33 syslog: wlceventd_proc_event(476): eth1: Disassoc ### Client 3 ###, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 22 00:13:41 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 3 ###, status: Successful (0)
Jan 22 00:13:41 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 3 ###, status: Successful (0)
Jan 22 01:53:32 syslog: wlceventd_proc_event(476): eth1: Disassoc ### Client 3 ###, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 22 01:53:32 syslog: wlceventd_proc_event(459): eth1: Deauth_ind ### Client 3 ###, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Jan 22 02:13:39 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 3 ###, status: Successful (0)
Jan 22 02:13:39 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 3 ###, status: Successful (0)
Jan 22 04:54:02 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 4 ###, status: Successful (0)
Jan 22 04:54:02 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 4 ###, status: Successful (0)
Jan 22 04:54:33 syslog: wlceventd_proc_event(476): eth1: Disassoc ### Client 4 ###, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 22 05:53:23 syslog: wlceventd_proc_event(476): eth1: Disassoc ### Client 3 ###, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 22 06:13:30 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 3 ###, status: Successful (0)
Jan 22 06:13:30 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 3 ###, status: Successful (0)
Jan 22 08:21:37 syslog: wlceventd_proc_event(459): eth1: Deauth_ind ### Client 5 ###, status: 0, reason: Disassociated due to inactivity (4)
Jan 22 08:39:45 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 5 ###, status: Successful (0)
Jan 22 08:39:45 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 5 ###, status: Successful (0)
Jan 22 08:53:18 syslog: wlceventd_proc_event(476): eth1: Disassoc ### Client 3 ###, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 22 09:13:25 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 3 ###, status: Successful (0)
Jan 22 09:13:25 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 3 ###, status: Successful (0)
Jan 22 09:43:17 syslog: wlceventd_proc_event(476): eth1: Disassoc ### Client 3 ###, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 22 11:31:38 syslog: wlceventd_proc_event(459): eth1: Deauth_ind ### Client 1 ###, status: 0, reason: Disassociated due to inactivity (4)
Jan 22 13:05:14 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 1 ###, status: Successful (0)
Jan 22 13:05:14 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 1 ###, status: Successful (0)
Jan 22 13:06:11 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 3 ###, status: Successful (0)
Jan 22 13:06:11 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 3 ###, status: Successful (0)
Jan 22 13:09:37 syslog: wlceventd_proc_event(459): eth1: Deauth_ind ### Client 1 ###, status: 0, reason: Disassociated due to inactivity (4)
Jan 22 13:31:22 syslog: wlceventd_proc_event(459): eth1: Deauth_ind ### Client 5 ###, status: 0, reason: Disassociated due to inactivity (4)
Jan 22 14:09:59 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 5 ###, status: Successful (0)
Jan 22 14:09:59 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 5 ###, status: Successful (0)
Jan 22 14:46:55 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 1 ###, status: Successful (0)
Jan 22 14:46:55 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 1 ###, status: Successful (0)
Jan 22 15:53:08 syslog: wlceventd_proc_event(476): eth1: Disassoc ### Client 3 ###, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 22 16:00:51 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 4 ###, status: Successful (0)
Jan 22 16:00:52 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 4 ###, status: Successful (0)
Jan 22 16:18:37 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 3 ###, status: Successful (0)
Jan 22 16:18:37 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 3 ###, status: Successful (0)
Jan 22 16:21:37 syslog: wlceventd_proc_event(495): eth2: Auth ### Client 2 ###, status: Successful (0)
Jan 22 16:21:37 syslog: wlceventd_proc_event(524): eth2: Assoc ### Client 2 ###, status: Successful (0)
Jan 22 16:53:00 syslog: wlceventd_proc_event(476): eth1: Disassoc ### Client 3 ###, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 22 17:13:04 syslog: wlceventd_proc_event(495): eth1: Auth ### Client 3 ###, status: Successful (0)
Jan 22 17:13:04 syslog: wlceventd_proc_event(524): eth1: Assoc ### Client 3 ###, status: Successful (0)
Jan 22 18:00:46 syslog: wlceventd_proc_event(476): eth2: Disassoc ### Client 2 ###, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 22 18:00:46 syslog: wlceventd_proc_event(459): eth2: Deauth_ind ### Client 2 ###, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 22 18:00:48 syslog: wlceventd_proc_event(495): eth2: Auth ### Client 2 ###, status: Successful (0)
Jan 22 18:00:48 syslog: wlceventd_proc_event(524): eth2: Assoc ### Client 2 ###, status: Successful (0)
Jan 22 18:00:55 pppd[386]: Serial link appears to be disconnected.
Jan 22 18:01:00 WAN Connection: Fail to connect with some issues.
Jan 22 18:01:01 nat: apply redirect rules
Jan 22 18:01:01 pppd[386]: Connection terminated.
Jan 22 18:01:01 pppd[386]: Modem hangup
Jan 22 18:01:07 syslog: wlceventd_proc_event(495): eth2: Auth ### Client 2 ###, status: Successful (0)
Jan 22 18:01:07 syslog: wlceventd_proc_event(524): eth2: Assoc ### Client 2 ###, status: Successful (0)
Jan 22 18:01:08 syslog: wlceventd_proc_event(476): eth2: Disassoc ### Client 2 ###, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 22 18:01:08 syslog: wlceventd_proc_event(459): eth2: Deauth_ind ### Client 2 ###, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 22 18:01:08 syslog: wlceventd_proc_event(459): eth2: Deauth_ind ### Client 2 ###, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 22 18:01:08 syslog: wlceventd_proc_event(495): eth2: Auth ### Client 2 ###, status: Successful (0)
Jan 22 18:01:08 syslog: wlceventd_proc_event(524): eth2: Assoc ### Client 2 ###, status: Successful (0)

Jan 22 18:01:12 pppd[386]: Connected to ########## via interface vlan3880
Jan 22 18:01:12 pppd[386]: Connect: ppp0 <--> vlan3880
Jan 22 18:01:12 pppd[386]: CHAP authentication succeeded
Jan 22 18:01:12 pppd[386]: peer from calling number ########## authorized
Jan 22 18:01:12 pppd[386]: local  IP address ##########
Jan 22 18:01:12 pppd[386]: remote IP address ##########
Jan 22 18:01:12 pppd[386]: primary   DNS address ##########
Jan 22 18:01:12 pppd[386]: secondary DNS address ##########1
Jan 22 18:01:12 nat: apply nat rules (/tmp/nat_rules_ppp0_vlan3880)
Jan 22 18:01:13 wan: finish adding multi routes
Jan 22 18:01:13 miniupnpd[18359]: shutting down MiniUPnPd
Jan 22 18:01:13 miniupnpd[2597]: version 1.9 started
Jan 22 18:01:13 miniupnpd[2597]: HTTP listening on port 38645
Jan 22 18:01:13 miniupnpd[2597]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 22 18:01:15 WAN Connection: WAN was restored.

best regards
tuxki

perkeleeeeee
 
How many times a day does this happen?

Does the connection come back up by itself or do you have to enable it manually?
 
Hi Colin

Usually it happens once, sometimes twice a day. The connection establish itself "WAN Connection: WAN was restored".
 
If it only happens at approximately the same times each day then I suspect there is nothing wrong. It sounds like your ISP is only giving you a connection for 12 or 24 hours after which you have to reconnect (which the router does by itself automatically).

I would only suspect a problem if it were happening at random time intervals.
 
Dammit, I forgot about it. Indeed, my ISP refreshes my IP every 24h. IP refresh time (usually at 3am) just changed because I switched devices. I might fix this quite easily on my own. Worst case I have to call my ISP to change the ip assignment time.

Thank you Colin

best regards
tuxki
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top