Meraki

CMIT-Dub · ‎Oct 4 2021

Great video but I must have missed something. My Site-B is configured as 'Spoke' selecting Site-A as hub. Site-A needed to be set to 'Hub'. VPN status is green. Both IP ranges are different, one 10.10.... and the other 192.168.... When I map from computer/Site-B to share on computer/Site-A it will not connect as simply in your video. Using Windows 10. What am I missing?

PhilipDAth · ‎Oct 22 2020

You really need to use wired and wireless 802.1x. https://documentation.meraki.com/MX/Access_Control_and_Splash_Page/MX_Access_Policies_(802.1X) If you haven't done it before - it's a lot to take on. You would want to get someone in to set this up.

cmr · ‎Oct 5 2020

@M4TT we have our DC MXs set up as @GIdenJoe said. They have been completely trouble free for a year or so with 8 remote sites over dual connected SD-WAN and an increasing number of homeworkers with either small MXs or Z3s using the supernet method described. We use Sophos XGs as the main internet facing firewalls and their NAT plays nicely, I believe Palo Alto does not, not sure about other vendors.

Bruce · ‎Oct 2 2020

Should work exactly as you expect. Whether it’s a MX/Z cellular model, or a model with a USB cellular modem, if the wired WAN links fail then the AutoVPN should rebuild on the cellular. As you rightly state though, the cellular won’t be part of a SD-WAN, it only provides failover.

Meraki

Community

About M4TT

M4TT

Community Record

Badges

Re: The Power of the Meraki Teleworker Gateway

Re: Z3 Access Control

Re: MX as one-armed VPN Concentrator limitations

Re: Z3 & Z3c VPN over cellular