1
Votes

Omada SDN - Port Isolation

 
1
Votes

Omada SDN - Port Isolation

Omada SDN - Port Isolation
Omada SDN - Port Isolation
a week ago - last edited Tuesday

Hello,

I have a vulnerable device on my network that I'd like to isolate from the rest of my home network. The goal is to configure the switch port it's connected to so that it can only communicate with the gateway (router), and not with any other devices or ports on the switch.

I've attempted to do this using VLANs, but unfortunately, the device in question needs to connect to a VPN, and the connection becomes unstable unless it's on the default (untagged) network. I've spent a lot of time trying to get it working over a separate VLAN, but it just doesn't play nice.  Too many dropouts and instability.

In the SDN interface, I see an option for Port Isolation, but I can't find a way to configure it in detail. From what I understand, Port Isolation simply blocks isolated ports from talking to each other, while still allowing them to talk to non-isolated ports. That’s very rigid and doesn’t offer the level of control I need.

What I’m really looking for is a way to configure one specific port so it can only communicate with the gateway (or upstream), while allowing the rest of the ports on the switch to continue communicating with each other normally.

Is there a workaround or feature I’m missing that would let me achieve this?

Thanks in advance!

#1
Options
1 Accepted Solution
Re:Omada SDN - Port Isolation-Solution
Saturday - last edited Tuesday

  @n4n0_76 

 

You can only really do this with ACLs

 

Port isolation doesnt stop devices on other vlans communicating with it, because those other vlans will have to hop traffic through the gateway so in that case it isnt direct port<>port.  Since you want it to communicate with the gateway for outbound internet traffic, you cant isolate it from that.

 

You need to set up switch ACLs to prevent that individual IP reaching anything but the gateway, and all other IPs from reaching that single device.

 

Also, having a device on another vlan should not stop it from having stable outbound VPN at all as long as your configurations are correct.  Even then, you still need to set up the lan<>lan ACLs

Main: ER8411 x1, SG3428X x1, SG3452 x1, SG2428LP x1, SG3210 x1, SG2218P x1, SG2008P x3, ES208G x1, EAP650 x6 Remote: ER7206 v2 x1, ER605 v2 x3, SG2008P x2, EAP650 x2, ES205G x1 Controller: OC300
Recommended Solution
#3
Options
2 Reply
Re:Omada SDN - Port Isolation
a week ago - last edited a week ago

  @n4n0_76 

Thank you for your post.To meet your requirement, you can configure Port Isolation so that the device can communicate only with the specific uplink device you define.Please refer to the configuration guide below.

How to configure Port Isolation on Smart and L2 Managed Switches using the new GUI

Based on the current definition of port isolation on the Omada Controller:
“An isolated port cannot communicate directly with any other isolated ports, while the isolated port can send and receive traffic to non-isolated ports.”Therefore, this feature may not fully meet your requirements.However, I will forward the issue you raised for further feedback.

#2
Options
Re:Omada SDN - Port Isolation-Solution
Saturday - last edited Tuesday

  @n4n0_76 

 

You can only really do this with ACLs

 

Port isolation doesnt stop devices on other vlans communicating with it, because those other vlans will have to hop traffic through the gateway so in that case it isnt direct port<>port.  Since you want it to communicate with the gateway for outbound internet traffic, you cant isolate it from that.

 

You need to set up switch ACLs to prevent that individual IP reaching anything but the gateway, and all other IPs from reaching that single device.

 

Also, having a device on another vlan should not stop it from having stable outbound VPN at all as long as your configurations are correct.  Even then, you still need to set up the lan<>lan ACLs

Main: ER8411 x1, SG3428X x1, SG3452 x1, SG2428LP x1, SG3210 x1, SG2218P x1, SG2008P x3, ES208G x1, EAP650 x6 Remote: ER7206 v2 x1, ER605 v2 x3, SG2008P x2, EAP650 x2, ES205G x1 Controller: OC300
Recommended Solution
#3
Options