I would like to setup a site-to-site setup to deploy around all of the remote sites where all “local” subnets would “see” each other, as well as the “hub” site (idealy with Bonjour/mDNS working across the subnets):
What would be the best approach for such a setup (using Mikrotik only) ?
Pretty close with multiple warehouses - we will need a specific (dedicated) network (in pratice a specific ETH attached to the router) to allow connecting and “seeing” across all the other locations at any given point. In essece whereever you are, assuming you plug into the “right” port, you have access (and can discover using mDNS) to all other devices that are also plugged in.
Good, in the sense that you are starting to provide the requirements but sill to much config speak.
The diagram is a good start but lets talk about needs of users, devices and locations without talking about swtiches routers etc.
I have five warehouses,
a. requirements within each warehouse (users, devices) what is unique about them as well!~
b. requirements of admin for the company assuming their is an HQ environment (logistics, ordering, usage??)
c. requirements for users and/or devices across warehouses, describe.
Without a hard understanding of the actual requirements, a design (and a config) are a stab in the dark.
To me it seems like a case for a hub-and-spoke L3 VPN with multicast routing as you want the subnets at sites A, B, … to be distinct ones. But I have no practical experience with multicast routing so can’t give you the exact configuration. The multicast package has to be installed on all routers. I would recommend to test the whole thing using 3 CHRs in a virtual environment.
Each have their unique network with unique subnet - very basic needs (some local LAN devices, internet access).
Then we have some unique “line of business” hardware that needs to be able to roam across those 5 warehouses at any time and, to the best of of out ability, to be as “plug and play” as possible whenever plugged into the “magic port” (ie a specific ETH on the router dedicated to this use). When plugged into that port they should be able to “see” all the other subnets and “discover” their pears using mDNS. They would be authorised by being plugged into said designated port and MAC address (this is not a high security setup, it is just to avoid the unsuspecting user using the dedicated port despite instructions, but even in so doing and even if the MAC filtering would not work there is no major issue for them being able to see the other subnets).
Yep - I guess we will have to settle to that solution. IP could be assigned based on the MAC of each device (there are not that many of them)… but we would have loved to step it up