EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on May 6th, 2024)- [Thread Closed]

EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on May 6th, 2024)- [Thread Closed]

275 Reply
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Jan 4th, 2024)
2024-01-16 02:25:47

Hi @Dilly

 

Thanks for your valuable feedback, and here is the link you mentioned.

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#257
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Jan 4th, 2024)
2024-01-16 03:31:37

  @Hank21 

 

Ohhhhh! Nice!
Thanks very much.

 

  1  
  1  
#258
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Nov 24th, 2023)
2024-01-20 18:36:28 - last edited 2024-01-20 18:46:26

Hi  @Hank21 ,

 

thanks for your support and sorry for answering late. With the update of the firmware, at least sometimes the IPv6 traffic was possible, but sometimes not.

 

In the meantime, after trying several setups, settings, devices, and so on, I finally can reproduce the error exactly with both of the access points EAP650-Wall and EAP650-Wall:

Here is the summary:

 

 

Setup:

  • Access points are connected to switch TL-SG2016P on port 1 (EAP-655-Wall) and port 2 (EAP650-Wall)
  • EAP655-Wall: Firmware 1.2.4 Build 20231208 Rel. 73353(4555)
  • EAP650-Wall: Firmware 1.1.4 Build 20231208 Rel. 66358(4555)
  • (only) one SSID is configured per access point:
    SSID with VLAN ID 10 on EAP-655-Wall
    SSID with VLAN ID 20 on EAP-650-Wall
  • in a first step, the ports on the switch are configured as following:
    • port (port 1 on the switch) of EAP655-Wall is a tagged port of VLAN 10, port of EAP650-Wall is not part of VLAN 10
    • port (port 2 on the switch) of EAP-650-Wall is a tagged port of VLAN 20, port of EAP655-Wall is not part of VLAN 20
    • one port on the switch (11) is configured as untagged in VLAN 10 (running gateway1/DHCP on this port)
    • another port on the switch (12) is configured as untagged in VLAN 20 (running another gateway2/DHCP on this port)
  • summary of VLANs: there are two VLAN running in parallel but not on the same ports, as AP and gateway are in separated VLANs with no overlap:
    • VLAN ID 10: tagged (1) AP, untagged (11) gateway1
    • VLAN ID 20: tagged (2) AP, untagged (12) gateway 2

 

Reproducible error:

  • As soon as I add one of the ports of the access points to the other VLAN by configuring it as a tagged port (for a potential other SSID with another VLAN ID), I got these strange IPv6 errors, where a valid access is not possible anymore (tested with site https://test-ipv6.com/index.html.en_US)
    Example: adding port (1) as a tagged port of VLAN ID 20 leads to the IPv6 error

 

Goal for the final setup:

  • My final setup of the access points VLAN setup would be:
    • having two SSIDs running on the access points with two different VLAN IDs (10 & 20)
    • having this acces point on the switch with a tagged port of VLAN ID 10 and a tagged port of VLAN ID 20 configured
    • one SSID should use the gateway1 (over VLAN 10) and the other SSID should use the other gateway2 (over VLAN ID 20)

 

Problem:

  • With the current limitation, that one of the access points (EAP650-Wall or EAP655-Wall) couldn't be part of two VLANs by a tagged port in both VLANs, the mentioned solution wouldn't be possible at all.

 

Do you have any further advice or an estimation of when this bug would be fixed in the firmware? I'm currently setting up the infrastructure with several access points and switches of this type but with this limitation, an implementation as expected wouldn't be possible at all, so I'm currently waiting with ordering the complete set of devices.

Thanks in advance!

  0  
  0  
#259
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Nov 24th, 2023)
2024-01-22 02:16:08

Hi @Jay_3_14

 

Jay_3_14 wrote

Reproducible error:

  • As soon as I add one of the ports of the access points to the other VLAN by configuring it as a tagged port (for a potential other SSID with another VLAN ID), I got these strange IPv6 errors, where a valid access is not possible anymore (tested with site https://test-ipv6.com/index.html.en_US)
    Example: adding port (1) as a tagged port of VLAN ID 20 leads to the IPv6 error

 

May I confirm whether the IPv4 is working properly in this scenario?

 

"As soon as I add one of the ports of the access points to the other VLAN by configuring it as a tagged port"

Do you mean set the ETH Vlan ID like the below image on the EAPs but it will cause the current issue?

 

What is the firmware version of your Controller?

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#260
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Nov 24th, 2023)
2024-01-22 06:53:57

Hi @Hank21,

 

I'm sorry, my description was a little bit misleading perhaps...

The Eth-Ports on the access points I'm not using at all, only the one on the background to connect the AP to the switch (TL-SG2016P).

On this switch, I had the AP as (tagged) port of one VLAN ID (10) only first and everything went well with IPv6. When adding the port on the switch to another VLAN ID (20), I got these troubles with IPv6, and only with IPv6. IPv4 works well without any problems.

As a workaround, I turned of the Router Advertisement on the Router to avoid having IPv6 in my local network. By this, all timeouts on the wifi clients are gone but the price is not having IPv6 anymore. I assume that as soon as the access point is part in multiple VLANs (by tagged connection/port on the switch), something went wrong with multicast/RA messages to the access point, could that be?

  0  
  0  
#261
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Nov 24th, 2023)
2024-01-23 03:54:36

  @Jay_3_14 

 

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 TKID240145443, 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!

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#262
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Aug 2nd, 2023)
2024-01-24 02:06:02

  @gregg098 

  0  
  0  
#263
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Jan 4th, 2024)
2024-01-25 01:51:58
I have Controller 5.12.23 through Docker and EAP655 with 1.2.3 firmware (updated through custom firmware). The controller is not finding the new version 1.2.6. What should I do?
  0  
  0  
#264
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Jan 4th, 2024)
2024-01-25 12:47:49

  @PasLu 

 

I had to grab it from here. I thinks it's because it's not release for your region.

https://www.tp-link.com/en/support/download/eap655-wall/#Firmware

  0  
  0  
#265
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Jan 4th, 2024)
2024-01-25 13:37:54

  @BoboXX 

 

that was the case! Thank you. I'm not sure why the Canadian website doesn't have the firmwares but US does...

 

thanks again! 

  0  
  0  
#266
Options