Meraki

RaphaelL · ‎Aug 24 2022

Glad you got it working !

RaphaelL · ‎Aug 11 2022

Are you capturing a renew or a new lease ? eg : if you reboot the device it may go through d-o-r-a. If the dhcp lease is around 75% expired the camera will do a dhcp renew ( r-a ) .Both the request and ack will be unicast. Those are the common DHCP packets you will see on your network. ** I do not have a DHCP helper , the DHCP server is on the same LAN. Captures on your side will be slightly different.

RaphaelL · ‎Aug 11 2022

Hi , 1- Is there a MX in the flow ? ( You posted this under Security & SD-WAN ) MXs had nasty DHCP bugs that were resolved under MX 15.44 and higher. DHCP renew might fail ( in our case 100% of the time ) 2- DHCP process goes under D-O-R-A ( Discover - Offer - Request - Ack ). However under the DHCP renew process , the packets are unicast ( since the client already has an valid IP ) 3 - Do you have DHCP snooping enabled ? 4- Meraki is showing that on the port no offers are being received by the camera but when I do a packet capture on that specific port it shows that the offer is getting there. Which device are you capturing the DHCP offers ?

RaphaelL · ‎Aug 11 2022

Unfortunately no , the release notes don't go that deep in the level of detail. You might have to contact support to see if your behavior is fixed in a specific release. I haven't used critical vlan yet , so I can't share any inside on that feature 😞

RaphaelL · ‎Aug 11 2022

What MS version are you running ? I think there was issue with 802.1X auth on voice vlan prior to MS 14.33.X

RaphaelL · ‎Aug 10 2022

Hi , Yes it requires a licence. https://documentation.meraki.com/MX/Content_Filtering_and_Threat_Protection/Threat_Protection Threat Protection is available only with Advanced Security Edition licensing.

RaphaelL · ‎Aug 9 2022

Excellent ! Glad we were able to help you ! Have a good one

RaphaelL · ‎Aug 9 2022

Hi , You can apply a group policy to any network client with this endpoint : https://developer.cisco.com/meraki/api-v1/#!update-network-client-policy

RaphaelL · ‎Aug 9 2022

Hi , If you look at the documentation the input must be an array : https://developer.cisco.com/meraki/api-v1/#!cycle-device-switch-ports like : ports = ['1', '2-5'] or simply ports = ['1'] while you are probably passing a string from getDeviceSwitchPorts ( portId = "1" ) There are many ways to fix it. portlist = [] portlist.append(port['portId']) port_Cycle = dashboard.switch.cycleDeviceSwitchPorts(device['serial'], portlist)

RaphaelL · ‎Aug 8 2022

Currently testing it. I'm on a 3 weeks vacation so I will have to follow up that issue when I come back. Will keep this thread updated

RaphaelL · ‎Aug 4 2022

Well done to everyone !

RaphaelL · ‎Aug 4 2022

We currently only have iphones and ipads. I will have to try to set it to adaptive.

RaphaelL · ‎Aug 4 2022

Hi ! Have you tried messing with 802.11r ? Enabled , Adaptive ?

RaphaelL · ‎Aug 3 2022

Hi , This is the correct endpoint for outbound firewall rules on a MX : https://developer.cisco.com/meraki/api-v1/#!get-network-appliance-firewall-l-3-firewall-rules getNetworkApplianceFirewallL3FirewallRules It would have been easier to state 'outbound' somewhere on that documentation

RaphaelL · ‎Jul 28 2022

Hi , I'm 99% sure that this feature is not available via API. It would be a great addition to the API ! Clicking the 'Give your feedback' box on the bottom right of your dashboard page and do the suggestion ! It helps !

RaphaelL · ‎Jul 26 2022

That is pretty much all the syslog events that are sent by Meraki devices. Not sure to understand your question. The detail is already in the documentation that you linked

RaphaelL · ‎Jul 26 2022

Hi , Those are the IEEE 802.11 codes . They can be found on google or that link : https://community.cisco.com/t5/wireless-mobility-knowledge-base/802-11-association-status-802-11-deauth-reason-codes/ta-p/3148055

RaphaelL · ‎Jul 25 2022

Yes that would be the way to do it ! Somehow I missed the part about the Group Policy in your post.

RaphaelL · ‎Jul 25 2022

Hi , Simply do : Deny 192.168.1.0/24 RFC1918 ( 10.0.0.0/8 , 192.168.0.0/16 , 172.16.0.0/12 ) Any Permit 192.168.1.0/24 Any Any This will block anything from 192.168.1.0/24 towards rfc1918 , except it's own vlan and will allow the flows towards the internet.

RaphaelL · ‎Jul 22 2022

Woot Woot ! Thanks a lot guys ! 😀

RaphaelL · ‎Jul 19 2022

The call is indeed : dashboard.organizations.getOrganizationClientsBandwidthUsageHistory(orgID) if you do a print(meraki.__version__) ( in python3.X ) Are you running the latest version ( 1.22.1 ) ? You might be on a older package version ! You can update / upgrade the package version with : pip install meraki --upgrade Edit : just tried the endpoint with the package and confirmed that it is working for my Org.

RaphaelL · ‎Jul 18 2022

Still no luck with 28.6 nor 28.6.1 ( the code is identical to 28.6 ) Going to test 29.1 soon..

RaphaelL · ‎Jul 18 2022

Hi , This is probably the feature you are refering to : https://documentation.meraki.com/MR/Encryption_and_Authentication/IPSK_Authentication_without_RADIUS

RaphaelL · ‎Jul 15 2022

Not sure to understand your question but A Port 49 <--> C Port 49 B Port 49 <--> D Port 49 will work since A,B are on the same stack and C,D on the same stack. vPC is only needed when the hardware is not stacked or configured in a VSS mode. If your goal is to plug a device into stack A,B and stack C,D and try to bundle the links , that won't work :

RaphaelL · ‎Jul 13 2022

Should be an easy fix ! Syslog shows : dport=51514 but the rule states 51414...

About RaphaelL

RaphaelL

Raphael Letourneau

Community Record

Badges