This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Macbook Pro remains connected to AP230's but No Internet Access

Macbook Pro remains connected to AP230's but No Internet Access

Go to solution
dgillespie
New Contributor II

‎12-18-2019 12:33 AM

If the user disconnects from the wifi and reconnects then he will have internet access again but he has to do this a couple times an hour. It's an older macbook pro but it is utilizing 5G. Has anyone run across this before?

 

Here is are some sample logs with the error highlighted:

 

Log1

Middle Office 12/17/2019 15:58 D854A21D0194 Basic Tx probe resp (pwr 10dBm)

Front Office 12/17/2019 15:58 D854A21D8AE4 Detail Rx <specific> probe req (rssi -79dB)

Middle Office 12/17/2019 15:58 D854A21D01A4 Basic Sta(at if=wifi1.1) is de-authenticated because of STA roam away

Middle Office 12/17/2019 15:58 D854A21D01A4 Info Tx disassoc (reason 101 <n/a> pwr 11dBm)

Middle Office 12/17/2019 15:58 D854A21D01A4 Basic Sta(at if=wifi1.1) is de-authenticated because of notification of driver

Back Office 12/17/2019 15:58 D854A21D0324 Info Sending 1/4 msg of 4-Way Handshake (at if=wifi1.1)

Back Office 12/17/2019 15:58 D854A21D0324 Info Received 2/4 msg of 4-Way Handshake (at if=wifi1.1)

Back Office 12/17/2019 15:58 D854A21D0324 Info Received 4/4 msg of 4-Way Handshake (at if=wifi1.1)

Back Office 12/17/2019 15:58 D854A21D0324 Basic IP 172.17.33.44 assigned for station

Back Office 12/17/2019 15:58 D854A21D0324 Basic Tx auth <open> (frame 2 status 0 pwr 11dBm)

Back Office 12/17/2019 15:58 D854A21D0324 Basic Rx auth <open> (frame 1 rssi -65dB)

Back Office 12/17/2019 15:58 D854A21D0324 Basic Rx assoc req (rssi -65dB)

Back Office 12/17/2019 15:58 D854A21D0324 Info WPA-PSK auth is starting (at if=wifi1.1)

Back Office 12/17/2019 15:58 D854A21D0324 Basic Tx assoc resp <accept> (status 0 pwr 11dBm)

Back Office 12/17/2019 15:58 D854A21D0324 Info Sending 3/4 msg of 4-Way Handshake (at if=wifi1.1)

Back Office 12/17/2019 15:58 D854A21D0324 Info DHCP server sent out DHCP ACKNOWLEDGE message to station

Back Office 12/17/2019 15:58 D854A21D0324 Basic DHCP session completed for station

Back Office 12/17/2019 16:00 D854A21D0324 Info IPv6 address fe80::c17:5ea:2169:7d4 is snooped.

 

Log2:

Middle Office 12/17/2019 15:57 D854A21D01A4 Basic Tx probe resp (pwr 11dBm)

Middle Office 12/17/2019 15:57 D854A21D01A4 Basic Tx probe resp (pwr 11dBm)

Front Office 12/17/2019 15:57 D854A21D8AE4 Info Tx disassoc (reason 101 <n/a> pwr 11dBm)

Front Office 12/17/2019 15:57 D854A21D8AE4 Basic Sta(at if=wifi1.1) is de-authenticated because of STA roam away

Front Office 12/17/2019 15:57 D854A21D8AE4 Basic Sta(at if=wifi1.1) is de-authenticated because of STA roam away

Front Office 12/17/2019 15:57 D854A21D8AE4 Basic Sta(at if=wifi1.1) is de-authenticated because of notification of driver

Middle Office 12/17/2019 15:57 D854A21D01A4 Info DHCP server sent out DHCP ACKNOWLEDGE message to station

Middle Office 12/17/2019 15:57 D854A21D01A4 Basic Rx assoc req (rssi -50dB)

Middle Office 12/17/2019 15:57 D854A21D01A4 Info Sending 3/4 msg of 4-Way Handshake (at if=wifi1.1)

Middle Office 12/17/2019 15:57 D854A21D01A4 Info station sent out DHCP REQUEST message

Middle Office 12/17/2019 15:57 D854A21D01A4 Info Sending 1/4 msg of 4-Way Handshake (at if=wifi1.1)

Middle Office 12/17/2019 15:57 D854A21D01A4 Info Received 2/4 msg of 4-Way Handshake (at if=wifi1.1)

Middle Office 12/17/2019 15:57 D854A21D01A4 Info PTK is set (at if=wifi1.1)

Middle Office 12/17/2019 15:57 D854A21D01A4 Basic Rx auth <open> (frame 1 rssi -50dB)

Middle Office 12/17/2019 15:57 D854A21D01A4 Basic Tx auth <open> (frame 2 status 0 pwr 11dBm)

Middle Office 12/17/2019 15:57 D854A21D01A4 Basic Tx assoc resp <accept> (status 0 pwr 11dBm)

Middle Office 12/17/2019 15:57 D854A21D01A4 Basic IP 172.17.33.44 assigned for station

Middle Office 12/17/2019 15:57 D854A21D01A4 Basic DHCP session completed for station

0 Kudos
1 ACCEPTED SOLUTION

Go to solution
dgillespie
New Contributor II

‎12-20-2019 03:46 PM

@Sam Pirok​ and @Lloyd Sommerer​  I have recently discovered that this issue is not only happening on the one Macbook Pro - there are some Dell laptops running Win10 that are having the same issue: they remain connected but have no internet access. This seems to be related to Roaming in two ways:

  1. when a client moves from one side of the office to another, it roams to a new AP but it takes 30 seconds to 1 minute for internet access to work again.
  2. when a client is situated in a middle proximity between two AP's, without moving it can roam between both AP's causing the internet to drop.

 

I did have another call with Aerohive and something that stuck out to the engineer was the results of the show log buff | incl watchdog command on one of the AP's. There were a lot of entries (about 20+) and it essentially means that packets are getting stuck in the AP. This is a good reason why a client would remain connected (with valid ip) but have no internet - so we have an idea of what is happening.

 

It led him to believe one of two things:

  1. the AP's don't like the latest HiveOS - 10.0r7a. For this he recommended I downgrade to 8.4.11 on the one AP which I haven't tried yet.
  2. there is an issue with the eth0 NIC on the AP. I don't believe this to be the issue because other AP's are showing more than normal (more than 2 or 3) entries as well with the show log buff | incl watchdog command.

 

I did disable Frame Burst on the radio profiles and this did not resolve the issue. I am going to be updating the drivers on the Win10 laptops and do more testing.

View solution in original post

0 Kudos
14 REPLIES 14

Go to solution
systemscsn
Valued Contributor

‎10-23-2020 02:34 PM

Kevin, please let us know if the big difference was good or bad?

 

Because we are a school with a lot of Macbooks, your answer is important.  Thanks, J.

0 Kudos

Go to solution
JA
New Contributor III

‎10-08-2020 01:53 PM

Hi Kevin

When you disabled “Enable short guard interval” and “Enable Aggregate MAC Protocol Data Units” you said you noticed a big difference. Was that for the good or the bad?

Thanks

0 Kudos

Go to solution
KevinP1
Contributor II

‎10-06-2020 04:15 PM

Since upgrading to 10.0r9a and tweaking some radio config settings, our Apple devices have been performing much better. We’ve found potential issues or maybe even bugs within either the firmware or ExtremeCloudIQ that can severely change how our client devices perform.

With every ExtremeCloudIQ version update and AP650 firmware update, everything can change or break based on what Extreme updates. I’ve had basic setting changes break everything and clients couldn’t connect c0f2b0f0f4b5440197b140283262716d_1f62b.pngc0f2b0f0f4b5440197b140283262716d_1f621.png . I know we noticed a big difference after we disabled “Enable short guard interval” and “Enable Aggregate MAC Protocol Data Units”. I would say that 10.0r8 was a frustrating firmware release and around that time there were plenty of bugs in the early stages of ExtremeCloudIQ.

Thankfully, things are getting better and having consistant firmware updates and IQ updates have made a big difference.

0 Kudos

Go to solution
systemscsn
Valued Contributor

‎10-06-2020 01:36 PM

I know that windows 10 has an issue if its an Intel wifi card, and you have to go to intel and download the driver for it.  Once i did that it fixed most of my windows 10 issues.

 

I have firmware 10.0.5r5 and seem to have plenty of Macbook issues with wifi.   So thats interesting that you downgraded to 8.4r11 and it fixed your issue.  You are talking about the AP firmware right? for the AP650’s?  because that would be a major step back for us to do, if it were to fix all my macbook headaches!

0 Kudos
GTM-P2G8KFN