Seriously, what is Mikrotik’s problem with Apple Devices?
The devices lose the connection as soon as it enters the standby mode, and as soon as it reconnects, we can not get a new connection.
Does anyone have a suggested configuration for the connection does not fall all the time?
Thanks.
Routerborad: 2011UiAS-2HnD
System Version: 6.40.2
There are no known issues like you describe. Please post your wireless config export, also it would be nice to see the wireless log, when this happens.
# aug/25/2017 18:52:52 by RouterOS 6.40.2
# software id = JF25-4YTZ
#
# model = 2011UiAS-2HnD
# serial number = 5E6C059915FC
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n channel-width=20/40mhz-Ce \
comment=Wi-Fi country=brazil disabled=no mode=ap-bridge ssid=ITIDAI \
wireless-protocol=802.11
/interface wireless manual-tx-power-table
set wlan1 comment=Wi-Fi
/interface wireless nstreme
set wlan1 comment=Wi-Fi
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa-psk,wpa2-psk eap-methods="" \
group-key-update=1h mode=dynamic-keys supplicant-identity=MikroTik \
wpa-pre-shared-key=***** wpa2-pre-shared-key=*****
/interface wireless access-list
add mac-address=9C:D2:1E:EA:6E:AD
Also please post the logs from the moment when the Apple device can’t connect.
It is normal that they disconnect. They will wake up when needed.
19:05:05 wireless,debug wlan1: CC:44:63:32:16:AE attempts to associate
19:05:05 wireless,debug wlan1: CC:44:63:32:16:AE not in local ACL, by default accept
19:05:05 wireless,info CC:44:63:32:16:AE@wlan1: connected
19:15:25 wireless,info CC:44:63:32:16:AE@wlan1: disconnected, extensive data loss
Poor signal or noise in this case.
Check registration table and see what you get there
Is your DHCP Lease Time set to less than 8hrs?
I recommend 1d unless you need a shorter lease.
Interesting, my household is entirely Apple (MacBooks, iPads, iPhones & a hackintosh), save for an Android phone and a Dell notebook. No problems here. 2011UAS-2HnD v6.39.
I could not found the proper thread but I recall that removing STP or RSTP from the bridge which WiFi and LAN are part of resolved the problem. But it was long, long time ago …
Well, it is all about poor signal.
Have been using Apple devices all the time, everything was fine, no complaints.
I have problem with apple devices too !
My router RB3011- ros 6.39.2 after upgrade to 6.40.3 , the problem is still here . The APs are Linksys, TP-Links ! The problem is only with this Apple device with this mac addr.!
What is the issue here JohnTRIVOLTA ?
What is the lease time in your DHCP server ?
Lease time is 1 day . Тhe problem is that the device is trying to get an IP address - then a free one IP from the dhcp pool for 15-20 minutes and finally the device takes one. After an indefinite time, this problem is repeated !
P.S. I hope the problem is in the Apple device, which I say to its owner!
How long was the apple client sleeping, when he got this issue waking up?
Try to run packet sniffer before he wakes up, then during the issue.
OK , but this is a remote place , for this next week as I go to the site I will generate a file to explore it !
P.S. I have activated the sniffer for this mac address to see what it will collect for 24 hours.
No, because on all other Android devices I have no loss of signal, even on long distances.
In my case it’s disabled at Bridge.
Please report when you have a return of the tests.
Thank you.
That problem with Apple devices that decline offered DHCP addresses is not related to the wireless interface.
I know this, because at work we have a Cisco wireless system with a MikroTik router towards internet, and we
see these same errors. Lease time is 7 days, that is not the reason. Sometimes Apple users complain they
get no internet. But more often it just works. It is some strange problem…
it’s not MikroTik fault but Apple, pe2chl wrote that he have same problem with Cisco and I can agree because at my previous work we had same problem with AP connected to Juniper switch. Anyway as I remember you can find solution for that, it’s related with automatic location in network settings.