Business Community > WiFi > EAP615-WALL not passing 802.1q tagged traffic on port 1 to port 2 tagged with vlan 192
< WiFi

EAP615-WALL not passing 802.1q tagged traffic on port 1 to port 2 tagged with vlan 192

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

EAP615-WALL not passing 802.1q tagged traffic on port 1 to port 2 tagged with vlan 192

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
EAP615-WALL not passing 802.1q tagged traffic on port 1 to port 2 tagged with vlan 192
EAP615-WALL not passing 802.1q tagged traffic on port 1 to port 2 tagged with vlan 192
2024-08-02 11:28:12 - last edited 2024-08-02 11:46:09
Tags: #VLAN & Multi-Networks #Network Connectivity
Model: EAP615-Wall  
Hardware Version: V1
Firmware Version: 1.2.4

SG2210p powering a 615-WALL. the gateway is connected router on a stick style to the SG2210P (802.1q all vlans to pfsense router)

 

I have a vlan aware workstation on port 1 of the EAP615-WALL  I configured the second port to vlan 192 in the omada controller.

 

The attached device that is unaware of vlan's successfully connected to the network and aquired an ip from the gateway. however

my workstation could not connect to the device on port 2.

I suggest this is a bug.

 

Both devices can talk to the gateway 192.168.1.1 (tagged traffic from a port of the SG2210P)

but 
The Workstation (802.1q aware)  can't communicate with the device attached to port 2 (tagged at the EAP615-wall) 

 

Workstation 802.1q taged as vlan 192 in the client machine -> port 1 (all vlans)

Device -> port 2 (vlan 192)

 

 

  0      
 
  0      
 
#1
Options
8 Reply
Re:EAP615-WALL not passing 802.1q tagged traffic on port 1 to port 2 tagged with vlan 192
2024-08-05 02:36:39

Hi  @GrantD 

 

Currently, the ETH ports of EAP-wall are untagged by default, and they can't be modified. 

If possible, please try to give the workstation the ability to deal with untagged packets.

Wish you a happy life and smooth network usage!  >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#2
Options
Re:EAP615-WALL not passing 802.1q tagged traffic on port 1 to port 2 tagged with vlan 192
2024-08-06 01:28:26

  @Vincent-TP 

 

Clearly the vlan can be set on the ports of the EAP615-wall as in the picture of my original paste.

  0  
  0  
#3
Options
Re:EAP615-WALL not passing 802.1q tagged traffic on port 1 to port 2 tagged with vlan 192
2024-08-06 03:48:16

Hi  @GrantD 

We can add the ETH ports into certain VLAN, but their egress rule is untagged and can't be changed to be tagged. This is the reason.

 

From the screenshot you provided, the ETH2 is in VLAN192, and the egress rule is untagged. With this configuration, only those clients which can deal with untagged packets can get internet access from this port, and the clients plugged into this port will be in VLAN192.

Wish you a happy life and smooth network usage!  >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#4
Options
Re:EAP615-WALL not passing 802.1q tagged traffic on port 1 to port 2 tagged with vlan 192
2024-08-06 04:31:57

  @Vincent-TP yes and that works fine.... 

 

The issue is that the TAGGED Frames from the workstation on port one are either not stripped of their 802.1q data and forwarded out port 2 OR the incomming untagged frames from port 2 are not tagged and forwarded out port 1

  0  
  0  
#5
Options
Re:EAP615-WALL not passing 802.1q tagged traffic on port 1 to port 2 tagged with vlan 192
2024-08-06 04:39:19

  @Vincent-TP The workstation is multhomed on several networks. 

 

 

  0  
  0  
#6
Options
Re:EAP615-WALL not passing 802.1q tagged traffic on port 1 to port 2 tagged with vlan 192
2024-08-06 05:56:46

Hi  @GrantD 

 

Please let me know your VLAN requirements for the workstation, and I will see if they can be achieved and how to do that.

Wish you a happy life and smooth network usage!  >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#7
Options
Re:EAP615-WALL not passing 802.1q tagged traffic on port 1 to port 2 tagged with vlan 192
2024-08-07 22:55:27

  @Vincent-TP 

 

Let me clarify the setup.. some things work and some things don't

 

I have a vlan aware device (my workstation) which tags 802.1q traffic inside the box (docker/virtualhost) for a number of subnets including it's vlan 192 as well as my managment vlan and several others. this is connected to port 1 of the 615-wall.. it works fine. it can connect to the gateways and the internet and so on for all the networks it's connected to.

 

I have a device that is a normal network device that doesn't know about vlans on port 2. port 2 is enabled in the omada controller and set to vlan 192. this device can connect to the gateway but cannot talk to my workstation.

 

This may be an implementation of private vlan within the 615-wall (if so how do I disable this)   or it may be a bug. (in which case please fix it.) 

 

Grant.

  0  
  0  
#8
Options
Re:EAP615-WALL not passing 802.1q tagged traffic on port 1 to port 2 tagged with vlan 192
2024-08-08 01:22:16

  @GrantD 

 

Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240816481, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!

Wish you a happy life and smooth network usage!  >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#9
Options

Information

Helpful: 0

Views: 567

Replies: 8

Tags

VLAN & Multi-Networks Network Connectivity
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.