Meraki

Erik_Gunnarsson · ‎Sep 26 2023

You cannot reach a Non-Meraki VPN network (3rd party application) from a Meraki AutoVPN tunnel (Branch site) Only local subnets on the MX that has the Non-Meraki VPN tunnel can reach it. (The AnyConnect subnet should work) If you need access from branches to 3rd party application you need to build a Non-Meraki VPN tunnel from each branch and from vMX to the provider

Erik_Gunnarsson · ‎Sep 25 2023

When you enable AnyConnect on the VMX, the subnet will show up under "Site-to-Site VPN" Here you can enable the subnet to have access to VPN. (No routing settings needed) Your branch sites will not be able to communicate with the 3rd party application behind the non meraki peer via SDWAN if you're planning for this? Depending on vMX model it handles different number of VPN clients: https://meraki.cisco.com/product-collateral/mx-sizing-guide/?file vMX small 50 vMX medium 250 vMX large 500 You need a seperate AnyConnect licens to run this

Erik_Gunnarsson · ‎May 10 2022

You don't need to add the license to the MX, you just need to have a valid license. "Customers are expected to have a valid AnyConnect license to use AnyConnect with the MX Appliance. Customers are not required to validate their licenses via the Meraki MX or the dashboard. Customers will only be required to accept terms and conditions of use before they can enable AnyConnect. If you are already using AnyConnect or setting it up for the first time, there will be a dashboard notification to accept the terms and conditions of use. There will be no disruption of the AnyConnect service for active networks." https://documentation.meraki.com/MX/AnyConnect_on_the_MX_Appliance/AnyConnect_Licensing_on_the_MX

Erik_Gunnarsson · ‎Sep 25 2018

I'm setting up an hybrid access policy with 802.1x and MAB on a Meraki MS120. Is it possible to set or change the MAC address format sent to radius? The auth request comes with the format aabbccddeeff from the MS120. In our enviroment, we already use authentication with alot of MAC address accounts in the Active Directory created with the format AA-BB-CC-DD-EE-FF. In our existing switches the only option seems to be upper or lowercase addresses seperated with - (hyphens). If it's not possible to change the format beeing sent from the Meraki, there seems to be no way for this to co-exist during a migration period to MS switches.

Meraki

Community

About Erik_Gunnarsson

Erik_Gunnarsson

Erik Gunnarsson

Community Record

Badges

Re: Client VPN using vMX

Re: Client VPN using vMX

Re: Please how can I adding L-AC-APEX-LIC on meraki appliance?

MAC address format, MAC Authentication Bypass

Re: Please how can I adding L-AC-APEX-LIC on meraki appliance?

Re: Client VPN using vMX

Re: Please how can I adding L-AC-APEX-LIC on meraki appliance?