Restricting site to site vpn access between networks

[acadiana]

I have about 15 networks that are under one dashboard. I have site to site vpn enabled for 2 networks that works just fine. Today I need to connect 2 other networks that do not need to communicate with the first 2. How do I do that? It seems they can all communicate right now.

[ww]

You need to use the vpn firewall to create fw rules.

https://documentation.meraki.com/MX/Site-to-site_VPN/Site-to-site_VPN_Firewall_Rule_Behavior

Another option would be to use a group policy that is using stateless fw rules. And apply that to the vlans that are part of the vpn.https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_and_Applying...

[alemabrahao]

Hi,

You can create an L3 rule on the site-to-site VPN page.

[acadiana]

It shows that its for non meraki peers, but these are all meraki peers. Still use that rule section?

[alemabrahao]

I use It for SD-WAN and It works well.

[ww]

"These firewall rules will apply to all MX networks in the organization that participate in site-to-site VPN (both AutoVPN and Non-Meraki)."

[alemabrahao]

Overview

Administrators have the ability to add firewall rules to restrict the traffic flow through the VPN tunnel for a Cisco Meraki MX Security Appliance. Similar to other Meraki firewall options, this firewall is stateful and will only block traffic if it does not match an existing flow.

These firewall rules will apply to all MX networks in the organization that participate in site-to-site VPN (both AutoVPN and Non-Meraki).

Creating Firewall Rules

To create a firewall rule, follow the steps below.

1. Navigate to Security & SD-WAN > Configure > Site-to-site VPN.

2. Select Add a rule in the Site-to-site outbound firewall under the Organization-wide settings section of the page.

3. Fill in the desired parameters for the rule

4. Select Save changes.

Considerations for VPN Firewall Rules

When configuring VPN Firewall rules, it is important to remember that traffic should be stopped as close to the originating client device as possible. This cuts down on traffic over the VPN tunnel and will result in the best network performance. Because of this, site-to-site firewall rules are applied only to outgoing traffic. As such, the MX cannot block VPN traffic initiated by non-Meraki peers. 

https://documentation.meraki.com/MX/Site-to-site_VPN/Site-to-site_VPN_Firewall_Rule_Behavior

[acadiana]

What should the rule look like. Source and Destination?

[ww]

Depends on your needs.. but For example: 

Allow >

source: location1 and location2 subnet   destination: location1 and location2 subnet

Allow >

source: location3 and location4 subnet  destination: location3 and location4 subnet

Deny > any any

[alemabrahao]

Considerations for VPN Firewall Rules

When configuring VPN Firewall rules, it is important to remember that traffic should be stopped as close to the originating client device as possible. This cuts down on traffic over the VPN tunnel and will result in the best network performance. Because of this, site-to-site firewall rules are applied only to outgoing traffic. As such, the MX cannot block VPN traffic initiated by non-Meraki peers.