About YellowKLR

YellowKLR · ‎05-15-2020

Yes, I was checking the site-to-site outbound firewall. I did the trace route from the client VPN to a remote site - it did not go to the MX90. I recreated my W10 VPN connection in case there was an error, still can't get to the remote site. We have the VPN connection set up for split tunnel, so I changed the setting to have the VPN connection use the default gateway on the remote network - and I was able to access resources on the remote site. Our system changes have not been well-documented, so I'm guessing that IT laptops were initially set up with a full tunnel VPN connection so we could manage all of our remote sites when off campus, even though the official documentation states to use a split tunnel. Thanks for the assistance and nudge in the right direction.

YellowKLR · ‎05-15-2020

Hello, When I am connected to the client VPN on our MX90, I am not able to access resources on our remote sites that are connected via site-to-site VPNs. Here's the background... Our Dashboard had all the switches installed across 23 remote sites in one network, and all the APs in another network. I reorganized the Dashboard, creating combined networks for our remote sites. Before the reorganization, I could access resources on all of our remote sites when connected to the client vpn - but no longer. The client VPN runs on the MX90 at our main site, I can access all resources on that site's subnets, but I cannot ping anything on the remote subnets. The firewalls can ping each other. I confirmed that the client VPN on the MX90 is included in the VPN. On the remote MXs, I looked at the remote VPN participants and confirmed that the client VPN subnet was listed as a participant. The site to site VPN was not changed, it is set up with the MX90 as the hub, and all other sites as spokes. Does anyone have suggestions as to what I can check?

YellowKLR · ‎03-28-2020

Thank you for all of your responses - I am new to the community, and appreciate how helpful everyone is!

YellowKLR · ‎03-28-2020

* You could create some backup scripts I looked at the API documentation when someone referred to using to manage SSIDs, using it is going to be a learning curve for me. I want to move just the first network and make sure everything works as it is supposed to. I'll wait to do more stores until that first one opens up again, just to make sure nothing goes wonky. Hopefully by that time I'll have learned about the API and can make use of it.

YellowKLR · ‎03-26-2020

* In your case you shouldn't be moving switches, but combining existing networks All of our switches are in 1 network, and all of our APs are in another network - so I will be creating a combined network by moving the MR and MS for the site into the same network as the MX. Example: For our B'ville store, I was expecting to take the store's MS from RM-Switches and MR from RM-APs and move them to the existing MX-Bville network.

YellowKLR · ‎03-26-2020

We run thrift stores, it is a light load,no analytics needed. Each store has an MX, one MS and one MR.

YellowKLR · ‎03-26-2020

Much of our organization is shut down at the moment, so I figured this would be a good time to do some cleanup. When we moved to Meraki, our dashboard was set up to have separate networks for each firewall (22), then all of the switches from all sites were in one big network, and all APs in another. I've been researching best practice, and want to switch to combined networks. I've read how to move forward, it seems straightforward and I am planning on converting one of our closed stores tomorrow. Has anyone run into any 'gotchas' or unexpected behavior when moving to a combined network?

YellowKLR

Community Record

Badges

Re: Client VPN cannot ping site-to-site

Client VPN cannot ping site-to-site

Re: Reorganizing our Dashboard

Re: Reorganizing our Dashboard

Re: Reorganizing our Dashboard

Re: Reorganizing our Dashboard

Reorganizing our Dashboard

Re: Client VPN cannot ping site-to-site

Re: Reorganizing our Dashboard