D-Link Wireless Access Points For Business > DAP-2610

DAP-2610 with Apple Devices - Deauth Reason 6 Code

(1/3) > >>

davidrew8:
I am having some trouble with Apple devices (iPhone and iPad) being blocked from the wirless with Deauth Reason 6 code.  The device still shows attached to wirless but has no access to any external services (WWW, email etc.), its almost like its blacklisted.

The syslog server is recording multiple entries for the same device in a short timeframe:

AP=10:62:EB:A6:6B:70
iPhone=78:4F:43:32:8A:FF

<6>1 2018-01-17T14:51:53.664136+00:00 192.168.200.252  - - - [10:62:EB:A6:6B:70][192.168.200.252][0] [Wireless] 5G:Deauth:STA 78:4F:43:32:8A:FF(reason 6)
<6>1 2018-01-17T14:51:54.181915+00:00 192.168.200.252  - - - [10:62:EB:A6:6B:70][192.168.200.252][0] [Wireless] 5G:Deauth:STA 78:4F:43:32:8A:FF(reason 6)
<6>1 2018-01-17T14:51:54.691893+00:00 192.168.200.252  - - - [10:62:EB:A6:6B:70][192.168.200.252][0] [Wireless] 5G:Deauth:STA 78:4F:43:32:8A:FF(reason 6)
<6>1 2018-01-17T14:51:55.187775+00:00 192.168.200.252  - - - [10:62:EB:A6:6B:70][192.168.200.252][0] [Wireless] 5G:Deauth:STA 78:4F:43:32:8A:FF(reason 6)
<6>1 2018-01-17T14:51:55.692986+00:00 192.168.200.252  - - - [10:62:EB:A6:6B:70][192.168.200.252][0] [Wireless] 5G:Deauth:STA 78:4F:43:32:8A:FF(reason 6)
<6>1 2018-01-17T14:51:58.723040+00:00 192.168.200.252  - - - [10:62:EB:A6:6B:70][192.168.200.252][0] [Wireless] 5G:Deauth:STA 78:4F:43:32:8A:FF(reason 6)
<6>1 2018-01-17T14:52:57.697462+00:00 192.168.200.252  - - - [10:62:EB:A6:6B:70][192.168.200.252][0] [Wireless] 5G:Deauth:STA 78:4F:43:32:8A:FF(reason 6)
<6>1 2018-01-17T14:52:57.961568+00:00 192.168.200.252  - - - [10:62:EB:A6:6B:70][192.168.200.252][0] [Wireless] 5G:Deauth:STA 78:4F:43:32:8A:FF(reason 6)
<6>1 2018-01-17T14:52:57.964131+00:00 192.168.200.252  - - - [10:62:EB:A6:6B:70][192.168.200.252][0] [Wireless] 5G:Deauth:STA 78:4F:43:32:8A:FF(reason 6)
<6>1 2018-01-17T14:52:57.966391+00:00 192.168.200.252  - - - [10:62:EB:A6:6B:70][192.168.200.252][0] [Wireless] 5G:Deauth:STA 78:4F:43:32:8A:FF(reason 6)
<6>1 2018-01-17T14:52:58.095123+00:00 192.168.200.252  - - - [10:62:EB:A6:6B:70][192.168.200.252][0] [Wireless] 5G:Deauth:STA 78:4F:43:32:8A:FF(reason 6)
<6>1 2018-01-17T14:53:02.735508+00:00 192.168.200.252  - - - [10:62:EB:A6:6B:70][192.168.200.252][0] [Wireless] 5G:Deauth:STA 78:4F:43:32:8A:FF(reason 6)

The only way to reconnect is to switch the wirless off on the device and then re-enable it.  I think it tends to happen when the device is woken up but its not consistent.

I have searched several other forums both Apple and wirless focused for cannot find any definative advice.  I'm not sure if its a possible bug or just somthing the Apple device is not set correctly for.

Thanks again for any advice.


FurryNutz:
What security modes are you using?
Do you see these same errors if you turn OFF WPA2 security entirely and test? Turn on WPA2 after testing.

davidrew8:
I do have the AP's set for WPA2 only with AES Cypher on all SSID's as this is the most secure and fastest to authenticate.

There are no old legacy wireless devices on the network that require older protocols such as WPA/TKIP authentication.

I don't particularly want to expose the wireless network to any security threats by changing the authentication.  What's the thoughts behind the WPA2 bring a possible issue?

Thanks for the feedback.

FurryNutz:
Possible issue with security modes of the AP and the Apple devices. if the symptom isn't reproducible with OPEN wifi, and you change back to WPA 2 and is reproducible, could be something in the security mode.

I would also test WPA and TPIK only and see if the symptoms are reproducible as well.
I might try setting single mode G then try single mode N.
What channel width are you using? Try 20Mhz only then mixed 20/40Mhz. See if there is any change in symptoms...

Interesting, I found this:
http://community.arubanetworks.com/t5/Technology-Blog/802-11-Reason-Codes-and-Status-Codes/ba-p/257893
Not sure how applicable this is...
Remembering now that you mentioned, something about power and sleep modes causing this...been a while though.  :-\

JO:
Is your issue solved?
I’m having the same problem
Regards Jo

Navigation

[0] Message Index

[#] Next page

Go to full version