cwinfo/yggdrasil-network.github.io
5
0
Fork 0
mirror of https://github.com/cwinfo/yggdrasil-network.github.io.git synced 2025-02-28 22:11:33 +00:00
Code Releases Activity

Update blog post

Browse Source
This commit is contained in:
Neil Alexander 2018-12-10 22:37:42 +00:00
parent 45d88b1a36
commit 1ff487d120
No known key found for this signature in database
GPG Key ID: A02A2019A2BB0944
1 changed files with 19 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
_posts/2018-12-12-announcing-v0-3.md
View File

@ -56,29 +56,28 @@ we have **not** needed to introduce breaking changes at this stage and currently
the network has been running a mix of both older and newer developmental nodes the network has been running a mix of both older and newer developmental nodes
without any particular issues. without any particular issues.
### New features ### Features
You'll be able to see the full list of modifications that have been made in our You can see the full list of modifications that have been made in our
[changelog](changelog.md), but I'd like to take the time to discuss some of our [changelog](changelog.md).
bigger changes.
Perhaps the largest user-facing change is the introduction of Crypto-Key Routing Perhaps the largest user-visible change is the introduction of Crypto-Key
for traffic tunnelling, allowing you to effectively use Yggdrasil as a VPN for Routing for traffic tunnelling, allowing you to effectively use Yggdrasil as a
both IPv4 and IPv6 traffic between any two given points on the network. This VPN for both IPv4 and IPv6 traffic between any two given points on the network.
tunnelled traffic enjoys the same benefits as regular Yggdrasil IPv6 traffic in This tunnelled traffic enjoys the same benefits as regular Yggdrasil IPv6
that it is end-to-end encrypted and our many optimisations assist in preventing traffic in that it is end-to-end encrypted and our many optimisations assist in
TCP-over-TCP anomalies that often arise in other solutions. I wrote an preventing TCP-over-TCP anomalies that often arise in other solutions. I wrote
introductory [blog post](_posts/2018-11-06-crypto-key-routing.md) back at the an introductory [blog post](_posts/2018-11-06-crypto-key-routing.md) back at the
beginning of November about CKR, which explains some more about how to beginning of November about CKR, which explains some more about how to configure
configure it and how it works. it and how it works.
In the background, we've made a change from using a Kademlia-based DHT to a In the background, we've made a substantial change from using a Kademlia-based
Chord-based DHT. This has some advantages in that a node can bootstrap and start DHT to a Chord-based DHT. This has some advantages in that a node can bootstrap
working with far less state information than was needed before. Additional and start working with far less state information than was needed before.
state, which we learn about automatically through searches, helps to speed up Additional state, which we learn about automatically through searches, helps to
DHT lookups. We also believe that using Chord can help us to reduce some idle speed up DHT lookups. We also believe that using Chord can help us to reduce
DHT chatter on the network in the future, and to help nodes converge more some idle DHT chatter on the network in the future, and to help nodes converge
quickly when they change their coordinates on the network. more quickly when they change their coordinates on the network.
We've fixed a reasonable number of bugs and crashes, including in the DHT, We've fixed a reasonable number of bugs and crashes, including in the DHT,
switch and ICMPv6 code, and have made a number of additions to the admin socket switch and ICMPv6 code, and have made a number of additions to the admin socket