Solution Solution to EAP650/EAP655-Wall, EAP225/EAP235-Wall - ETH VLAN Related Issues [Apr 24, 2023 Updated]
This Article Applies to: EAP650-Wall v1, EAP655-Wall v1, EAP225-Wall v2, EAP235-Wall v1
Update as of Apr 12th, 24th 2023:
Add the Beta firmware for EAP225-Wall v2 and EAP235-Wall, which has fixed the ETH VLAN issue described in this thread.
EAP225-Wall(EU&US)_v2_1.0.0_Build 20221229 (Beta)
EAP235-Wall(EU&US)_v1_3.1.99_Build 20221221 (Beta)
EAP235-Wall(CA)_v1_3.1.99_Build 20230424 (Beta)
Note: Please check the device label to verify the country code of your device first, then choose the correct file to download and install.
Beta Release Notes:
1. Fixed the ETH VLAN issue described in this thread based on the current official firmware EAP225-Wall_V2_5.0.3 Build 20210604, EAP235-Wall_V1_3.1.0_Build 20210721.
2. The above firmware is applied to EAP225-Wall(EU&US) v2, EAP235-Wall(EU&US) v1, EAP235-Wall(CA) v1.
3. Please be sure you have read the Beta Test Agreement before proceeding!
Issue Description/Phenomenon:
Recently we received feedback that EAP655-Wall | EAP650-Wall connected in series via ETH3 port may cause tagged VLAN failed to be transparently transmitted. Here are the case details.
Topology & Setup:
Internet --- Router ---PoE Switch --- AP1, EAP655-Wall (ETH1-3, no VLAN) --->PoE output>--- AP2, EAP650-Wall
EAPs are configured with SSID1(no VLAN), SSID2(no VLAN), and SSID3(VLAN10)
Problem:
- With the above setup, clients failed to receive an IP address in SSID3 on AP2, while clients connected to other SSIDs on AP2 works fine, and all the three SSIDs on AP1 works fine.
- If setting a VLAN on the ETH3 port, none of the SSIDs work any more, clients no longer receive an IP address.
Related Threads:
Clients on Second Access Point don't get an IP adress with tagged SSID
Available Solutions:
The issue will be fixed in the subsequent official firmware soon.
Before the new firmware is released to fix the issue, you may upgrade the following Beta firmware to fix the issue temporarily.
Beta Firmware Download:
EAP650-Wall(EU&US)_V1_1.0.3 Build 20230407 (Beta)
EAP655-Wall(EU&US)_V1_1.0.0 Build 20230330 (Beta)
Beta Release Notes:
1. Fixed the casting or streaming issue for EAP655-Wall mentioned in the solution post 604118.
2. Fixed the tagged ETH VLAN issue described in this thread based on firmware EAP650-Wall_V1_1.0.1 Build 20220627, EAP655-Wall_v1_1.0.0 Build 20220719.
3. The above firmware is applied to EAP650-Wall(EU&US) v1, EAP655-Wall(EU&US) v1/v1.60.
4. 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.
Update as of Apr 12th 2023:
Add the Beta firmware for EAP225-Wall v2 and EAP235-Wall, which has fixed the ETH VLAN issue described in this thread.
EAP225-Wall(EU&US)_v2_1.0.0_Build 20221229 (Beta)
EAP235-Wall(EU&US)_v1_3.1.99_Build 20221221 (Beta)
Beta Release Notes:
1. Fixed the ETH VLAN issue described in this thread based on the current official firmware EAP225-Wall_V2_5.0.3 Build 20210604, EAP235-Wall_V1_3.1.0_Build 20210721.
2. The above firmware is applied to EAP225-Wall(EU&US) v2, EAP235-Wall(EU&US) v1.
3. 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.
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.
To submit a new different issue, please Start a New Thread for better assistance.
Thank you for your support and contribution in TP-Link Community!
Hi, I tried several times to download the file from the forum post, unpack on a Mac (native and KeKa) and a Win10 PC (7z). Same failed result each time, "Invalid File"
Hi @Fae, last week I upgraded my five EAP225-Wall access points from the official firmware 'EAP225-Wall(EU)_V2_5.0.3 Build 20210604' to the beta firmware 'EAP225-WALLv2_1.0.0_20221229 (beta)'.
Every week the Automatic Upgrade Schedule checks if upgrades are available and installs them. Last night the upgrade (or rather downgrade) to the official firmware 'EAP225-Wall(EU)_V2_5.0.3 Build 20210604' was performed, assuming that this was done because the version number of the beta firmware is v1.0.0 and the version number of the official firmware is v5.0.3, which is higher.
Why does the official version have version v5.0.3 and the beta version have version v1.0.0 and not v5.0.4, which would have avoided the downgrade?