Post #2204291
2026-03-24 11:19 UTC
@MrGamy@toot.kif.rocks @kidney@mastodon.online
Attempting a high level suggestion based on the information given: one of the wireguard endpoints will need to act as "server", presumably the double Nat + dyndns situation. Configure portforwardings for one UDP through both NATs to whatever is the final endpoint running wireguard behind the double NAT. (You may test this with netcat while wireguard is not running). The other end should then simply be able to use the dyndns and UDP port as target to connect to.
Replies (1)
-
@them@mastodon.fsinf.at 2026-03-24 11:22
@MrGamy@toot.kif.rocks @kidney@mastodon.online You need one device that is "publicly" reachable (in the above this is achieved by portforwardings through the NATs) for other wireguard clients to connect to. Be aware that depending on your ISP (internet Service Provider) you may not be able to do that (due to shared public IP, search for CGNAT (carrier grade NAT) for more info). Also consider that you may have only ipv4 or only ipv6 connection on either ends.