Updated as of Jan 30th 2023:

 

The official firmware has been released to fix the issue mentioned in this post.

Please follow the direct download link below for manual upgrade, or visit TP-Link regional official website for updates.

 

EAP615-Wall(EU/US)_V1_1.1.3 Build 20220921   Release Note >

 

Notes:

(1) The above firmware is applied to EAP615-Wall v1/v1.80/v1.60.

(2) The above firmware can be installed on the EU version and US version.

 

Any further issues, please don't hesitate to Start a New Thread from HERE. 

To get better assistance from Community, you may check Tips For Efficiently Reporting an Issue In The Community.

 

Thank you for your attention. See you in the forums soon!

 

 

This Article Applies to:

 

EAP615-Wall v1

 

Background:

 

Omada Wall Plate AP such as EAP615-Wall has 4 Gigabit Ethernet ports (1× uplink + 3× downlink), with one downlink port (ETH3) supporting PoE pass-through to provide power for wired device. The Wall AP supports configuring Access VLAN for the 3 downlink ETH ports. With ETH VLAN disabled, all the 3 downlink ports can pass through all tagged Ethernet traffic.

 

 

 

Issue Description/Phenomenon:

 

Recently we received feedback on the EAP615-Wall that tagging the ETH port may stop other tagged VLANs from passing through. Here are the case details.

 

Topology & Setup:

Internet --- Router ---(Port1) PoE Switch (Port2) --- EAP615-Wall (ETH1-3, no VLAN) --- 2nd EAP & PCs

 

VLAN10 (SSID1): 192.168.10.x/24

VLAN20 (SSID2): 192.168.20.x/24

VLAN30 (SSID3): 192.168.30.x/24

Switch Port1/ Port2 are tagged with VLAN10/20/30

EAPs are configured with SSID1(VLAN10), SSID2(VLAN20), SSID3(Dynamic VLAN)

 

With the above setup, everything works well.

• Wireless users connected to SSID3(Dynamic VLAN) can obtain IP addresses from the expected VLAN (VLAN10/20/30).

• All wireless clients connected to the 2nd EAP can obtain the correct IP addresses from SSID1(VLAN10)/ SSID2(VLAN20).

 

Problem:

After configuring the EAP615-Wall with a VLAN such as ETH1 VLAN30, things stopped working as expected.

• When the wireless users connect to SSID3(Dynamic VLAN), only the users belonging to VLAN30 can obtain IP addresses.

• All wireless clients connected to the 2nd EAP will fail to obtain an IP address from SSID1(VLAN10)/ SSID2(VLAN20).

 

Related Threads:

Re:EAP615-Wall tagging single port doesn't allow tagged traffic anymore on other unassigned ports

 

Available Solutions:

 

The issue has been located and TP-Link has released the official firmware to resolve the issue.

 

EAP615-Wall(EU/US)_V1_1.1.3 Build 20220921   Release Note >

 

Notes:

(1) The above firmware is applied to EAP615-Wall v1/v1.80/v1.60.

(2) The above firmware can be installed on the EU version and US version.

 

If you are looking for a quick solution, you may install the Beta firmware below to fix the issue temporarily.

 

EAP615-Wall_v1_1.0.0_Build20220801(Beta)

Note: Please be sure you have read the Beta Test Agreement before proceeding!

 

IMPORTANT NOTICE: To fix the issue, please don't use VLAN 4094 with the Beta firmware above.

 

Thank you for your attention!

 

Feedback:
 

If this was helpful, welcome to give us Kudos by clicking the upward triangle below.

If there is anything unclear in this solution post, please feel free to comment below.

 

Thank you in advance for your valued feedback!