Two Omada sites/networks on a single physical network?
Hi there
We're still in the R&D phase but we're stuck at stage two, and I'm now worrying that the design may not work.
We will be placing multiple "pods" (standalone meeting places) into multiple sites, each of which will be served by its own ER605 ER and an EAP653 offering VLAN isolation for IOT hardware as well as captive access for users wanting to connect to the network. They connect to the network via the host's internet (we are not the host).
The first setup worked flawlessly. Then we copied the site and adopted a new pair off ER and EAP, and now the first site works but the second does not connect any WiFi devices to the internet. The network (clumsily drawn) looks like this:
Note that we've designed it like this for good reason - some physical sites are huge and these two Omada "sites" could be 800m apart, therefore each AP will never see the other.
But with other sites, and in our R&D setup on the bench, they can obviously see each other (ERs tied to the same no-name switch, APs in the same WiFi space).
Is this whole approach flawed or is there any advice you can offer on what could be going wrong with the second Omada site setup?
What do you hope to do in the end?
This part would work. But they are under the same "another" router? That'll be fine as well. As long as they don't have duplicate IP addresses.
Cascade like would work but I am not sure I understand what issue you run into.
Controller will have different sites for different "Pods". And you need to port forward if necessary and place the controller in the network. VLAn is not a problem as it is inside another LAN. It does not affect the WAN side.
