ecovalence wrote

Hello,

This is a first time setup of Omada Controller on Windows.  Here is the network map (caveat: The controller pc is connected directly to port 11 on the ER8411 - idk why the map won't update).

 

I have two LANs setup:

 

So that everything connected to Port 8 on the switch get the 10.0.0.1 subnet:

 

I need the primary pc (on the 192.168.10.1 subnet via port 11 of the ER8411) to be able to communicate with all pcs on on the 10.0.0.1 subnet (for RDP/etc.).  I read that should happen by default, but it's not.  So I setup two ACL's:

And it still won't connect.

I didn't think I had to create static routes or configure NAT when using Omada.  Am I wrong?

Currently there is no entry in Transmission > Routing or NAT.

 

Please advise!

 

 

Hi @ecovalence 

The VLAN interfacse will allow you to reach each other. No need to set up the ACL rules. Have you tested whether the two PCs can PING each other? Please also try to disable/turn off the firewall/antivirus software on PCs and try again.

We have guides to help you to build the multi networks:

How to Set Up VLAN Interface on the Omada Router

How to Set Up VLAN Interface on the Omada Router With Omada Switch

How to configure Multi-Networks & Multi-SSIDs on Omada SDN Controller

 Hi @ecovalence 

We can confirm the VLAN interface on the gateway will not block the communication between different VLANs. You can try to PING the gateway IP address from different VLANs. For some PCs, the firewall on them might block the traffic from other VLANs.

And may I confirm that you have created a third VLAN? Could you share the whole page of your VLAN interface setting and the page of editing the VLAN? The screenshots you sent only contain the VLAN profile on switch.