VLAN Trouble - Devices can't talk to each other

VLAN Trouble - Devices can't talk to each other

VLAN Trouble - Devices can't talk to each other
VLAN Trouble - Devices can't talk to each other
a week ago - last edited Wednesday
Model: ER605 (TL-R605)   SG2008P  
Hardware Version: V2
Firmware Version: 2.2.6

Hello everyone!

 

I'm trying to isolate some PCs and servers on my network with a vlan and I'm running in to some unexpected behavior that I'm not able to solve.

 

Omada Controller version 5.14.32.4 is running in a docker container.


Hardware model, version, firmware, name:
ER605 V2.0 - 2.2.6 Router
TL-SG2008P V1.0 - 1.0.9 Office Switch
TL-SG2008 V3.0 - 3.0.9 Wall Switch
SG2008 V4.20 - 4.20.1 Hobby Room Switch
SG2008P V3.20 - 3.20.1 Living Room Switch

 

The connection map goes Router -> Office Switch -> Wall Switch -> Hobby Room Switch -> Living Room Switch

I also have three APs but they're not a factor.
My default LAN is 192.168.1.0/24.


I created VLAN10 192.168.10.0/24 for the devices I want to isolate in one direction.  The objective is the same as an IOT network where I can reach devices on VLAN10 from LAN, devices on VLAN10 cannot connect to LAN, and the devices on VLAN10 can communicate with each other.

 

Here are the steps I went through to create VLAN10:

  • New LAN interface
  • Select LAN1 for the LAN Interface
  • VLAN: 10
  • Gateway/Subnet: 192.168.10.1/24
  • DHCP Range: 192.168.10.100 - 192.168.10.254
  • Everything else is default

 

After creating this VLAN, switch profile VLAN10 was auto-generated.  The devices I want to isolate are on port 4 and 5 of the Hobby Room Switch.  After changing their IPs to the new range, 192.168.10.22 and 192.168.10.63, I set port 4 and 5 to the VLAN10 profile.  I tested the connection and I can connect to both boxes and they can connect to me on default LAN.

 

To isolate VLAN10 I first attempted a Switch ACL to block Source Network:VLAN10 to Destination Network:Default.  When enabled, I was no longer able to connect to either device.

 

I then disabled the switch ACL and tried a Gateway ACL to deny Source Network:VLAN10 to Destination Network:Default.  This works and allows me to connect to both .10 addresses.  I validated that neither .10 devices can connect to the default LAN.  All good here so far.  Both .10 devices can also connect to the internet.

 

For some reason though my .10 devices cannot communicate directly with each other.  192.168.10.22 and 192.168.10.63 cannot ping each other even though they're on the same VLAN on the same switch.

 

To add to the weirdness - 10.22 is a server.  If I launch a Docker container and assign it an address of 192.168.10.51 through MACVLAN, then it can connect to 10.63 no problem.  Any container hosted on 10.22 in bridge mode cannot communicate to 10.63 either.

 

I don't know what else to try.  To add to my confusion, pretty much any YouTube video or article I read instructs to use Switch ACL for isolation but that doesn't seem to be working for me for some reason.

  0      
  0      
#1
Options
2 Accepted Solutions
Re:VLAN Trouble - Devices can't talk to each other-Solution
a week ago - last edited Wednesday

Hi @BCCHowdy 

Thanks for posting in our business forum.

Did you start your setup with the guides?

How to Set Up VLAN Interface on the Omada Router

ACL Guide Compilation

Please double-check if there is anything wrong or misconceptions about the VLAN and ACL with the guides.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
Recommended Solution
  0  
  0  
#2
Options
Re:VLAN Trouble - Devices can't talk to each other-Solution
Tuesday - last edited Wednesday

It's my own fault.  I have a WireGuard connection configured on 10.22 and it's interfering with 10.63 communicating.  Not sure why but I'll dive into it.  Thank you for the guides Clive_A, I did review many of them to confirm the vlan setup I did was correct.  Thanks GRL for confirming the gateway ACL is the correct method for isolation.  I'm looking forward to seeing ip groups available on gateway ACL so I can allow access to my local DNS from VLAN10.

 

Thank you both!  I appreciate your responses.

 

-Howdy

Recommended Solution
  1  
  1  
#4
Options
3 Reply
Re:VLAN Trouble - Devices can't talk to each other-Solution
a week ago - last edited Wednesday

Hi @BCCHowdy 

Thanks for posting in our business forum.

Did you start your setup with the guides?

How to Set Up VLAN Interface on the Omada Router

ACL Guide Compilation

Please double-check if there is anything wrong or misconceptions about the VLAN and ACL with the guides.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
Recommended Solution
  0  
  0  
#2
Options
Re:VLAN Trouble - Devices can't talk to each other
Tuesday

  @BCCHowdy 

 

Switch ACL rules are not what you want, you want gateway ACL rules.

 

Switch rules are not stateful, therefore thay are unable to account for a situation like Device A cannot access device B, but device B can access device A

 

You need a stateful rule, which is a gateway ACL.  Unfortunately in controller mode you cannot currently use IP groups for individual IP address control (you can in standalone however), you can set them as whole LAN though.

 

rule 1:

LAN A > LAB B, Permit

 

rule 2:

LAN B > LAN A, Deny

 

 

  1  
  1  
#3
Options
Re:VLAN Trouble - Devices can't talk to each other-Solution
Tuesday - last edited Wednesday

It's my own fault.  I have a WireGuard connection configured on 10.22 and it's interfering with 10.63 communicating.  Not sure why but I'll dive into it.  Thank you for the guides Clive_A, I did review many of them to confirm the vlan setup I did was correct.  Thanks GRL for confirming the gateway ACL is the correct method for isolation.  I'm looking forward to seeing ip groups available on gateway ACL so I can allow access to my local DNS from VLAN10.

 

Thank you both!  I appreciate your responses.

 

-Howdy

Recommended Solution
  1  
  1  
#4
Options