wgsd VS cjdns

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

This sub is not about TOR and all the seediness that goes on there but rather about creating darknets, by which we/they mean mesh networks and encrypted networks using tools like https://github.com/cjdelisle/cjdns/

One of my favorite projects in IPv6 space is the CJDNS project: LINK TO GITHUB

From a purely networking perspective, there are far better solutions than tailscale.

Have a look at full mesh VPNs like:

https://github.com/cjdelisle/cjdns

https://github.com/yggdrasil-network/yggdrasil-go

https://github.com/gsliepen/tinc

https://github.com/costela/wesher

These build actual mesh networks where every node is equal and can serve as a router for other nodes to resolve difficult network topologies (where some nodes might not be connected to the internet, but do have connections to other nodes with an internet connection).

Sending data through multiple routers is also possible. They also deal with nodes disappearing and change routes accordingly.

tailscale (and similar solutions like netbird) still use a bunch of "proxy servers" for that. You can set them up on intermediate nodes, but that have to be dealt with manually (and you get two kinds of nodes).

I'm excited about P2P/decentralized/distributed overlay networks. Still catching up so would be grateful for tips on resources.

Pinecone[0][1], newer initiative made by former Yggdrasil[2] maker(s).

CJDNS[3].

AIUI CJDNS relies on intermediary high-uptime discoverable router nodes which is what is motivating Pinecone. POKT[4][5] to CJDNS seems like what Filecoin is to IPFS.

I'm yet to get around to doing the groundwork of grokking more established solutions like B.A.T.M.A.N. and how all these pieces fit together,

[0]: https://fosdem.org/2022/schedule/event/matrix_p2p_pinecone/

[1]: https://github.com/matrix-org/pinecone

[2]: https://yggdrasil-network.github.io/

[3]: https://github.com/cjdelisle/cjdns/

[4]: https://www.pokt.network/

[5]: https://piped.kavin.rocks/watch?v=-xgRUAA_p5E

CJDNS, a further step towards automatic and cryptographically secure nodes at the protocol level#23077

I know there is the Whitepaper. Maybe I miss the part, but I am looking how the path/next Hop is generated.

yggdrasil is a cjdns clone with different routing

cjdns has a whitepaper

https://github.com/cjdelisle/cjdns/blob/master/doc/Whitepape...

I was really excited for a moment, because I thought this was cjdns https://github.com/cjdelisle/cjdns.