Solution TCP Connections May Fail Between Different VLANs On The Same EAP650/ EAP670/ EAP653 [Case Closed]
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
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.
EAP653(EU/US)_V1_1.0.4 Build 20220921 Full Release Note >
EAP650(EU/US)_V1_1.0.6 Build 20220921 Full Release Note >
EAP670(EU/US)_V1_1.0.6 Build 20220921 Full Release Note >
Notes:
(1) The above firmware is applied to v1/v1.20/v1.26.
(2) The above firmware can be installed on the EU version and US version.
(3) The release notes above didn't mention it has fixed the TCP connection issue but the above firmware does have fixed it.
If you still have the TCP connection failure issue, it might be a different case, 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:
EAP650 v1/ v1.20/ v1.26
EAP670 v1/ v1.20/ v1.26
EAP653 v1/ v1.6
Issue Description/Phenomenon:
Recently we received feedback that TCP connections (such as Remote Desktop) failed between clients connected to different VLAN SSIDs on the same EAP650/ EAP670/ EAP653. Here is the case details.
Topology & Setup:
Internet --- Router --- EAP650 SSID1 & SSID2 ))) ((( PC1 & PC2
VLAN1 (SSID1): 192.168.1.x/24
VLAN3 (SSID3): 192.168.3.x/24
Problem:
-
When the PC1 & PC2 are connected to the different SSIDs respectively, TCP connections (such as remote desktop) are broken between the two for anything beyond a simple network ping, i.e., the client on VLAN1 can ping the client on VLAN3 but the attempt to open a remote desktop connection ends up a failure.
-
When two PCs are each connected to the same VLAN SSID, the Remote Desktop connection works as expected.
Related Threads:
Issues with tcp connections between VLANs on the same AP
Available Solutions:
The issue has been located and TP-Link has released the official firmware to resolve the issue.
EAP653(EU/US)_V1_1.0.4 Build 20220921 Full Release Note >
EAP650(EU/US)_V1_1.0.6 Build 20220921 Full Release Note >
EAP670(EU/US)_V1_1.0.6 Build 20220921 Full Release Note >
Notes:
(1) The above firmware is applied to v1/v1.20/v1.26.
(2) The above firmware can be installed on the EU version and US version.
(3) The release notes above didn't mention it has fixed the TCP connection issue but the above firmware does have fixed it.
If you are looking for a quick solution, you may install the Beta firmware below to fix the issue temporarily.
Note: Please be sure you have read the Beta Test Agreement before proceeding!
For EAP650 v1/ v1.20/ v1.26:
EAP650_v1_1.0.0_Build20220804(Beta)
For EAP653 v1/ v1.6:
EAP653_v1_1.0.0_Build20220804(Beta)
For EAP670 v1/ v1.20/ v1.26:
EAP670_v1_1.0.0_Build20220804(Beta)
Note: the above Beta firmware has added the PPSK support.
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!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
It is an absurdity for a company like TP-Link to treat customers, who really spend a lot of money on hardware, like this and leave them out in the cold!
They act as if they could and can do business. But honestly, they really are not currently!
And the only remedy left for us as paying customers is to complain and ask again and again.
If there's a timeline or any definite statements on the subject from TP-Link, then I'll be quiet - I promise. But not like this!
- Copy Link
- Report Inappropriate Content
Crusoe wrote
@Spryde Any update on when you'll ask for another update?
Yes, it's very disappointing and tarnishing this bug hasn't been addressed, you've aired that grievance and I share it. But only thing to do now is wait for the release. I subscribe to this thread so that I know as soon as the release is issued. All the notifications of people asking for updates are unnecessary. Fae is active, so they'll respond when there's an update, which means the answer to your question is no, there are not any updates. I don't see the value in Fae replying replying "No, there are no updates" every time you ask as it just sends further unnecessary notifications and wastes everyone's time. as no new information is relayed.
@Fae Could we consider locking this thread?
Well, @Christian2705 posted a new thread regarding this and @Fae replied to it. So it's as if he has this thread set to ignore (if that's even an option). He said he'd check with R&D to see if they could speed it up...lol. No need to lock threads. And thanks to @Christian2705 .
https://community.tp-link.com/en/business/forum/topic/589094
- Copy Link
- Report Inappropriate Content
Hi,
first of all thanks to @Christian2705 for his efforts.
I made my decision. If TP-Link will not bring final Firmware by end of the year, I will sell all my TP-Link stuff and in our company, we will not be buying any more TP-Link products in the near future.
You feel like you're just a perpetual beta tester for TP-Link.
The R&D team seems to be much too small and instead of fixing problems, new devices and versions are always brought to the market, instead of providing the products on the market (which are all not cheap) with stable firmware.
This is really a pity, because I actually like the Omada approach very much.
But how should one please work sensibly with the devices?!
And to be a beta tester forever is unfortunately also not possible, because our company policies do not allow that (because of the separate privacy policy and data transfer to TP-Link).
- Copy Link
- Report Inappropriate Content
To anyone considering using this beta firmware, just a warning that I've found a bug when trying to use it with a EAP650 connected to a Cisco CBS250-8FP-E-2G POE switch. Before the upgrade to the beta the AP works as expected powered by the Cisco switch, however after upgrading to this beta firmware the AP starts missing heartbeats and goes into a permanent reboot cycle.
If I then connect the same AP to a TL-SG2210MP TP-Link POE switch the AP works fine using the beta.
So be careful and run some tests if you plan to use this with none TP-Link POE switches.
- Copy Link
- Report Inappropriate Content
@Dsinc I don't think, TP Link will ever fix those issues.
best advice at the moment: take UniFi or any other hardware until TP-Link gets its stuff running.
- Copy Link
- Report Inappropriate Content
Received a firmware update in Omada yesterday for my EAP650 to version 1.0.6 that solves this issue. I'm in the US.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi Fae, Hi All.
Any update on this issue? As far as I understand and check, v1.0.6 AND acutal beta do not solve those ongoing fails/bugs of your Access Points.
My APs are now around a 3/4 year old and never worked, as they should work.
This cannot be the case, that you just don't fix those huge issues with your APs.
Please give us a definitve timeline, when those issues will be fixed.
- Copy Link
- Report Inappropriate Content
the fact that they won't respond to this thread at all anymore, even to acknowledge it is pretty disgraceful. If this is the level of support the products receive I am going to have to stop investing in the Omada ecosystem
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 6
Views: 10699
Replies: 32
Voters 2
