Wireguard Endpoint FQDN and Routing
It's been over a year since this post https://community.tp-link.com/en/business/forum/topic/621338 (not mine), and we're still in the same situation. A lot of users rely on dynamic IPs because they're scarce. Without the ability to use FQDN on the endpoint, this makes the TP-Link router obsolete.
Please tp-link, help us..
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @rfl-floripa
Thanks for posting in our business forum.
You don't have to tag me. I will reply if necessary. Or I will proactively update the thread of the feature request if necessary. Subscribe to the major discussion thread for notice.
We are aware of the request and on the feature request page, both OVPN and WG have been marked and provided with the adaptation schedule. Stay tuned for the releases.
Omada routers, adding OpenVPN servers by its hostname is impossible, only accept IPs.
Make the wireguard peer generator more friendly (QR codes, exports and autogenerating codes)
- Copy Link
- Report Inappropriate Content
Hi @rfl-floripa
Thanks for posting in our business forum.
You don't have to tag me. I will reply if necessary. Or I will proactively update the thread of the feature request if necessary. Subscribe to the major discussion thread for notice.
We are aware of the request and on the feature request page, both OVPN and WG have been marked and provided with the adaptation schedule. Stay tuned for the releases.
Omada routers, adding OpenVPN servers by its hostname is impossible, only accept IPs.
Make the wireguard peer generator more friendly (QR codes, exports and autogenerating codes)
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 37
Replies: 1
Voters 0
No one has voted for it yet.