Strange wifi disturbance

[Gravityz]

Ever since i had ew firmware in my RT-AC86U i experienced a lot of wifi dropouts
i switched back to earlier firmware and the problem seems gone
since that day i am monitoring a couple of devices to see if connectivity gets broken.

today i experienced something weird
for half an hour (16:00-16:32) a lot of devices were disconnecting and connecting all the time.

this is what i see in the log.
it looks like one device is killing the network or may tries to connect/disconnect so much that others are not able to.

can somebody see what is happening?
setup is rt-AX88U with RT-AC86U in an AIMESH with 1 SSID for everything and roaming assistant on(smart connect off)

the device with the most entries is only 2 meters away from the main router so signal strength/quality can not be the problem

D0:C1:93:04:E6:1F

16:00:04 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind 5C:80:B6:A0:CB4, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:06:22 wlceventd: wlceventd_proc_event(530): eth7: Auth 5C:80:B6:A0:CB4, status: Successful (0), rssi:0
May 8 16:06:22 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc 5C:80:B6:A0:CB4, status: Successful (0), rssi:-72
May 8 16:16:52 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-38
May 8 16:16:52 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-38
May 8 16:16:53 wlceventd: wlceventd_proc_event(511): eth6: Disassoc D0:C1:93:04:E6:1F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 8 16:16:55 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:16:55 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:16:55 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:16:55 wlceventd: wlceventd_proc_event(559): eth6: Assoc D0:C1:93:04:E6:1F, status: Successful (0), rssi:-37
May 8 16:17:36 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:17:36 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:17:36 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:17:36 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:17:36 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:17:36 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:17:39 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:17:39 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:17:39 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:17:39 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:17:39 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:17:39 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:17:44 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:17:44 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:17:44 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:17:44 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:17:44 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:17:44 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:17:44 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:17:44 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:18:12 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:18:12 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:18:12 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:18:12 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:18:12 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:18:12 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:18:14 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:18:14 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:18:14 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:18:14 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:18:14 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:18:14 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:18:16 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:18:16 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:18:16 wlceventd: wlceventd_proc_event(559): eth6: Assoc D0:C1:93:04:E6:1F, status: Successful (0), rssi:-37
May 8 16:25:43 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-37
May 8 16:25:43 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-37
May 8 16:25:44 wlceventd: wlceventd_proc_event(511): eth6: Disassoc D0:C1:93:04:E6:1F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 8 16:25:50 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:25:50 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:25:50 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:25:50 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:25:50 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:25:58 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:25:58 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:25:59 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:25:59 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:25:59 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:25:59 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0
May 8 16:26:09 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind D0:C1:93:04:E6:1F, status: 0, reason: Unspecified reason (1), rssi:0
May 8 16:26:09 wlceventd: wlceventd_proc_event(530): eth6: Auth D0:C1:93:04:E6:1F, status: Successful (0), rssi:0

 

[ColinTaylor]

for half an hour (16:00-16:32) a lot of devices were disconnecting and connecting all the time.

Ignoring the single reassociation on 5GHz all the other messages are from one device, a Wi-Fi doorbell. If you were having internet connectivity problems check your ISP connection.

 

[Gravityz]

thanks Colin,
i do not see anything in the log which points to internet connectivity problems, only this

15:55:13 rc_service: amas_lib 1253:notify_rc restart_firewall

the device imentioned is indeed a wifi doorbell(how the xxxx could you tell Colin)
maybe it has problems with it's cloud connectivity
if this is the case than this device seems capable of disrupting the complete wifi network

 

[ColinTaylor]

thanks Colin,
i do not see anything in the log which points to internet connectivity problems, only this
15:55:13 rc_service: amas_lib 1253:notify_rc restart_firewall

Try and work out why the firewall restarted. That usually indicates a WAN issue.

the device imentioned is indeed a wifi doorbell(how the xxxx could you tell Colin)
maybe it has problems with it's cloud connectivity
if this is the case than this device seems capable of disrupting the complete wifi network

It's a common trait of mobile/IoT devices that if they can't reach the internet they will keep disconnecting/reconnecting in an attempt to re-establish the connection. There is no other information in the log that would suggest a problem with other devices (maybe look at the node's syslog for those devices).

 

[Gravityz]

ok but does this also explain why other wifi devices also disconnected and connected at the same time. i understand that one device keeps on trying but should it not be that such a device can not affect others otherwise it is like a domino effect and all devices keep on trying again and again disrupting the network. disconnect/reconnect should not use a lot of bandwidth

 

[ColinTaylor]

ok but does this also explain why other wifi devices also disconnected and connected at the same time.

I have no idea. The log entries you posted do not show any other Wi-Fi devices disconnecting or reconnecting to that router.

 

[Gravityz]

you are correct, i also do not see other devices in the log but i monitored a couple of devices through a regular ping and i see that those devices are sometimes not reachable during the time that doorbell is trying to reconnect.
so the doorbell is the cullprit, now i must figur out how i can isolate it from the rest. private guest network will probably not work because it disturbs the complete network

 

[ColinTaylor]

so the doorbell is the cullprit,

So far you haven't proven this is the culpret. All you know is that this doorbell and some other devices have issues at the same time. That's why I said it could be an internet issue. If you have a cable modem check it's logs for outages. It could possibly be related to AiMesh which is why I suggested you look the the node's syslog.

 

[Gravityz]

ok i will. checked the modem and it seems something happened there so it could indeed be a wan outage. for now i will keep my eye on it.
thanks for the help

 

[Gravityz]

ok.
today it happened again when i came home from work.
the device in question is my Iphone XS(F0:99:B6:48:C7:40)
nothing spectacular, is was only 12 minutes but with multiple wifi devices
I checked the modem and it did not have problems

it looks like sometimes ad evice(wifi doorbell and now iphone) has problems connecting/disconnecting which affects the complete network
i am starting to think this is indeed an aimesh problem.
when upgrading to the latest fw on my rt-AC86U the problems get really worse.
so with the older firmware the problem is also there but at a much lower scale

maybe roaming assistant has something to do with it
2.4ghz is at -79dbm, 5ghz is at -68dbm
this way signals are being switched nicely when i walk from ground floor(Rt-AX88U) to second floor(RT-AC86U)

May 11 17:58:38 wlceventd: wlceventd_proc_event(530): eth6: Auth F0:99:B6:48:C7:40, status: Successful (0), rssi:0
May 11 17:58:38 wlceventd: wlceventd_proc_event(559): eth6: Assoc F0:99:B6:48:C7:40, status: Successful (0), rssi:-74
May 11 17:58:44 roamast: [EXAP]Deauth old sta in 0 0: F0:99:B6:48:C7:40
May 11 17:58:44 roamast: eth6: disconnect weak signal strength station [f0:99:b6:48:c7:40]
May 11 17:58:44 roamast: eth6: remove client [f0:99:b6:48:c7:40] from monitor list
May 11 17:58:49 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-68
May 11 17:58:49 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-68
May 11 17:58:49 wlceventd: wlceventd_proc_event(530): eth7: Auth F0:99:B6:48:C7:40, status: Successful (0), rssi:-78
May 11 17:58:49 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-68
May 11 17:58:49 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc F0:99:B6:48:C7:40, status: Successful (0), rssi:-78
May 11 17:58:50 wlceventd: wlceventd_proc_event(511): eth6: Disassoc F0:99:B6:48:C7:40, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 11 18:05:59 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind 28:ED:E0:70:54:5D, status: 0, reason: Unspecified reason (1), rssi:0
May 11 18:05:59 wlceventd: wlceventd_proc_event(530): eth6: Auth 28:ED:E0:70:54:5D, status: Successful (0), rssi:0
May 11 18:05:59 wlceventd: wlceventd_proc_event(559): eth6: Assoc 28:ED:E0:70:54:5D, status: Successful (0), rssi:-39
May 11 18:09:28 roamast: [EXAP]Deauth old sta in 1 0: F0:99:B6:48:C7:40
May 11 18:09:28 roamast: eth7: disconnect weak signal strength station [f0:99:b6:48:c7:40]
May 11 18:09:28 roamast: eth7: remove client [f0:99:b6:48:c7:40] from monitor list
May 11 18:09:35 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-60
May 11 18:09:35 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-60
May 11 18:09:35 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-60
May 11 18:09:36 wlceventd: wlceventd_proc_event(511): eth7: Disassoc F0:99:B6:48:C7:40, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 11 18:09:39 wlceventd: wlceventd_proc_event(530): eth7: Auth F0:99:B6:48:C7:40, status: Successful (0), rssi:0
May 11 18:09:39 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc F0:99:B6:48:C7:40, status: Successful (0), rssi:-74
May 11 18:09:50 roamast: [EXAP]Deauth old sta in 1 0: F0:99:B6:48:C7:40
May 11 18:09:50 roamast: eth7: disconnect weak signal strength station [f0:99:b6:48:c7:40]
May 11 18:09:50 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-88
May 11 18:09:50 roamast: eth7: remove client [f0:99:b6:48:c7:40] from monitor list
May 11 18:09:50 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Previous authentication no longer valid (2), rssi:-88
May 11 18:09:51 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:0
May 11 18:09:51 wlceventd: wlceventd_proc_event(511): eth7: Disassoc F0:99:B6:48:C7:40, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 11 18:10:36 wlceventd: wlceventd_proc_event(530): eth7: Auth F0:99:B6:48:C7:40, status: Successful (0), rssi:0
May 11 18:10:36 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc F0:99:B6:48:C7:40, status: Successful (0), rssi:-82
May 11 18:10:59 roamast: [EXAP]Deauth old sta in 1 0: F0:99:B6:48:C7:40
May 11 18:10:59 roamast: eth7: disconnect weak signal strength station [f0:99:b6:48:c7:40]
May 11 18:11:00 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-89
May 11 18:11:00 roamast: eth7: remove client [f0:99:b6:48:c7:40] from monitor list
May 11 18:11:01 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Previous authentication no longer valid (2), rssi:-89
May 11 18:11:01 wlceventd: wlceventd_proc_event(530): eth7: Auth F0:99:B6:48:C7:40, status: Successful (0), rssi:0
May 11 18:11:01 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc F0:99:B6:48:C7:40, status: Successful (0), rssi:-89
May 11 18:11:06 roamast: [EXAP]Deauth old sta in 1 0: F0:99:B6:48:C7:40
May 11 18:11:06 roamast: eth7: disconnect weak signal strength station [f0:99:b6:48:c7:40]
May 11 18:11:06 roamast: eth7: remove client [f0:99:b6:48:c7:40] from monitor list
May 11 18:11:06 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-88
May 11 18:11:06 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-88
May 11 18:11:06 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-88
May 11 18:11:10 wlceventd: wlceventd_proc_event(511): eth7: Disassoc F0:99:B6:48:C7:40, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 11 18:11:14 wlceventd: wlceventd_proc_event(530): eth7: Auth F0:99:B6:48:C7:40, status: Successful (0), rssi:0
May 11 18:11:14 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc F0:99:B6:48:C7:40, status: Successful (0), rssi:-80
May 11 18:11:51 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-82
May 11 18:11:51 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-82
May 11 18:11:52 wlceventd: wlceventd_proc_event(511): eth7: Disassoc F0:99:B6:48:C7:40, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 11 18:15:03 wlceventd: wlceventd_proc_event(530): eth7: Auth F0:99:B6:48:C7:40, status: Successful (0), rssi:0
May 11 18:15:03 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc F0:99:B6:48:C7:40, status: Successful (0), rssi:-82
May 11 18:15:08 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind F0:99:B6:48:C7:40, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:0
May 11 18:15:08 wlceventd: wlceventd_proc_event(511): eth7: Disassoc F0:99:B6:48:C7:40, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 11 18:15:38 wlceventd: wlceventd_proc_event(530): eth7: Auth F0:99:B6:48:C7:40, status: Successful (0), rssi:0
May 11 18:15:38 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc F0:99:B6:48:C7:40, status: Successful (

 

[Gravityz]

ok. this time i noticed something which happened right before a disturbance in the wifi(multiple connects/disconnects
i looked up the ip address and it seems a hack attack

May 18 16:10:15 vpnserver1[25271]: TCP connection established with [AF_INET6]::ffff:45.227.254.48:65251
May 18 16:11:15 vpnserver1[25271]: 45.227.254.48:65251 [UNDEF] Inactivity timeout (--ping-restart), restarting
May 18 16:11:15 vpnserver1[25271]: 45.227.254.48:65251 SIGUSR1[soft,ping-restart] received, client-instance restarting

 

[ColinTaylor]

That's normal port scanning/hacking attempts. You should expect to see these messages when you allow access to your VPN server from the internet, especially if you're running it on one on the standard ports. There's no reason to think it's associated with your problem.