0
Votes

No FQDN support as Endpoint for Wireguard (in Standalone mode)

  This repeated request has been merged into the main thread Wireguard Peers: Endpoint with domain names. Please vote on the main thread.

 
0
Votes

No FQDN support as Endpoint for Wireguard (in Standalone mode)

  This repeated request has been merged into the main thread Wireguard Peers: Endpoint with domain names. Please vote on the main thread.
No FQDN support as Endpoint for Wireguard (in Standalone mode)
No FQDN support as Endpoint for Wireguard (in Standalone mode)
Yesterday - last edited Yesterday
Tags: #Suggestion
Model: ER707-M2  
Hardware Version: V1
Firmware Version: 1.2.4 Build 20241031 Rel.78300

At the start that is the hardware version, not sure which one is correct to select:

I wanted to connect my "external" network with my TP Link ER707-M2 at home, but I encountered an issue, since here in Germany we only get changing iPv4 Addresses by tht Telekom, I have to add the FQDN address.
My router here is the TP Link ER707-M2 and the "external" router is the FritzBox 7590, both have a DDNS address and the VPN works as long as the FritzBox gets a new iPv4 address, then the connection to the TP-Link router in standalone mode will fail because it only supports IP addresses with the newest beta firmware and that is changing unfortunately, not any kind of FQDN address.

This is not my private FQDN for the FritzBox "XXXX" is just a placeholder

I researched a bit in the internet and found a forum post saying " It has been projected. This feature has been scheduled on Omada Controller V5.15.X and adapted firmware. See the other accepted label." (tp-link forum)

Not sure if it means it also gets automatically adotped to the standalone interface but it would be very very useful to have it, since otherwise only incoming connection like e.g. from my iPhone are possible.

If that would be fixed then the router is perfect for me and what I found when I searched for it for a few other people as well.
Thanks

Julian

#1
Options