wlan sending station leaving
data unknown device sent deauth
UNICAST KEY EXCHANGE TIMEOUT
Can you clarify what exactly you make setup power on wireless card?After I lowered the output power of the wireless card to 15 (default 17) - this problem wasn't appeared.
This appears to have fixed my problem. In our office there is a ton of other WiFi signals on every sub channel. Maybe that is what is causing the connection to be very unstable.force the channel; ie dont set the channel on the ap to auto
The problem actually wasn't solved for long and reappeared next day. I tried some more settings, including disabling security and lowering the tx power, but the problem persists. I think my smartphone itself is suspect. I truly hope this problem won't appear at a customer...I forced it onto channel 4 which is the best one here. If the problem appears again I will tell you guys here. Thank you!
Same problem, same solving. McAfee blocked my Wifi.problem solved.
The android mobilphone used McAfee
And the APP blocked the mac-adress of the WLAN, because i placed it for unsafe.
//...
20:54:32 caps,info 48:51:B7:C4:53:42@cap31 connected
20:54:32 caps,info 48:51:B7:C4:53:42@cap32 disconnected, registered to other interface
20:55:39 caps,info 48:51:B7:C4:53:42@cap31 disconnected, received deauth: unspecified (1)
20:55:47 caps,info 48:51:B7:C4:53:42@cap31 connected
20:55:49 caps,info 48:51:B7:C4:53:42@cap31 reassociating
20:55:49 caps,info 48:51:B7:C4:53:42@cap31 connected
20:55:49 caps,info 48:51:B7:C4:53:42@cap31 disconnected, received deauth: unspecified (1)
20:55:50 caps,info 48:51:B7:C4:53:42@cap31 connected
20:57:05 caps,info 44:74:6C:B2:B3:A6@cap32 connected
20:57:06 dhcp,info dhcp1 assigned 192.168.88.162 to 44:74:6C:B2:B3:A6
20:58:25 caps,info 48:51:B7:C4:53:42@cap31 disconnected, group key timeout
20:58:29 caps,info 48:51:B7:C4:53:42@cap32 connected
21:01:00 caps,info 80:57:19:E8:0B:38@cap31 disconnected, received disassoc: sending station leaving (8)
21:01:05 caps,info 80:57:19:E8:0B:38@cap31 connected
21:01:35 caps,info 48:51:B7:C4:53:42@cap31 connected
21:01:35 caps,info 48:51:B7:C4:53:42@cap32 disconnected, registered to other interface
21:02:35 caps,info 48:51:B7:C4:53:42@cap31 disconnected, received deauth: unspecified (1)
//...
Throw it into my trash bin ... I don't have any apple gadget nearby ...i'm going to throw a microtik hap ac2 into the trash
Nothing to do with Apple. It does it with my iot gear too. I have about 10 esp8266 devices that can't connect.Throw it into my trash bin ... I don't have any apple gadget nearby ...i'm going to throw a microtik hap ac2 into the trash
When did you get this anwser?
This time...
"We were able to reproduce the problem. (Blah blah blah). We don't currently have a Fix."
June 10th.When did you get this anwser?
This time...
"We were able to reproduce the problem. (Blah blah blah). We don't currently have a Fix."
*) wireless - fixed frequency duplication in the frequency selection menu;
*) wireless - fixed incorrect IP header for RADIUS accounting packet;
*) wireless - improved 160MHz channel width stability on rb4011;
*) wireless - improved DFS radar detection when using non-ETSI regulated country;
*) wireless - improved installation mode selection for wireless outdoor equipment;
*) wireless - set default SSID and supplicant-identity the same as router's identity;
*) wireless - updated "china" regulatory domain information;
*) wireless - updated "new zealand" regulatory domain information;
So you only see this problem after a week?I have the same similar issue “disconnected, received disassoc: sending station leaving”. I have not found a fix for this problem but I think I have a workaround that has solved this issue. Wrote a script and add it to the scheduler as shown below:
/system scheduler
add interval=1w name=Recycle-Caps-Interfaces on-event=":log info \"Disable caps-man\";\r\
\n/caps-man manager set enabled=no\r\
\n:delay 10s\r\
\n:log info \"Enable caps-man\";\r\
\n/caps-man manager set enabled=yes\r\
\n" policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon start-date=sep/18/2019 start-time=02:00:00
This runs once a week at 2:00 AM in the morning and so far it has worked for me. Yes, I am aware that mobile clients disconnect when they go onto sleep mode to save battery life.
Because it runs on a weekly basis is hard to say. All I know is that I don’t see it anymore due to the weekly runs. Maybe if I run it once a month I could find out, but I haven’t and see no need to do so.So you only see this problem after a week?I have the same similar issue “disconnected, received disassoc: sending station leaving”. I have not found a fix for this problem but I think I have a workaround that has solved this issue. Wrote a script and add it to the scheduler as shown below:
/system scheduler
add interval=1w name=Recycle-Caps-Interfaces on-event=":log info \"Disable caps-man\";\r\
\n/caps-man manager set enabled=no\r\
\n:delay 10s\r\
\n:log info \"Enable caps-man\";\r\
\n/caps-man manager set enabled=yes\r\
\n" policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon start-date=sep/18/2019 start-time=02:00:00
This runs once a week at 2:00 AM in the morning and so far it has worked for me. Yes, I am aware that mobile clients disconnect when they go onto sleep mode to save battery life.
Don't know if it can help but i have same trouble and i just change name of SSID on virtual wifi (i have trouble "station leaving" only on virtual wifi) with a short name without special chararcter and for moment it's ok.I see this problem the same day I configure the router.
Now on some jobs the problem pops up a few days after I have left. Those ones... disabling the radio interface sometimes cures it. But the jobs where I see those messages right away... I have to change manufactures. Too many lost hours and clients.
I see this problem the same day I configure the router.
Now on some jobs the problem pops up a few days after I have left. Those ones... disabling the radio interface sometimes cures it. But the jobs where I see those messages right away... I have to change manufactures. Too many lost hours and clients.
You could disable the wireless on the Tik and use an external AP, then you have all the great features of RouterOS with wireless that doesn't give you issues.I prefer a plastic toy (Asus, etc ....) as a "professional" MKT device that will not hold the connection.
[admin@MikroTik] > /interface wireless print
Flags: X - disabled, R - running
0 R name="wlan1" mtu=1500 l2mtu=1600 mac-address=74:4D:28:6D:4E:1D arp=enabled
interface-type=IPQ4019 mode=ap-bridge ssid="Don't look at me"
frequency=auto band=2ghz-b/g/n channel-width=20/40mhz-XX
secondary-channel="" scan-list=default wireless-protocol=802.11
vlan-mode=no-tag vlan-id=1 wds-mode=disabled wds-default-bridge=none
wds-ignore-ssid=no bridge-mode=enabled default-authentication=yes
default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0
hide-ssid=no security-profile=default compression=no
So as You had problems, then You actually lied in Your other post - viewtopic.php?f=7&t=160943#p792785I had this too... looked very weird .... could not believe it because it worked before without a glitch..... viewtopic.php?f=7&t=160376
I was not clear on "check your DHCP leases". It's not about the duration of the lease. It's about the fact that the DHCP lease gets to the state "offered" , a point where it is usable for the receiver, but never makes it to the state "bound". After a short period of time a DHCP lease that stays in "offered" gets dropped. The client looses, or is revoked, it's leased IP address, and as a reaction disconnects.Solution was to fix the bridge port setting with "learn=auto".
Check your bridge port setting, and check your DHCP leases.
learn=auto, dhcp leases 1d 00:00:00 . . .
iPhone dissacoc . . . :-(
sep/15 20:49:13 wireless,info 28:ED:6A:AA:...@wlan1: disconnected, received disassoc: sending station leaving (8)
Yes! You're right! It's not a "whireless" problem.There might be other checks. Those "internet" checks done by station devices (testing for reachability of "some" public server), also make the station device start trying other stored SSID's in its list, if the "internet check" test fails. Even if the current wifi connection is excellent (but gives no access to internet).
IP -> DNS Settings
Max. Concurrent Queries = 500 (Default: 100)
Max. Concurrent TCP Sessions = 100 (Default: 20)
Let me add some useful information about the network topology.... look in the LOG for the reason mentioned there. (enable System >logging > Topics:wireless to see more information). Is it "station leaving (8)" ... or something else ?
08:45:11 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 rejected, forbidden by access-list
08:45:30 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap60 rejected, forbidden by access-list
08:45:32 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 rejected, forbidden by access-list
08:45:42 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 rejected, forbidden by access-list
08:45:44 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap63 rejected, forbidden by access-list
08:45:47 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap69 connected, signal strength -57
08:46:15 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap69 disconnected, received deauth: sending station leaving (3)
08:48:03 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 connected, signal strength -67
08:48:19 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap60 connected, signal strength -54
08:48:19 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 disconnected, registered to other interface
09:03:08 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap60 disconnected, group key timeout
09:05:13 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap60 connected, signal strength -50
/caps-man access-list
add action=accept allow-signal-out-of-range=10s disabled=no interface=any signal-range=-80..120 ssid-regexp=""
add action=reject allow-signal-out-of-range=10s disabled=no interface=any signal-range=-120..-81 ssid-regexp=""
/caps-man configuration
add channel=channel1 datapath=loccal_forwarding_datapath datapath.arp=disabled hide-ssid=no mode=ap name=cfg1 rx-chains=0,1,2 security=security1 ssid=xxxxxxx tx-chains=0,1,2
add channel=channel6 datapath=loccal_forwarding_datapath hide-ssid=no mode=ap name=cfg6 rx-chains=0,1,2 security=security1 ssid=xxxxxxx tx-chains=0,1,2
add channel=channel11 datapath=loccal_forwarding_datapath hide-ssid=no mode=ap name=cfg11 rx-chains=0,1,2 security=security1 ssid=xxxxxxx tx-chains=0,1,2
add channel=channel3 datapath=loccal_forwarding_datapath datapath.vlan-id=10 datapath.vlan-mode=use-tag hide-ssid=yes mode=ap name=cfgSmartWifi security=security2 ssid=YYYYY
add channel=channel5 datapath=loccal_forwarding_datapath datapath.vlan-id=50 datapath.vlan-mode=use-tag hide-ssid=yes mode=ap name=cfgCameraWiFi security=security2 ssid=ZZZZZ
/caps-man datapath
add arp=reply-only client-to-client-forwarding=yes local-forwarding=yes name=loccal_forwarding_datapath
/caps-man channel
add band=2ghz-b/g/n control-channel-width=20mhz frequency=2412 name=channel1
add band=2ghz-b/g/n control-channel-width=20mhz frequency=2437 name=channel6
add band=2ghz-b/g/n control-channel-width=20mhz frequency=2462 name=channel11
add band=2ghz-b/g/n control-channel-width=20mhz frequency=2422 name=channel3
add band=2ghz-b/g/n control-channel-width=20mhz frequency=2432 name=channel5
/caps-man provisioning
add action=create-enabled comment="CAP 1" master-configuration=cfg1 radio-mac=XX:XX:XX:XX:D8:FD slave-configurations=cfgCameraWiFi,cfgSmartWifi
add action=create-enabled comment="CAP 2" master-configuration=cfg6 radio-mac=XX:XX:XX:XX:0D:A9 slave-configurations=cfgCameraWiFi,cfgSmartWifi
add action=create-enabled comment="CAP 3" master-configuration=cfg11 radio-mac=XX:XX:XX:XX:5A:7C slave-configurations=cfgCameraWiFi,cfgSmartWifi
add action=create-enabled comment="CAP 4" master-configuration=cfg1 radio-mac=XX:XX:XX:XX:E3:5E slave-configurations=cfgCameraWiFi,cfgSmartWifi
/caps-man security
add authentication-types=wpa-psk,wpa2-psk encryption=aes-ccm name=security1
add authentication-types=wpa-psk,wpa2-psk encryption=aes-ccm name=security2
/ip dns
set allow-remote-requests=yes max-concurrent-queries=1000 max-concurrent-tcp-sessions=200 servers=1.1.1.1,8.8.8.8,9.9.9.9,208.67.220.220,208.67.222.222,8.8.4.4,1.0.0.1
08:45:11 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 rejected, forbidden by access-list
08:45:30 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap60 rejected, forbidden by access-list
08:45:32 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 rejected, forbidden by access-list
08:45:42 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 rejected, forbidden by access-list
08:45:44 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap63 rejected, forbidden by access-list
08:45:47 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap69 connected, signal strength -57
08:46:15 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap69 disconnected, received deauth: sending station leaving (3)
08:48:03 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 connected, signal strength -67
08:48:19 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap60 connected, signal strength -54
08:48:19 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 disconnected, registered to other interface
09:03:08 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap60 disconnected, group key timeout
09:05:13 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap60 connected, signal strength -50
/caps-man access-list
add action=accept allow-signal-out-of-range=10s disabled=no interface=any signal-range=-80..120 ssid-regexp=""
add action=reject allow-signal-out-of-range=10s disabled=no interface=any signal-range=-120..-81 ssid-regexp=""
Ok, thank you for the explanation. Do you have any suggestion to mitigate or resolve the issue?(3) is different from (8) as reason. (8) is the client who disconnects, (3) is because you kicked the client out !
https://aboutcher.co.uk/2012/07/linux-w ... son-codes/
This rejected and disconnected .....
Is caused by this .... (and even forbidden for 10 seconds, after the disconnect)Code: Select all08:45:11 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 rejected, forbidden by access-list 08:45:30 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap60 rejected, forbidden by access-list 08:45:32 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 rejected, forbidden by access-list 08:45:42 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 rejected, forbidden by access-list 08:45:44 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap63 rejected, forbidden by access-list 08:45:47 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap69 connected, signal strength -57 08:46:15 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap69 disconnected, received deauth: sending station leaving (3) 08:48:03 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 connected, signal strength -67 08:48:19 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap60 connected, signal strength -54 08:48:19 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap66 disconnected, registered to other interface 09:03:08 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap60 disconnected, group key timeout 09:05:13 192.xx.xx.xx caps,info XX:XX:XX:XX:07:F6@cap60 connected, signal strength -50
"action=reject allow-signal-out-of-range=10s " will keep the reject decision for 10s , even if the signal is out of the forbidden range
Code: Select all/caps-man access-list add action=accept allow-signal-out-of-range=10s disabled=no interface=any signal-range=-80..120 ssid-regexp="" add action=reject allow-signal-out-of-range=10s disabled=no interface=any signal-range=-120..-81 ssid-regexp=""
add action=accept allow-signal-out-of-range=30s disabled=no interface=any signal-range=-86..120 ssid-regexp=""
add action=reject allow-signal-out-of-range=3s disabled=no interface=any signal-range=-120..-87 ssid-regexp=""
Many thanks. Going to try.What I would try ...
.Code: Select alladd action=accept allow-signal-out-of-range=30s disabled=no interface=any signal-range=-86..120 ssid-regexp="" add action=reject allow-signal-out-of-range=3s disabled=no interface=any signal-range=-120..-87 ssid-regexp=""
If you want to push off slow connections, rise the "basic rate" from 6 Mbps to 18 Mbps. (some experimenting to tune may be required. 12Mbps? 24Mbps?)
Hello.Don't know if it can help but i have same trouble and i just change name of SSID on virtual wifi (i have trouble "station leaving" only on virtual wifi) with a short name without special chararcter and for moment it's ok.I see this problem the same day I configure the router.
Now on some jobs the problem pops up a few days after I have left. Those ones... disabling the radio interface sometimes cures it. But the jobs where I see those messages right away... I have to change manufactures. Too many lost hours and clients.
before : Restaurant-Jeannala
After : Jeannala
Oh please. this problem continues 6 years! I NEVER had any problems with wifi until i started using Mikrotik.[No need to hait Mikrotik - I think it would be the same with another AP.
Well whats user @dbrowning2 above saying about forcing 1,6,12 options on DHCP ?I dont understnad hes post fully.It looks like it has trouble getting a DHCP lease. That is enough reason for "modern" devices to disconnect the L2 connection as well.
Debug it from the DHCP side first.
Nah... Its pretty easy to pinpoint. You just have to accept reality.Something makes the phone decide to disconnect, that can be hard to pinpoint without some wireless sniffing.
I get that exact message and see that pattern all time. I can keep my Mikrotik Routers and Switches... But I can't keep Mikrotik wireless in there. Switch to anyone of 6 other vendors and problems stop.It looks like it has trouble getting a DHCP lease. That is enough reason for "modern" devices to disconnect the L2 connection as well.
Debug it from the DHCP side first.
Sure have.And any of you two sniffed the traffic to see what's pushing the phone(s) to disconnect?
And exactly the same case my side, i got this issue more or less on all sites.Sure have.And any of you two sniffed the traffic to see what's pushing the phone(s) to disconnect?
Did extensive trouble shooting with Mikrotik too. They finally copped to the fact that they can't deal with interference. They called my environment "unique."
Except I had the exact same problem, across nearly 100 UNIQUE SITES, all over the United States.
I agree with that. I do not roll out indoor office wireless using MikroTik APs until they have equipment that can cope with the standards of today. But that wasn't the question.I get that exact message and see that pattern all time. I can keep my Mikrotik Routers and Switches... But I can't keep Mikrotik wireless in there. Switch to anyone of 6 other vendors and problems stop.
My problem...I agree with that. I do not roll out indoor office wireless using MikroTik APs until they have equipment that can cope with the standards of today. But that wasn't the question.I get that exact message and see that pattern all time. I can keep my Mikrotik Routers and Switches... But I can't keep Mikrotik wireless in there. Switch to anyone of 6 other vendors and problems stop.
Me, don't judge me.Seriously who here is typing on this forum with their iphone 6?
There are known but unresolved problems with MT DHCP on wireless.Well whats user @dbrowning2 above saying about forcing 1,6,12 options on DHCP ?I dont understnad hes post fully.It looks like it has trouble getting a DHCP lease. That is enough reason for "modern" devices to disconnect the L2 connection as well.
Debug it from the DHCP side first.
I dont have any DHCP issues on wired clients, its just problem on wireless.
/ip dhcp-server option
add code=1 name=subnetmask value=0xffffff00
add code=6 force=yes name="WLAN-Domain Server" value=0xc0a85901
add code=12 force=yes name=Hostname value="\$(HOSTNAME)"
add code=6 name="LAN-Domain Server" value=0xc0445801
/ip dhcp-server option sets
add name=WLAN options="subnetmask,WLAN-Domain Server,Hostname"
add name=LAN options="subnetmask,LAN-Domain Server,Hostname"