New MR 31.1.2 beta firmware: Https, rogue detection and general fixes

Solved
cmr
Kind of a big deal
Kind of a big deal

New MR 31.1.2 beta firmware: Https, rogue detection and general fixes

Wireless firmware versions MR 31.1.2 changelog

Important note

Bug fixes

  • General stability and performance improvements
  • HTTPS redirection does not work for LSP on wired interface
  • Channels missing for rogue detection

Known issues

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 6 APs)
If my answer solves your problem please click Accept as Solution so others can benefit from it.
1 Accepted Solution
thomasthomsen
Kind of a big deal

So ... did pcaps on the switch, nothing, on the wired and lan side of the AP, nothing.

Once I saw a single IPv6 packet on the switch from one of the wired clients, but, just the one single lonely packet.

 

So I tried to change the config on the wired ports a bit, nothing.

 

Restarting clients, static IP, and so on, nothing.

 

Then, in absolute desperation and almost agony, I re-booted the AP (why would you even do such a thing.... you monster).

And I was shocked that the wired ports then worked.... shocked I tell you 🙂

 

I have updated the case with my findings, but Im not sure there is anything to be done now that it , apparently, works again.

View solution in original post

12 Replies 12
jbright
A model citizen

When will AFC support for 6 GHz be incorporated into the 31.x firmware versions?

 

thomasthomsen
Kind of a big deal

And it immediately broke wired ports on my MR36H APs. 🙂

Case created, lets see what happens.

 

thomasthomsen
Kind of a big deal

Luckily I had this fine, well used, adapter in my drawer 🙂

thomasthomsen_0-1719480881152.png

 

News flash, 802.11g does not feel "modern" AT ALL, in 2024 🙂

Tried to have a webex call on the thing, hot dang it a lot of poor voice and video.

 

thomasthomsen
Kind of a big deal

So ... did pcaps on the switch, nothing, on the wired and lan side of the AP, nothing.

Once I saw a single IPv6 packet on the switch from one of the wired clients, but, just the one single lonely packet.

 

So I tried to change the config on the wired ports a bit, nothing.

 

Restarting clients, static IP, and so on, nothing.

 

Then, in absolute desperation and almost agony, I re-booted the AP (why would you even do such a thing.... you monster).

And I was shocked that the wired ports then worked.... shocked I tell you 🙂

 

I have updated the case with my findings, but Im not sure there is anything to be done now that it , apparently, works again.

thomasthomsen
Kind of a big deal

PS: And the trusted, tried and true, 802.11g adapter goes back in the drawer 🙂

thomasthomsen
Kind of a big deal

MR31.1.3 seems to "break" authentication / association on CW9164 after a while.

Different customers, and even in my lab, after the CW9164 has been online for a while a mix (when looking at the health score) of association and authentication errors seem to happen.

Eventlog on PSK/SAE networks shows EAPOL timeout, on dot1x networks not much is revealed, only what seems to be general authentication errors.

Reloading the AP fixes the problem for a while (dont know exact time).

I have not been able to do wireless packetcaptures of the problem, but it is happening on the wireless side of things.

It did not seem to be present on 31.1.2

Reverting to 30.7 and there are no problems at all, also after x time.

thomasthomsen
Kind of a big deal

MR APs do not seem to be affected.

cmr
Kind of a big deal
Kind of a big deal

My CW9166 was doing the same.  I've downgraded to 30.7 and it also now seems fine.

If my answer solves your problem please click Accept as Solution so others can benefit from it.
thomasthomsen
Kind of a big deal

"speak of the devil" ... new MR software arrived just now.

thomasthomsen
Kind of a big deal

Hmmmm ... "just" : 

General stability and performance improvements

Roaming-related issues with 802.11r configured SSID (Wi-Fi 6 APs)

 

 

Of course : Upgrading right now 🙂

 

thomasthomsen
Kind of a big deal

Was WPA3 transistion mode not supposed to fix this for me ?

This device has disabled the 6 GHz frequency band because there are no active SSIDs using WPA3 encryption.

or did I miss a "memo" ? 🙂

thomasthomsen
Kind of a big deal

Hmmm the AP lies to me, my phone is connected with 6Ghz ... interesting 🙂

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels