OK, so this should be relatively easy, but I am having trouble getting the packets to route correctly. We recently swapped out all of our Fortinet products for Meraki devices and are slowly expanding upon that. Firewalls are installed and configured, as well as switch stacks, APs, etc.
We need to essentially connect the 2 sites together using a wireless point-to-point transparent bridge. I say it is "transparent" because the switches see the link as just a long network cable. I got the wireless link connected and talking back and forth, but the packets don't seem to route correctly. I'm trying to determine if I need to setup a static route from the MX through the MS to the other sites. I have LLDP enabled and can see the switches 'see' each other at both ends, but there are some strange entries into the logs where the clients as Site A are getting DHCP addresses from Site B and vice versa. I need to figure out how to isolate the clients to grab DHCP leases (currently all being done from Windows servers) and tell network A to find network B and backwards, so as to not need to use VPN tunnels to connect them anymore. I had all of this working with my Fortinet products without issues, but I could also assign a faux IP to the port/interface on the other switches/routers, telling the devices how to route the packets through those interfaces. I have read through all the documentation I could find, but was hoping someone more familiar with Meraki in these forums could shed some light on this quicker.
When you say to create a route from side A to side B, is that on the MX or the MS device or both? Keep in mind that I just took this project over from the last employee who quit. It appears that no layer 3 interfaces have been created either to setup a route. I can configure a static route in the MX without issues, though neither devices has any L3 items enabled or in use I should say.