Problems with WiFi network.

[Warak]

Hello everyone. So few days ago my router, ASUS RT-68U, started to do strange things. All seems ok, suddenly my smartphone lost WiFi internet, jumped to another WiFi device(no internet there), I tried to manually reconnect it to my router, all seems ok but as soon as I start to use WiFi for anything, lets say open LTT forum everything is happening again, internet turns off, smartphone feels it and reconnects to another device. Nothing was added or removed from the network, its just started.

I "forgot" another WiFi device, turned off mobile data, started to do some experiments and its basically a cycle. I restart router, all looks good, I start to use internet on my smartphone and few minutes latter its start to loose connection, it looks like its connected to router, but no internet, browser wont open anything, VoWiFi changes to VoLTE and so on. 5-10 minutes later everything is good again till I start to do something with internet.

 

I started to look for a problem...

1. Maybe router is overheating? Its in pretty closed space, feels little hot. I put it on a table, so its nice and cool around it, nothing changed, router is still little hot - So I guess its not overheating.

2. My router is in AP mode, connected to switch, maybe something wrong with switch? Ports there like to just suddenly die. I changed port, same problems. - Guess its not switch problem.

3. Checked firmware, updated, but it was working few days ago so doubt it was firmware problem, but fresh is suppose to be better so why not.

4. What about cable itself? I used another cable(Switch->Router), Also didnt helped.

 

I decided to go and see router logs, Iam not specialist but perhaps I will find something in there, like BIG RED ERROR MESSAGE, nope, there was lots of things there but nothing I can see except one thing

 

Spoiler

Dec 27 13:10:07 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:10:07 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:10:15 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 13:10:17 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:10:17 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:10:25 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 13:10:25 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:10:25 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:16:48 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)

This, over and over, and over again. Lots of this. It doesnt look like big red error message I wanted, but it is something.

Perhaps someone else can see something in the logs, it starts from the moment I changed cable between router and switch till right now basically.

Right this moment(13:51) everything was working, few minutes later everything is broken again...Smartphone is connected to WiFi network, but there is no internet and messages are returned. 

Spoiler

Dec 27 13:56:37 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:56:37 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:56:45 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 13:56:46 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:56:46 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:56:54 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 13:56:56 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Dec 27 13:57:00 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:57:00 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:57:09 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 13:57:10 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Dec 27 13:57:27 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:57:27 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:57:35 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 13:57:37 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:57:37 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:57:45 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 13:57:47 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:57:47 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:57:55 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 13:57:57 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:57:57 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:58:05 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 13:58:08 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:58:08 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:58:16 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 13:58:18 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:58:18 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:58:26 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 13:58:28 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:58:28 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:58:36 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 13:59:39 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:59:39 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:59:47 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 13:59:53 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 13:59:53 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:00:01 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:00:03 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Dec 27 14:00:18 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:00:18 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:00:27 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:00:27 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 27 14:00:28 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Dec 27 14:00:32 disk_monitor: Got SIGALRM...

14:03 - all works again.

 

Can it be smartphone problem?...I need to find some other device to check, but I got WiFi LED strip, its also got problems so seems like its router. btw as soon as I started to pair phone and LED strip, somehow its also broken, cycle started again, no internet and lots of messages in the log, except its 2 devices now. :67 is my phone and I guess :18 is LED strip...

Spoiler

Dec 27 14:00:32 disk_monitor: Got SIGALRM...
Dec 27 14:02:30 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:02:30 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:04:28 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:04:33 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:04:33 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:07:28 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 04:CF:8C:AC:8F:18, status: 0, reason: d11 RC reserved (0)
Dec 27 14:07:28 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 04:CF:8C:AC:8F:18, status: 0, reason: d11 RC reserved (0)
Dec 27 14:07:37 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind 04:CF:8C:AC:8F:18, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:07:42 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 04:CF:8C:AC:8F:18, status: 0, reason: d11 RC reserved (0)
Dec 27 14:07:42 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 04:CF:8C:AC:8F:18, status: 0, reason: d11 RC reserved (0)
Dec 27 14:07:42 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 04:CF:8C:AC:8F:18, status: 0, reason: d11 RC reserved (0)
Dec 27 14:09:16 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Previous authentication no longer valid (2)
Dec 27 14:09:17 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:09:17 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:09:24 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:09:25 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:09:25 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:09:33 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:09:35 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:09:35 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:09:43 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:09:45 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 27 14:09:55 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:09:55 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:03 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:10:25 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:25 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:33 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:10:41 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 04:CF:8C:AC:8F:18, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:41 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 04:CF:8C:AC:8F:18, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:41 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 04:CF:8C:AC:8F:18, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:41 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:42 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:42 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:42 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:42 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:43 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:43 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:43 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:43 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:43 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:44 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 04:CF:8C:AC:8F:18, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:45 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 04:CF:8C:AC:8F:18, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:45 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 04:CF:8C:AC:8F:18, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:45 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:45 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:45 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:45 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:10:45 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:11:19 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:11:19 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:11:27 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:11:29 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:11:29 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:11:33 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:11:38 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:11:38 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:11:46 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:11:48 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:11:48 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:11:56 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:11:58 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:11:58 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:12:06 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:12:08 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:12:08 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:12:16 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)

Can anyone help me, what happened with my router? What does he want from me? Or perhaps its just a good time to buy new router? 68U worked just fine till few days ago, but he is still pretty old already, at least 4 or 5 years.

Sorry for such long post, I think I am going insane...

Log.txt

[Warak]

Also - 14:18, everything looks fine again, just tried to open page in a browser, it works...

Spoiler

Dec 27 14:12:16 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind DC:16:B2:4D:8C:67, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 27 14:18:22 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)
Dec 27 14:18:22 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc DC:16:B2:4D:8C:67, status: 0, reason: d11 RC reserved (0)

 

[Windows7ge]

How is your network configured if your router is in AP mode? Is there another router in the home?

 

If there are no other connected clients (wired or wireless) and it's kicking everyone you try to connect you can try a factory reset to see if that helps but if not you will likely have to replace the unit.

[Warak]

1 hour ago, Windows7ge said:

How is your network configured if your router is in AP mode? Is there another router in the home?

 

If there are no other connected clients (wired or wireless) and it's kicking everyone you try to connect you can try a factory reset to see if that helps but if not you will likely have to replace the unit.

Optical cable comes to ONT, ONT is connected to switch, this switch(1) is connected to another switch(2), router is in AP mode and connected to 2nd switch. Nothing is connected to this router except smartphone, its basically wi-fi AP for smartphone and other wireless things cause I dont want to use wi-fi from ISPs ONT, I dont trust it but I have to use it cause my ISP gave me fiber, not simple twisted pair.

 

Tried factory reset, didnt helped. Tomorrow I will buy something cheap, I like SUS RT-N19 and try him. 

[Windows7ge]

10 minutes ago, Warak said:

Tried factory reset, didnt helped. Tomorrow I will buy something cheap, I like SUS RT-N19 and try him. 

Do let us know how that goes. Besides replacing the cable or connecting directly to your ISP router I can't think of another fault besides failed router(AP).

 

That or crazy amounts of network interference. Have you tried checking the wireless spectrum in your area? Is it a screaming match with your neighbors?

[Warak]

39 minutes ago, Windows7ge said:

Do let us know how that goes. Besides replacing the cable or connecting directly to your ISP router I can't think of another fault besides failed router(AP).

 

That or crazy amounts of network interference. Have you tried checking the wireless spectrum in your area? Is it a screaming match with your neighbors?

Not really, tbh I think you can call it 0 interference considering how it looks in more public places  Just few other ONTs from same ISP(MGTS_GPONs) + 2 of my "other wifi devices"(LIB20) but they dont do anything, they cant do anything plus they were always there, problems started few days ago.

 

[Windows7ge]

2 minutes ago, Warak said:

Not really, tbh I think you can call it 0 interference considering how it looks in more public places  Just few other ONTs from same ISP(MGTS_GPONs) + 2 of my "other wifi devices"(LIB20) but they dont do anything, they cant do anything plus they were always there, problems started few days ago.

Only other thing I can recommend is replacing the hardware and seeing if it makes a difference. There's a fairly limited number of software troubleshooting steps you can do with consumer routers like this when an issue starts out of nowhere. Common causes can be interference, a rouge client on the network, at least one of which you've eliminated, or failing hardware.

 

We will see if a replacement unit changes the situation. Just hold onto the receipt in case it doesn't.

[Warak]

16 hours ago, Windows7ge said:

Only other thing I can recommend is replacing the hardware and seeing if it makes a difference. There's a fairly limited number of software troubleshooting steps you can do with consumer routers like this when an issue starts out of nowhere. Common causes can be interference, a rouge client on the network, at least one of which you've eliminated, or failing hardware.

 

We will see if a replacement unit changes the situation. Just hold onto the receipt in case it doesn't.

Well...I guess I need new router  Bought RT-N19, few problems in the beginning with initial setup, not sure why but I couldnt get to GUI after I put router in AP mode, after hard reset all is ok till I put it in AP again  But few hard resets and problem solved itself  perhaps I just missed something small first times, still strange.

Anyway, so far N19 works fine, I will see how it would be after few hours, perhaps I will try my 68U again in a few days but as I said, so far it looks like I need new router. N19 is not so bad, but little too budget for me...only 2.4 WiFi, just 2 10\100 ports and so on, good as a backup though.

 

Well at least its almost NY, new router can be a gift for myself  RP-AC68U looks awesome, but I will have to put it in the open, pretty stupid to buy such device and hide it in some closet. + It can do two things at a time - AP + Night Lamp

[Windows7ge]

Using a Router instead of a AP you can expect it's IP address may either no longer be accessible or it's IP to have changed to be one from the parent router. You may find it to be no longer accessible again where in you'll have to check the main home router to see if it's address is different.

 

Of course I could be wrong. If I'm not mistaken real APs don't take an IP address. All they rely on is their Layer 2 MAC.

[Warak]

34 minutes ago, Windows7ge said:

Using a Router instead of a AP you can expect it's IP address may either no longer be accessible or it's IP to have changed to be one from the parent router. You may find it to be no longer accessible again where in you'll have to check the main home router to see if it's address is different.

 

Of course I could be wrong. If I'm not mistaken real APs don't take an IP address. All they rely on is their Layer 2 MAC.

I think you wrong cause it the end I wanted my router in AP mode with 192.168.1.1 address and I got it, I tried same settings each time...same IP, same Gateway and DNS, so its some kind of strange bug or some mistake I made, messed up one of the addresses perhaps, 129 instead of 192 or something like this.

Its not rocket science right...any free IP address + Gateway and DNS 1 = IP of the main router. Anyone can do it  I think I can even put LAN IP on auto, main router = DHCP so it will sort things out

 

Guess we will never know, its working now so its should've worked first time if I didnt made a mistake with IP\Gateway\DNS right? I will never believe that two hard resets are helped with something

[Windows7ge]

Does your main LAN operate on 192.168.0.0/24?

[Warak]

52 minutes ago, Windows7ge said:

Does your main LAN operate on 192.168.0.0/24?

Not sure I understand your question...

[Windows7ge]

2 minutes ago, Warak said:

Not sure I understand your question...

When you plug a router into another router (at least in the case of consumer products) the first router may produce a network such as 192.168.0.0/24 while the next router will use 192.168.1.0/24. And so on and so forth. It increments the network. Each time so as to avoid a address conflict.

 

Though I have heard of some brands using 192.168.68.0/24 or 192.168.100.0/24. Why? I don't know, but whatever.

 

It's not a big deal. Just a curiosity of mine. I'm thinking if you connect a device to the parent router(modem) you may not be able to access the AP WebUI. I'm not certain, I've not played with a router in AP mode.

[Warak]

12 minutes ago, Windows7ge said:

When you plug a router into another router (at least in the case of consumer products) the first router may produce a network such as 192.168.0.0/24 while the next router will use 192.168.1.0/24. And so on and so forth. It increments the network. Each time so as to avoid a address conflict.

 

Though I have heard of some brands using 192.168.68.0/24 or 192.168.100.0/24. Why? I don't know, but whatever.

 

It's not a big deal. Just a curiosity of mine. I'm thinking if you connect a device to the parent router(modem) you may not be able to access the AP WebUI. I'm not certain, I've not played with a router in AP mode.

No idea

 

Closest things I could find to what I think u talking about is this. Its from my main router, I never really touched it, I got no idea what this thing is and what it can do, it even got custom UI from my ISP, iam simply afraid to touch anything there  

 

Well not anything, anything I dont 100% understand. + there is an old saying "dont touch BIOS if everything is working"...Heard it like 20 or so years ago from a smart dude, first thing he told me when I got my first PC  I dont even want to know how many times this saying saved me from doing something stupid  Ofc updating BIOS today it not the same as it was 20 years ago but still...

 

Too bad my IPS cant just allow me to use my own equipment, I would love to do everything from the ground up...My own routers, SFP for fiber cable and so on...but I have to use IPSs ONT...

[Windows7ge]

2 hours ago, Warak said:

Well not anything, anything I dont 100% understand. + there is an old saying "dont touch BIOS if everything is working"...Heard it like 20 or so years ago from a smart dude, first thing he told me when I got my first PC  I dont even want to know how many times this saying saved me from doing something stupid  Ofc updating BIOS today it not the same as it was 20 years ago but still...

20 or so years later things have not significantly changed. There's only so many settings you're advised to touch and updating your BIOS can still turn your motherboard into a paperweight if something goes wrong.

 

2 hours ago, Warak said:

Too bad my IPS cant just allow me to use my own equipment, I would love to do everything from the ground up...My own routers, SFP for fiber cable and so on...but I have to use IPSs ONT...

I would say most ISP's do allow the usage of 3rd party modems you'd just need one that is compatible with your type of fiber cable, and that falls under their supported modem list. From there you could connect any router you want. (It'd be two separate boxes).

 

Based on your pictures it seems your DHCP pool is set to ignore the first 63 addresses and it uses the 192.168.1.0/24 network. It means you should be able to connect to your router(AP)'s WebUI from anywhere in your home on any computer and the fact it has taken 192.168.1.1 should not interfere with any other devices on the network.

 

In layman's terms, everything SHOULD work as you've intended for it to.

[Warak]

16 minutes ago, Windows7ge said:

I would say most ISP's do allow the usage of 3rd party modems you'd just need one that is compatible with your type of fiber cable, and that falls under their supported modem list. From there you could connect any router you want. (It'd be two separate boxes).

I researched this option. You need to find specific SFP from D-Link, SFP which is discontinued few years ago I think, u need to use custom firmware, it would run very hot(65C-70C) so you will need good cooling and even after all this you will only get Internet(np phone or cable tv, dont care about both but still) and most likely it will be pretty unstable.

Not worth it unfortunately, in the end the only people who are doing all of this are enthusiasts and most of them do not recommend it for everyday use, for them its a hobby.

 

 

[Alex Atkin UK]

11 hours ago, Windows7ge said:

Using a Router instead of a AP you can expect it's IP address may either no longer be accessible or it's IP to have changed to be one from the parent router. You may find it to be no longer accessible again where in you'll have to check the main home router to see if it's address is different.

 

Of course I could be wrong. If I'm not mistaken real APs don't take an IP address. All they rely on is their Layer 2 MAC.

Real APs are indeed the same, they will pull an IP over DHCP or want you to connect to it and configure a static IP, but as they are intended to work like that they likely have better documentation to warn you of how it works and/or smartphone apps to automatically detect it on the LAN no matter what its IP is.

[Windows7ge]

1 hour ago, Alex Atkin UK said:

Real APs are indeed the same, they will pull an IP over DHCP or want you to connect to it and configure a static IP, but as they are intended to work like that they likely have better documentation to warn you of how it works and/or smartphone apps to automatically detect it on the LAN no matter what its IP is.

That's a lot of wasted addresses then in commercial installations, but I guess that's why subnets </24 exist.

[Alex Atkin UK]

1 minute ago, Windows7ge said:

That's a lot of wasted addresses then in commercial installations, but I guess that's why subnets </24 exist.

Its more important in commercial though as they will be centrally managed.

There's also the fact management and normal traffic are likely on different VLANs.

[Windows7ge]

2 minutes ago, Alex Atkin UK said:

Its more important in commercial though as they will be centrally managed.

There's also the fact management and normal traffic are likely on different VLANs.

I'd love to get my hands on some of that technology and understand how they work and are implemented. I know switch ports can belong to more than one VLAN but I've not thought about the AP being able to use or exist on more than 1 VLAN at a time. The Management VLAN then the Clients VLAN.

 

I'll have to find a good brand and buy one or two and plug them into my managed switch. Have a go at em. I've been looking at the brands the business I visit install but I've not seriously researched the features of them yet.

[Alex Atkin UK]

23 minutes ago, Windows7ge said:

I'd love to get my hands on some of that technology and understand how they work and are implemented. I know switch ports can belong to more than one VLAN but I've not thought about the AP being able to use or exist on more than 1 VLAN at a time. The Management VLAN then the Clients VLAN.

 

I'll have to find a good brand and buy one or two and plug them into my managed switch. Have a go at em. I've been looking at the brands the business I visit install but I've not seriously researched the features of them yet.

I haven't gotten my head around VLANs yet.  I tried to split my bridged modems traffic over VLANs so I only had one cable for both WAN and management, but ultimately I could only get it working by just running two cables from each.

 

It doesn't help that being consumer routers, they word everything differently so I "thought" it was VLAN tagging, but can't be sure.  Plus I found conflicting information on if VLAN tags reduce your MTU or not.

Sometimes its just more important to get it working and as I daisy-chain between the modems, they just count as extra network switches on the LAN, not really a loss.

[Alex Atkin UK]

accidental double-post

[Windows7ge]

4 minutes ago, Alex Atkin UK said:

I haven't gotten my head around VLANs yet.  I tried to split my bridged modems traffic over VLANs so I only had one cable for both WAN and manamagement, but ultimately I could only get it working by just running two cables from each.

 

It doesn't help that being consumer routers, they word everything differently so I "thought" it was VLAN tagging, but can't be sure.  Plus I found conflicting information on if VLAN tags reduce your MTU or not.

I'd have to have your modem to even begin to know if that's a possibility. The modem/router needs to know what to tag and if it doesn't give you an easy option to do that or to create sub-interfaces on the physical port as to create a managed network then it may not be a possibility at all. Depending on how you have all this configured though you could run both modems management ports into a switch then run one cable to another switch or computer to act as the management network.

 

Based on what I know a portion of the IP header is already dedicated to VLAN tagging. If VLAN tagging is enabled all it should do is occupy that slot in the header. The MTU should not shrink. Even if it did you could always bump up the payload. Enable Jumbo Frames on the switch.

[Alex Atkin UK]

3 minutes ago, Windows7ge said:

I'd have to have your modem to even begin to know if that's a possibility. The modem/router needs to know what to tag and if it doesn't give you an easy option to do that or to create sub-interfaces on the physical port as to create a managed network then it may not be a possibility at all. Depending on how you have all this configured though you could run both modems management ports into a switch then run one cable to another switch or computer to act as the management network.

 

Based on what I know a portion of the IP header is already dedicated to VLAN tagging. If VLAN tagging is enabled all it should do is occupy that slot in the header. The MTU should not shrink. Even if it did you could always bump up the payload. Enable Jumbo Frames on the switch.

They basically are connected to each other and as its a home network, doesn't really need to be a private management LAN.

Its kinda useful being able to still login to them from my laptop anyway, plus you gain all the spare ports on those modems (routers) as extra switch ports on the LAN, so in the end it was no loss.

[Windows7ge]

5 minutes ago, Alex Atkin UK said:

They basically are connected to each other and as its a home network, doesn't really need to be a private management LAN.

Its kinda useful being able to still login to them from my laptop anyway, plus you gain all the spare ports on those modems (routers) as extra switch ports on the LAN, so in the end it was no loss.

Same reason the IPMI on all my servers are connected to the LAN. Internal security isn't a super concern and the convince factor is worth the trade-off when I need to edit BIOS configurations or install something new.

 

We need a new switch. I've filled a 24 port.