dhaavi

Can you communicate the value of Octelium in 25 words or less?

This is the correct capitalisation.

Thanks. Made my day.

Mycoria is built for resilience - so not relying on the current Internet backbone working flawlessly.

Even if the current Internet works "normally", many users of similar network have reported better connectivity with the overlay network routing. Eg. routing on the IANA Internet is highly influenced.

If you let Mycoria generate a config for you, it will include your current public Interfaces on the device, so this will only be true for servers. Mycoria does not rely on IANA addresses, but uses them to improve the network structure automatically: Finding better routes between routers over the IANA Internet.

For the use case given by Zrok, Mycoria is very similar.

Nothing can access your device by default. You will have to define services and add "friends" (your other devices) to allow them to access.

Latency is considered in routing.

Every router announces itself on the network. Routers can optionally publish their IANA IP addresses.

Buckets live on the routers themselves.

Interesting idea - thanks! Will think about this more.

Thanks for the feedback. I will re-evaluate.

It's quite fast. Especially if you host a server near you and connect to it.

If nobody knows who you are, you are still anonymous, even if there is an ID.

With private addresses (in the future) this will also be solved, as Mycoria will be able to temporary addresses / IDs.

I understand what you mean. Yes, the technology can do that. I was thinking about the WireGuard as a software in itself.

Thanks for taking the time for this feedback.

This is what I hope to solve with the private addresses: These are not geo-marked and not routable. Eg. they are randomly generated and cannot be attributed to a geographic location (easily).

Probably - depending on your use case. Mycoria is still more or less MVP though.

Veilid is new to me, will have to read about it first. Thanks the pointer!

Switch labels are effectively interface IDs on the servers, there is no data to be stored.

Geo encoding simply improves routing to unknown routers, kind of as a baseline structure to the whole network.

Yes, this is correct.

Mycoria has in integrated firewall for this, just in case that information got lost somewhere.

This also means that devices of the company will help other devices of the company to reach their destination, adding to resilience in outages and emergencies.

You can of course build bridges between these networks. This definitely something that is planned.

Mycoria is secure by default: It has an integrated firewall that only allows access from explicitly defined addresses, or, optionally from anyone in the network.

Also, multicast is completely disabled on Mycoria.

Nope. I did that with the last network I built: https://safing.io/spn/

Mycoria focuses a more on scalability, but still has some privacy focus.

Currently, this is just a fun project for me. I have technical ideas, but I don't have growths plans or the like - and it is nice that it does not have to.

Yes, I would expect the privacy would increase by some degree with more users, but I don't know by how much.

Although I will be using the technology in future projects, so Mycoria will benefit from that.

Thanks!

I wasn't really aware segment routing, tbh. However, I do think with where Mycoria is going, the additional control to change things as needed will be required.

I have used VerifPal https://verifpal.com/ for security analysis before, but not yet with Mycoria.

I think I have seen it, but that was a while ago.

Will read through it later! Thanks!

Thanks!

Just like the Internet we currently have, albeit less accurate, but more stable.

See https://github.com/mycoria/mycoria/blob/master/m/geo_marker....

In the future, non-routable private addresses will solve that for users that require it.

Thanks! Well, every participant has to cover their own server/bandwidth cost. So, from my perspective, yes, bandwidth is free and abundant. Although I hope that Mycoria can/will perform well in lower bandwidth areas.

Interesting. Can you link that paper/article?

The DNS is not central. Everyone maintains their own local mapping. When accessing a website on mycoria, you open a URL like this that first creates the mapping and then forwards you to it: http://router.myco/open/speedtest.de.myco/fd13:6239:a07a:eb4...

Mycoria brute forces a public key/IP pair until it matches the desired geo-prefix.

Tailscale is P2P network with optional relays, Mycoria is a mesh network.

Tailscale has central policies. Mycoria is more like a collective where you can offer services to everyone else within the network.

The DNS is not central. Everyone maintains their own local mapping.

When accessing a website on mycoria, you open a ULR like this that first creates the mapping and then forwards you to it: http://router.myco/open/speedtest.de.myco/fd13:6239:a07a:eb4...

This is a simplified conclusion. The IPv6 address is the fingerprint of the public key. They actual keys are exchanged over the network before any real traffic is sent.

There is not central store. This is done on the fly.

It has a lot of similarities and you can use it as a replacement for the core features.

Interesting, did not expect that question.

I would have thought libp2p is library enough to not be comparable. Am I wrong?

Mycoria is a ready-to-run software.

Geographical: No enforcement, but if you choose the wrong country, packets will have issues reaching you, because routing is "bucketed" into layers of regions. Routers only hold the bext x routes to each bucket.

Transport is custom in order to support source routing, but I use the WireGuard library for setting up the interface and such.

(I have experience with cryptography in network protocols from Safing/SPN - the cryptography of which was audited without fault. Also, I am _very_ cautious and keep to standards as close as possible.)