On: PeerVPN – Open-source peer-to-peer VPN

[jMyles]

Once running, cjdns creates a virtual ipv6 adapter.

To connect to other nodes, it uses either IP(v4 or v6) or Ethernet Frames. See: https://github.com/cjdelisle/cjdns#3-connect-your-node-to-yo...

I'm working on a Django Rest Framework frontend for it, Cirque: https://github.com/jMyles/cirque, which will make this easier to visualize.

[codexon → jMyles]

This isn't helpful for running software that only supports ipv4 though.

[jMyles → codexon]

Ahh, I misunderstood your requirement.

Fortunately, CJDNS works for this use case as well. It is possible to use a "tunnel" to connect CJDNS nodes via an IPv4 virtual interface or to connect to a gateway to IPv4. This way, IPv4 software can connect both to other nodes and to the outside internet.

At the moment, I believe that this is only configurable through the UDP admin interface, but this is most definitely a feature that we'll build into Cirque.

https://github.com/cjdelisle/cjdns/blob/master/admin/README....

[codexon → jMyles]

My personal usage case is to secure a handful of servers across datacenters for software that don't have encryption enabled.

If I use CJDNS to do this, it seems like I have a lot more steps to do. I have to copy everyone's pub key and setup ipv4 tunneling on each server?

With PeerVPN all I have to do is pick a single password and copy and paste it to each other server while only needing to change the static IP.