EAP225 Bug in Version 2.6.1 Build 20191022 Rel. 42463

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

EAP225 Bug in Version 2.6.1 Build 20191022 Rel. 42463

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
EAP225 Bug in Version 2.6.1 Build 20191022 Rel. 42463
EAP225 Bug in Version 2.6.1 Build 20191022 Rel. 42463
2020-01-23 18:00:24
Model: EAP225  
Hardware Version: V3
Firmware Version: 2.6.1

There is a bug in this relase and VLANs do not work. Clients will just not get an address from DHCP (the EAP225 gets address for himself without a problem).

 

It is definitely a problem of the software because I have just unboxed another EAP225, but with version 2.4.0 Build 20181121 Rel. 55897 and it works.

 

Also this one worked before the update.

 

TP-Link, please fix this ASAP.

  0      
  0      
#1
Options
23 Reply
Re:EAP225 Bug in Version 2.6.1 Build 20191022 Rel. 42463
2020-01-23 20:22:47 - last edited 2020-01-23 20:25:03

 

RoRo7 wrote

There is a bug in this relase and VLANs do not work. Clients will just not get an address from DHCP (the EAP225 gets address for himself without a problem).

 

It is definitely a problem of the software because I have just unboxed another EAP225, but with version 2.4.0 Build 20181121 Rel. 55897 and it works.

 

EAP225 firmware version 2.4.0 had a bug which was fixed in version 2.6.0. This is from the release notes:

 

2. Fixed the bug that untag packets can be transferred to SSIDs with different VLANs.

 

If your network does rely on untagged traffic to offer IP addresses using DHCP for different VLANs, it definitely has a wrong setup.

 

With a correct setup the bug fix in v2.6.0 does not change the behavior of working VLANs, no matter whether you use v2.4.0, v2.6.0 or v2.6.1 firmware. I didn't notice any problem in our VLAN setups for EAP225 when upgrading to v2.6.0 and v2.6.1.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  1  
  1  
#2
Options
Re:EAP225 Bug in Version 2.6.1 Build 20191022 Rel. 42463
2020-01-24 07:35:26

@R1D2 That would be strange, because I have the following APs working without problem.

 

EAP110 versions

 

3.3.0 Build 20190301 Rel. 39365

3.4.0 Build 20191014 Rel. 37239

 

EAP115

 

3.2.0 Build 20181211 Rel. 51136

 

EAP225

 

2.4.0 Build 20181121 Rel. 5589

 

The only EAP that has problems is the one I updated to 2.6.1.

 

Could it be that my network setup is wrong, but in this case - all the mentioned versions have still the bug you mention ? Then this is an unfixed problem in the complete range ?

 

2. Fixed the bug that untag packets can be transferred to SSIDs with different VLANs.

  0  
  0  
#3
Options
Re:EAP225 Bug in Version 2.6.1 Build 20191022 Rel. 42463
2020-01-24 09:04:49 - last edited 2020-01-24 09:05:31

@shberge Does not seem a solution for me, I need this separation - this is the reason I implement a "business" solution.

  0  
  0  
#5
Options
Re:EAP225 Bug in Version 2.6.1 Build 20191022 Rel. 42463
2020-01-24 10:12:30 - last edited 2020-01-24 10:39:30

 

RoRo7 wrote

@shberge Does not seem a solution for me, I need this separation - this is the reason I implement a "business" solution.

 

If you use VLANs for separation, you also need to separate broadcast domains – each VLAN carries an own network, isolated against each other. Please post a diagram or the setup for your network including VLANs and IP address blocks.

 

For example, this is the typical VLAN setup we use on several sites. This works with EAP110, EAP220 and EAP225:

 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#6
Options
Re:EAP225 Bug in Version 2.6.1 Build 20191022 Rel. 42463
2020-01-24 18:41:44
This looks almost 1:1 with the client setup (no management VLAN). However, EAP225, ver. 2.6.1 is the only one that doesn't work (I connect all of them to same port for the test). EAP225 with ver 2.4.0 works on the same port.
  0  
  0  
#7
Options
Re:EAP225 Bug in Version 2.6.1 Build 20191022 Rel. 42463
2020-01-25 11:55:25

@RoRo7, if you want me to help you, please post your setup.

 

What IPs do you use, how are switch settings, which PVIDs are set, which VLAN IDs are assigned to the SSIDs, what networks are defined on the router, where are the VLANs terminated, does the router assign VLAN IDs to its traffic etc.

 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#8
Options
Re:EAP225 Bug in Version 2.6.1 Build 20191022 Rel. 42463
2020-01-26 18:05:29

@R1D2 I would not post the end client setup without his permission. But on the other side, I am not willing to explain him, that he needs redesign of the network - because a single version of TP-Link EAP225 does not work.

 

It will not look good neither for the solution I proposed, neither to the vendor I have chosen.

 

EAP225 v. 2.6.1 goes to the drawer, until another release, working one is silently released. I cannot accept all the other versions are working, and the problem is on our side. It will mean for me, that all the other AP-s need fixing.

 

  0  
  0  
#9
Options
Re:EAP225 Bug in Version 2.6.1 Build 20191022 Rel. 42463
2020-01-29 19:38:50

@RoRo7 @R1D2   I am seeing the same behavior when upgrading to 2.6.1.  I run two EAP225v3 broadcasting two SSIDs and rely upon the EAP225v3 to tag the traffic for two VLANs.  All prior firmware versions up to 2.5.0 worked flawlessly.  Both versions 2.6.0 and 2.6.1 immediately caused all traffic to no longer pass upon upgrade.  

  1  
  1  
#13
Options
Re:EAP225 Bug in Version 2.6.1 Build 20191022 Rel. 42463
2020-01-29 21:20:43

@TFTCM, do you use an asymmetric VLAN setup? Asymmetric VLANs are not possible with Multi-SSID VLANs.

 

Please post your setup.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#14
Options
Re:EAP225 Bug in Version 2.6.1 Build 20191022 Rel. 42463
2020-01-29 21:31:54

@R1D2 Ah, there is someone else with the same problem. Specific to single AP version (ok two versions). No assymetric VLANs here. If you are a TP-Link employee, then check what is wrong with those two specific versions. Why deny there is a problem ?

  0  
  0  
#15
Options