Yes API would be your best option otherwise you will be doing an awful lot of navigating in a web browser.  ... View more

I have had a look there earlier but wasn't able to find anything.   Thanks for the reply though! ... View more

I think you are refering to the DDNS adress ? ( since you left a comment on a different post regarding DDNS ).   If so , you need to use the endpoint :  {0}/devices/{1}/managementInterface ... View more

Thanks for writing this up! Good stuff. ... View more

That does seem odd, I am guessing it's a mistake. I would confirm with support.   You could always look at your firewall logs to see where that traffic is going.  ... View more

We didn't experiment with changing client assignment, so I don't know.   FWIW:  we replicated the same issue (MR32 quits forwarding ARP frames) for clients connecting at 2.4GHz ... we resolved this by disabling 2.4GHz network-wide   --sk ... View more

You won't get the status via API. You will get the  device status which will be ''alerting''. You will then need to find what kind of alert since it is not specified via API. This is the only way at the moment. ... View more

Thanks Phil ! Lots of bedtime reading 🙂  ... View more

Facing same problem, is there any solution ? ... View more

Concur ... View more

Changing from getClients to getNetworkClients worked!!!!!!! network_id wouldn't apply here since I am wanting to return all Networks in my org. so I did have to change that argument to ( curr_net_id)   ... View more

I think this is more related to vulnerabilities. Let's say you find a bug with their implementation of a feature that doesn't involve a security issue ( or a vuln ) you won't get paid. Don't quote me on that ! ... View more

As @PhilipDAth mentioned the test user does not need to exist. If you are seeing this error message it is because at least one user recently failed to authenticate with the radius server or a recent dashboard radius server test failed. Each SSID that has radius enabled will have an option in the setting called "Radius Testing", by default this option is set to enabled. If enabled, the Meraki devices will send every 24 hours an Access-Request message to these RADIUS servers using  'meraki_8021x_test' to ensure that the RADIUS servers are reachable.  If a RADIUS test fails for a given device it will be tested again every hour until a passing result occurs. A subsequent pass will mark the server reachable and clear the alert, returning to the 24-hour testing cycle. Therefore if you are seeing this alert, one or more of your radius servers failed to respond or took too long to respond, if you do not want the dashboard to run these tests you can disable the option under your SSID settings. https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Alert_-_Recent_802.1X_Failure ✌️ ... View more

Great post and great explanation !  MTU , MSS can always be a nightmare to troubleshoot 🙂  ... View more

>Good idea ! However , Meraki has stated that the re-auth timer is a fixed 1h because of hardware limitation.   That's why I think having the RADIUS timeout adjusted would be the easiest thing to try. ... View more

Thank you for the quick repsonses!  This was the issue, I didn't undestand the IP parameter was for the uplink statistics destination, not for the public IP assigned to that WAN interface.  This is working for me now, thank very much! ... View more

Its all in ms (millisecond) For example 3rd Row is both 12.x ms ... View more

Also, I'm getting a reply like below, I see send and receive only but not the usage. is there any API that can retrieve the usage?      {         "application": "Miscellaneous web",         "destination": "webdefence.global.blackspider.com",         "protocol": "TCP",         "port": 80,         "recv": 35530,         "sent": 769,         "flows": 1835,         "activeTime": 21180,         "numClients": 6 ... View more

That is good lateral thinking! ... View more

Key is here to use as broad as possible rules and try to stay with IP only rules as much as possible.  In the documentation it clearly says that only rules that include TCP or UDP ports count towards the switch total. The amount of TCAM memory on MS switches must be way smaller than Catalyst switches causing limitations like this. The biggest issue with this is that if you have 10 clients with each different ACL's that contain layer 4 info you'll probably out of space already. ... View more

Thanks for the tip.   However, every time Meraki breaks something on the Stable channel, I'm told to upgrade to the Stable Release Channel or Beta channel for a fix.  Does anyone else see a problem with this?    I do realize that there are few options other than downgrade or upgrade or workaround, but please stop breaking "Stable".  That's what the other release channels are for.  ... View more

Hi Crocker,   I didnt know that had happened, if machine cert mapping is broken then the handshake should fail as the cert for the RADIUS server wouldnt be trusted.   The logs I do see suggest all is well until the client tries to return its cert, we see that leave the client machine, we also see it leave the WiFi AP and the switch but then we cannot see it traverse the VPN. We have had Microsoft check and they insist it never reaches their side, we had Meraki check and they say the cert is going through the VPN tunnel so its proving awkward to verify.   Thanks for the info. ... View more

See your point @PhilipDAth . Would be a good way to cross check that the NetworkID you’re working with also corresponds to the right Network in the Dashboard. ... View more

A "quick" way to find endpoint of expect results : api.meraki.com/api/v1/openapiSpec  then CTRL+F "static" and it was the first result 🙂  ... View more