Updated EAP787 to latest v1.5.2, 6 GHz discovery takes ages
Updated EAP787 to latest v1.5.2, 6 GHz discovery takes ages
I've recently updated my EAP787 to latest v1.5.2.
The infamous "TP_TX_VAP" AP on 6 GHz band is now gone, but now, it takes ages for client devices to discover 6 GHz AP, often times never using 6 GHz until I initiate an explicit discovery.
I don't use MLO and I have 6 GHz to a separate SSID for stationary wireless clients.
I recall the "TP_TX_VAP" AP was specifically for making clients to discover 6 GHz properly. Is there a way to bring it back?
Am I the only one to encounter this issue?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @arter97
Thanks for posting here. To better understand the situation, please let us know the following info:
1. How long will the 6G SSID show up? above 10 seconds? Or even longer?
2. Did you test this with different clients? Do they all behave the same? Please also let us know the brand of the clients you are using.
3. If try to scan the 6G SSID with a wifi scanner, will it show up quicker?
Please also share a screenshot of the 6G SSID settings page.
- Copy Link
- Report Inappropriate Content
1. Yeah, often times more than 10s.
2. Yes, multiple clients. Windows 11 with AX211 on latest drivers, multiple Android phones with varying wireless generations.
3. Yes, that's what I meant by explicit discovery. It sometimes never show up before I initiate a scanning.
Attached the settings page.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @arter97
Thanks for the information.
Please change the following config and let us know the behavior:
1. Change the channel to a different one.
2. lower the channel width to 40MHz or 80MHz,
3. Change the Beacon Interval to 100 ms on Site settings.

We will also test it locally and keep you posted. Thanks.
- Copy Link
- Report Inappropriate Content
Hi @arter97
We have tested by creating a 6G-only SSID based on your configuration locally and also encountered slower SSID discovery.
After investigation, it was determined that this behavior is expected for the following reasons:
In Wi-Fi 6E/7 networks, if an SSID is configured with both 5GHz and 6GHz bands, the client can first connect quickly to the 5GHz network. Subsequently, the AP can “guide” the client to the 6GHz network—providing information such as the BSSID and channel for the 6GHz network under the same SSID—via Beacon or Probe Response frames that include Reduced Neighbor Report (RNR) information elements. This enables fast directed connection or roaming to the 6GHz band, a process known as RNR guidance or out-of-band discovery.
If the SSID is configured only on the 6GHz band, the client must perform a full scan of multiple PSC channels in the 6GHz band, significantly increasing discovery time and making fast roaming less efficient due to the lack of RNR guidance information from lower-frequency bands.
Therefore, to ensure the best user experience (including coverage, performance, and connection speed), it is strongly recommended to enable both 5GHz and 6GHz bands for the same SSID when deploying Wi-Fi 6E/7 networks, using 5GHz as an efficient discovery anchor for 6GHz.
- Copy Link
- Report Inappropriate Content
@Vincent-TP I understand the technical reason behind it but this is a regression nontheless.
My primary use-case of 6E/7 is for stationary devices. I don't want those clients to inadvertently use 5 GHz (which happened often hence a 6 GHz-only AP setup), and prior to v1.5, my 6 GHz-only AP was discovered almost instantly. I'm guessing the previous "TP_TX_VAP" worked as an effective workaround. I know many users asked for it to be removed, but I need something here to prevent the regression.
Also, I'm noticing a far less successful rate of 5 to 6 GHz roaming on my primary Android phone, which I'm feeling this is related.
Please reconsider.
- Copy Link
- Report Inappropriate Content
I would like tp tx vap ssid gone, not important to my case, by a possible slower discovery time on 6 Ghz. TP-Link, please consider removal of that tp tx vap, appreciated.
- Copy Link
- Report Inappropriate Content
Hi @arter97
Thanks for the reply.
Did you try the suggestions below:

Especially point 3, we found that it helps a lot. Please try and let us know the results.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Vincent-TP Hi Vincent,
I've been trying it out your suggestion, specifically 3 only as the rest would affect performance.
I think it's too early to conclude and unstatistically based on feeling, I feel like it's still worse than the old v1.1.x branch but it's indeed noticeably better.
Let me run it for a few more days and report back.
Thanks for the suggestion.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 409
Replies: 13
Voters 0
No one has voted for it yet.
