This is what I get... "The settings you requested require confirmation. Please review the following list. The VLAN subnet 0.0.0.0/29 overlaps with remote VPN subnets on non-Meraki peers Fortigate (0.0.0.0/24) and Fortigate Secondary (0.0.0.0/24). IP traffic will be routed to the smallest subnet that contains the IP address. In the non-Meraki VPN peers configuration, potential overlaps might occur between the subnets on Fortigate (10.1.0.0/24, 10.1.0.0/23, 10.1.20.0/24, and 10.1.20.0/25). Please note that in this case, IP traffic will be routed to the most specific subnet. To learn more, please refer to the Peer Availability section of the Site-to-site VPN Settings knowledge base article (accessible through the non-Meraki VPN peers tooltip)." Yes the home office is a Fortigate. However not all remote offices will get all of the same access. I have 1 site configured on a MX450 that is in another location back to the same Fortigate.  That is working fine.  I assigned that a network tag & have tags for the other mx-85's I have a ticket in to see what's up.    ... View more

So... Example My core office has a data subnet of 172.16.1.0. I need to have 22 remote sites connect to this subnet. Each site has it's own local subnet that is not the same. Remote site 1 is configured. I try to configure remote site 2 & then I get the duplicate subnet because I already have the 172.16.1.0 network going to remote site 1. Then do I need a NAT for the 172.16.1.0?   ... View more