EAP655-WALL_V1_1.2.0_Build 20230717 (Beta)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Does this Beta firmware resolved the issue of VLAN tags not being handled correctly on another access point particularly EAP225-Outdoor Hardware Version 3.0 connected on Ethernet 3 (PoE enabled)?
All SSIDs we are using are assigned with different VLAN IDs. VLANs are handled correctly on EAP655-Wall but not on EAP225-Otdoor.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello @CarloPH,
After confirming with the Support Engineer, the VLAN Bug fixed hasn't been added in this 1.2.0 Beta firmware, I have reported it to them for attention.
It will be added in the further software iterations, thanks for your valuable feedback.
- Copy Link
- Report Inappropriate Content
I have had zero issues with multiple VLANs (one per SSID) running on EAP225-outdoorunits since firmware version 5.0.5 (currently I'm on 5.0.9). Suspect the issue is more the configuration of the ethernet switch port to which the EAP225 is connected perhaps?
- Copy Link
- Report Inappropriate Content
@d0ugmac1, I'm sorry if I've been vague in stating my problem. I also failed to mention that this is under Omada Controller and here is how it is connected:
Router > PoE Switch > EAP655-Wall (Ethe3 PoE enabled) > EAP225-Outdoor
No issues on VLANs when both EAP are plugged directly on the Trunk Ports of PoE Switch. However when EAP225-Outdoor is cascaded from the Eth3 of EAP655-Wall it cannot get an IP address on SSIDs with VLAN tags. There is a known issue about this here...
https://community.tp-link.com/en/business/forum/topic/605508
But the firmware version there is lower than the preloaded firmware of the EAP655-Wall (1.0.0-Beta versus 1.0.2). This is the reason why I was hoping this 1.2.0 Beta version also resolves the VLAN tagging issue.
d0ugmac1 wrote
I have had zero issues with multiple VLANs (one per SSID) running on EAP225-outdoorunits since firmware version 5.0.5 (currently I'm on 5.0.9). Suspect the issue is more the configuration of the ethernet switch port to which the EAP225 is connected perhaps?
- Copy Link
- Report Inappropriate Content
Hello @CarloPH,
After confirming with the Support Engineer, the VLAN Bug fixed hasn't been added in this 1.2.0 Beta firmware, I have reported it to them for attention.
It will be added in the further software iterations, thanks for your valuable feedback.
- Copy Link
- Report Inappropriate Content
@Hank21, Thanks for the info.
Btw, I've tried the Beta Version 1.0.0 and it does fixed the VLAN tagging issues.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 581
Replies: 4
Voters 0
No one has voted for it yet.