ergo VS yggdrasil-go

Ergo Framework does - https://github.com/ergo-services/ergo

https://github.com/ergo-services/ergo for golang

I think you should clarify what exactly you need. If you need something like TCP/UDP socket acceptor pool you may want to try Ergo Framework with ready to use design patterns https://github.com/ergo-services/ergo . Example for TCP https://github.com/ergo-services/examples/tree/master/gentcp, for UDP https://github.com/ergo-services/examples/tree/master/genudp

In case if you want to feel a flavour of Erlang in Golang - https://github.com/ergo-services/ergo

Besides, something like this already exists, I don’t see the point, but hey to each there own… https://github.com/ergo-services/ergo

Thanks for sharing. Looks good as a first attempt in the long way to production state. You may also want to take a look another approach of actor based implementation https://github.com/ergo-services/ergo

wait, so this can do the same? https://github.com/ergo-services/ergo

Unrelated project with the same name (coincidentally written in the same language): https://github.com/ergo-services/ergo

"an actor based Framework for creating microservices using technologies and design patterns of Erlang/OTP in Golang"

The project repository has been moved to https://github.com/ergo-services/ergo. It is still available on the old URL https://github.com/halturin/ergo and GitHub will redirect all requests to the new one (thanks to GitHub for this feature).

Really hope the network segregation[1] feature makes it in at some point.

[1]: https://github.com/yggdrasil-network/yggdrasil-go/discussion...

> The next version will make it much simpler to deploy isolated networks by using TLS roots to prevent accidental peerings.

Is that PR #1038 [1]? Any info on how to use that feature and whether it works over multicast as well?

I noticed this PR uses SHA-1 for matching fingerprints. SHA-1 has been broken for 13 years now. Is it possible to use something more secure?

> It's also worth noting that Yggdrasil doesn't have the equivalent of "peer exchange" — only directly connected peers would ever find out your public IP address. Yggdrasil will not form new peerings automatically, with the single exception being multicast-discovered nodes on the same LAN.

Right, my worry is that by having a server with a public IPv4 address and Yggdrasil running on an open port (so that my other nodes can connect to it) will allow someone to connect to it (either on purpose or accidentally) and cause my traffic to route over their node(s) and/or the public mesh.

Thanks!

[1] https://github.com/yggdrasil-network/yggdrasil-go/pull/1038

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).

The only real solution long-term is completely peer-to-peer ad-hoc networking that doesn't depend on BGP.

A few projects are in similar territory but none I've seen are working at the layer of bypassing BGP. Many are just acting as an overlay; which works to an extent. https://github.com/yggdrasil-network/yggdrasil-go

It's probably begging for a different model of the "internet" and where data lives.

My requirements:

1. Offline-first applications that sync via a pub/sub DHT of trusted peers. More details here but basically allows bypassing BGP.

at least on the official discord the recommended way if you don’t want to play on a public server is using yggdrasil

> I’ve been dreaming lately of a tor-like network that’s based loosely on the idea of tailnets. Rather than blockchain bullshit, you’d have a direct ring of trust with friends, and then you could set up access policies to forward packets for people you don’t trust, but who know someone you do trust.

Might want to check out Yggdrasil. It lets you can create a real mesh routed, E2E encrypted network. You can keep your network private, or connect it to the greater network and route others. There's no ring-of-trust (I can't imagine that as a viable solution at scale). But the config file has an AllowedPublicKeys section if you want to specify who can route through your node.

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

This may also interest you

https://github.com/slackhq/nebula https://github.com/yggdrasil-network/yggdrasil-go https://github.com/cjdelisle/cjdns

There is an overview in the whitepaper: https://github.com/yggdrasil-network/yggdrasil-go/blob/maste...

It fits the "private VPN" use-case quite well in my experience. You can connect to the wider network over the Internet, or just set your nodes up. If yggdrasil is installed on every router, it automatically creates a nice network topology, since it finds peers on the local subnet. Router advertising is also a possibility.

Though there's no real drawback to connecting to the wider network since it's end-to-end encrypted, you have to be aware that specifying more than one peer will make it possible for traffic to be routed trough you, so the whole network performance can be sensitive to the choices that are made when peering over the Internet, as I think hop count is the only metric for now.

For private meshes, I don't think you can specify fallback peer addresses over the Internet, so you have a bit of the same risk here. I've seen some info on mesh wireguard networks with peer information stored in DNS at this year's FOSDEM, but that's currently definitely more configuration than yggdrasil.

End-to-end encryption and the ability to generate your own static, roaming-compatible IPs is nice. I just wish one could open sockets directly with a crypto key rather than the derivated IP.

For more discussion, I can really recommend the Matrix chat room :)