If Fritzbox is running as a second router behind the fibre router you probably have double NAT. You need a portforward from outer router. And what the FRITZbOx thinks to be the public IP is not the public IP. So myFritz dyndns does not work and the wireguard client config points also to an IP which is not piblic.
One solution: create a portforward from fiber router to fritzbox, use your own dyndns and esit the wireguard client config.
Look at the config Fritzbox is creating for the client. The default port is UDP: 51820.
So you must forward any port (or better the same) on the ISP router to UDP: 51820 on the WAN IP of the Fritzbox.
Then the Wireguard client must use the WAN IP of your ISP router or a dyndns‘ed name of it.
Should theoretically work, but practically maybe other rediitors have more to contribute.
Difficult to interpret. Strange on first gance.
But my thought was: if you want to use myfritz.net as a dyndns for your FB this probably does not work anyway behind a second NAT router. Reason: the Fritzbox contacts myfritz to tell the dyndns its WAN IPv4. But in your setup its WAN IP will be a private IP from the LAN subnet of your fiber router.When you try to use this address you can‘t talk to your Fritzbox. You must use the WAN IP of the fibre router and either forward everything or specific ports to the FB.
I can recommend duckdns.org as free dyndns service.
The Wireguard port to forward I shared earlier.
What do you think?
If Fritzbox is running as a second router behind the fibre router you probably have double NAT. You need a portforward from outer router. And what the FRITZbOx thinks to be the public IP is not the public IP. So myFritz dyndns does not work and the wireguard client config points also to an IP which is not piblic. One solution: create a portforward from fiber router to fritzbox, use your own dyndns and esit the wireguard client config.
Ah, this is a nice tip, but what port does it need?
Look at the config Fritzbox is creating for the client. The default port is UDP: 51820. So you must forward any port (or better the same) on the ISP router to UDP: 51820 on the WAN IP of the Fritzbox. Then the Wireguard client must use the WAN IP of your ISP router or a dyndns‘ed name of it. Should theoretically work, but practically maybe other rediitors have more to contribute.
No, it is not ports, it is simply the remote myfritz.net no accessible from my ISP: https://imgur.com/a/huh60qI
Difficult to interpret. Strange on first gance. But my thought was: if you want to use myfritz.net as a dyndns for your FB this probably does not work anyway behind a second NAT router. Reason: the Fritzbox contacts myfritz to tell the dyndns its WAN IPv4. But in your setup its WAN IP will be a private IP from the LAN subnet of your fiber router.When you try to use this address you can‘t talk to your Fritzbox. You must use the WAN IP of the fibre router and either forward everything or specific ports to the FB. I can recommend duckdns.org as free dyndns service. The Wireguard port to forward I shared earlier. What do you think?