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)
1 Accepted Solution

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

5 Replies 5
jbright
A model citizen

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

 

thomasthomsen
Head in the Cloud

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

Case created, lets see what happens.

 

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.

 

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.

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

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