Meraki

HodyCrouch · ‎Aug 9 2019

Take a look at this previous topic. https://community.meraki.com/t5/Wireless-LAN/How-to-check-the-blocked-clients-list/m-p/7765

HodyCrouch · ‎Apr 30 2019

Take a look at Wireless > Access Control (and make sure your guest SSID is selected at the top). Locate the "Captive Portal Strength" setting. If you "Allow non-HTTP traffic prior to sign-on", users will be able to access the internet for most purposes without going through your captive portal page.

HodyCrouch · ‎Apr 25 2019

This shouldn't be too difficult using the Dashboard API. Start with a call to get the inventory. This will include the serial and networkId for all devices. You will then have to loop through all of the devices and call /networks/{networkId}/devices/{serial}/wireless/radioSettings Each call will return the device serial and rfProfileId. You will be working against the API rate limit, so make sure your script is throttled and that you include some retry logic. You should be able to get through a few thousand access points in less than 5 minutes.

HodyCrouch · ‎Apr 10 2019

The log entries actually show that the splash page frequency is configured to one hour (3600 seconds). Look at each line that shows a Splash Authentication. As suggested by @kYutobi , you should modify the Splash Page Frequency setting.

HodyCrouch · ‎Apr 8 2019

Have you considered VLAN tagging? You can set your guest SSID to tag with a different VLAN and use the "different gateway" to provide DHCP. That approach would provide you with the level of control you're looking for over the traffic routing.

HodyCrouch · ‎Mar 14 2019

I checked one of my own organizations and I see the same behavior (more jagged lines in the report for Feb 18 - Feb 24). I didn't make any WiFi configuration changes in your two time periods. My guess is that Meraki stores usage data at a high resolution for a limited period of time and keeps lower resolution usage data available for a longer period. It feels like they are using 30 days at the approximate cutoff. In a few quick tests, I found that the summary report showed higher resolution usage data whenever the start date of the report was within the last 30 days. Any older than that and the entire usage data plot showed lower resolution data. Again, just a guess so check it out for yourself and see if you agree.

HodyCrouch · ‎Mar 7 2019

You should start by logging in to Meraki Dashboard and looking at Help > Firewall Info. That page will show you the required firewall rules to allow Meraki equipment to communicate with the dashboard. With brand new (or factory reset gear), it's generally a good idea to connect them somewhere with DHCP and Internet access to allow the initial configuration to be downloaded. After that, you can do whatever you want.

HodyCrouch · ‎Mar 4 2019

The devnet sandbox is a good place to start. When you open the sandbox, you should see a username and password that you can use to login to Meraki Dashboard at meraki.cisco.com. You will also see an API key that you can use with the dashboard APIs. Once you login to Meraki Dashboard (using the credentials from the Sandbox page), go to Help > API docs. https://create.meraki.io/ is also a great resource for getting started.

HodyCrouch · ‎Feb 17 2019

The API does not appear to support setting different group policies for a client by SSID. I'm not aware of any workaround.

HodyCrouch · ‎Feb 15 2019

Your idea that Meraki keeps the OS information when a device previously connected to the network sounds reasonable. I doubt that Meraki would make that information available across organizations, but there's no way to know for sure without either testing yourself or getting Meraki to tell you.

HodyCrouch · ‎Feb 15 2019

I did a quick scan of some data from the Scanning API in a couple of environments. I only see a value for OS when the device is connected to the network. I've never seen details from Meraki on how they identify the OS. I would guess that they are using fingerprints of certain network traffic, similar to remote OS detection in nmap. Meraki appears to keep its own database when people flag the device type as inaccurate in Meraki Dashboard. If this guess is accurate, a device would have to associate to the network prior to OS detection. The results of OS detection may be inaccurate, especially when new devices, drivers, and OS versions are released. There's a decent chance that similar technology is used for detecting rouge access points on the LAN.

HodyCrouch · ‎Jan 30 2019

The endpoint /networks/[networkId]/clients/[id_or_mac_or_ip]/events includes parameters for startingAfter and endingBefore. The documentation warns against client applications setting these parameters. When you make a request to this API, the response includes a Link header. For example: Link: <https://n000.meraki.com/api/v0/networks/N_1234567890/clients/abc12345/events?startingAfter=1476908909.0>; rel=first, <https://n000.meraki.com/api/v0/networks/N_1234567890/clients/abc12345/events?startingAfter=1517256994.237001>; rel=next, <https://n000.meraki.com/api/v0/networks/N_1234567890/clients/abc12345/events?endingBefore=1548874564.0>; rel=last You can use the values of startingAfter or endingBefore in the Link header to work your way through all events for a given client. If you want to throw caution to the wind (as I might have done), you could try adding the endingAfter parameter to your original request and including the current unix epoch. Otherwise, the API seems to return the oldest events.

HodyCrouch · ‎Jan 30 2019

How are you performing the timestamp conversion? When I convert 1548864847, I get Wednesday, January 30, 2019 11:14:07 AM GMT-05:00

HodyCrouch · ‎Jan 16 2019

Does your account have full access at the organization level (not at the network level)?

HodyCrouch · ‎Jan 16 2019

Make sure the Dashboard API is enabled for your organization. Go to Meraki Dashboard > Organization > Settings. Look for the "API Access" setting.

HodyCrouch · ‎Jan 14 2019

When you see the 3 or 4 year term on the license information page, it's referring to the original length of the license. You can look at the 'Start date' column to learn when each license started. The '54 days' you see on the page means that your license will expire 54 days from now. Keep in mind that all Meraki licenses co-terminate for your entire network. Read this document to better understand the process https://documentation.meraki.com/zGeneral_Administration/Licensing/Cisco_Meraki_Licensing_Guidelines_and_Limitations/The_Science_Behind_Licensing_Co-Termination

HodyCrouch · ‎Jan 7 2019

In cases like this, your only option is to make a lot of separate API calls. To avoid the API request limit, you can use a rate limiter. For example, I sometimes use the throttled-request package with Node.js. Remember that the rate limit applies at the organization level. If you have any other integrations or tasks using the API, you need to consider the total usage. Using the first two letters of the model to determine the device type seems good enough for now.

HodyCrouch · ‎Dec 14 2018

If I'm reading this correctly, you want to set tuples in Meraki SM and access those key/value pairs from your custom Android application. Your application will need to use the RestrictionsManager object. Don't forget to check for changes when your app launches or resumes. You can also use intents to know when the configuration changes while your app is running. Further discussion is really outside of the scope of this forum. https://developer.android.com/reference/android/content/RestrictionsManager

HodyCrouch · ‎Dec 2 2018

When you add a license, you have the option of applying the license as additional devices or as a renewal. It looks like you added three of your licenses as renewals. As a result, you extended the expiration date of your one device rather than adding more devices to your network. You get a brief period when you can "undo" your license addition, which will let you correct the operation. That's why your screenshot has a circular arrow next to one of the licenses. If you don't have the "undo" option, you're going to have to contact Meraki support.

HodyCrouch · ‎Nov 19 2018

When you go to the Clients view and select 'all clients with a policy', notice the 'i' that appears to the right of the time period filter. The pop-up says: "This view will show you all clients that have a policy, regardless of when they last transferred data. The usage data is for the selected time period." In other words, you should see all clients on the network that have a policy, even if they haven't had any activity in the last 30 days.

HodyCrouch · ‎Oct 2 2018

Yes, you would create two RF Profiles. You then assign the RF profiles to your access points using the Wireless > Radio Settings page. You will find settings for 5GHz-only, 2.4GHz-only, and dual-band (with optional steering) on the RF Profile page.

HodyCrouch · ‎Sep 6 2018

You can use the Scanning API to receive connected clients along with their locations and RSSI. You also get the ssid, which you can use to filter by connected vs. probing devices. https://documentation.meraki.com/MR/Monitoring_and_Reporting/Scanning_API The Scanning API does not include client names (only mac addresses). If you want additional information about clients, you would use the Dashboard API (probably /devices/[serial]/clients). You would need the serial number of each access point, which you can get from the Dashboard API, from the Meraki Dashboard UI, or from the label on each access point.

HodyCrouch · ‎Aug 30 2018

That choice should be fine, but if you need a reference... https://time.is/San_Antonio The IANA time zone identifier for San Antonio is America/Chicago. In Meraki Dashboard, you can select "America - Chicago (UTC -5.0, DST)"

HodyCrouch · ‎Jul 30 2018

I believe the MR53 comes with mounting hardware for a drop-ceiling grid. Take a look at page 4 of the MR53 datasheet. The largest metal parts in the black foam twist on to the ceiling grid and are locked with set screws.

HodyCrouch · ‎Jun 21 2018

I take that back. I can't get this new API to work either. I've had success in the past with the similar API /api/v0/devices/[serial]/clients?timespan=7200 This returns all devices connected to a specified device. You would call this API for each device in a network.

About HodyCrouch

HodyCrouch

Community Record

Badges