wgsd VS WirtBot

if your looking at setting up coredns aswell then i would highly suggest checking out wgsd https://github.com/jwhited/wgsd

https://github.com/jwhited/wgsd does NAT traversal with Wireguard, but you need to operate a CoreDNS server to do it.

More info on how it works: https://www.jordanwhited.com/posts/wireguard-endpoint-discov...

Another one which looks promising is wgsd, a dns like plugin to discover peer's endpoints that sit behind a NAT. For me this is part of the solution, however not a complete one, as my client devices are also on Android and Android TV.

that guide is literally someone promoting their CoreDNS plugin, so I'm confused as to what you mean: https://github.com/jwhited/wgsd

If they are behind a NAT that you can't do port-forwarding on then you may need to run some additional software like https://github.com/jwhited/wgsd so 10.10.0.2 and 10.10.0.3 know where to look for each other by asking 10.10.0.1

Our current implementation just has the nodes configured with PersistentKeepAlive by default, which works well enough for our small setup. In future iterations our plan is to incorporate another service. Our inclination is to use WGSD: https://github.com/jwhited/wgsd

I have built https://b-m-f.github.io/WirtBot/ for this use case.

I wrote and maintain https://github.com/b-m-f/WirtBot .

Personally I use this together with https://github.com/b-m-f/WirtBot/ for keeping everything maintained, but `wg-pod` works with any `wg-quick` compatible config.

As for now, i am confused with this software. I'm glad I'm not the only one. ))) https://github.com/b-m-f/WirtBot/issues/112

its been almost a year since I first started working on WirtBot.

I have also built https://github.com/b-m-f/WirtBot to make the setup even easier. But this will introduce a third Node that is purely routing traffic, which might be overkill depending on your technical expertise.