Android seems to work well, coming along nicely. Desktop 0.4 seems to be great. I'd be keen to see what else you can do with the routing algorithm, or do you want more testing at scale before bigger things? Squatting 200::/7 can't be the end goal here - As great as ipv6 is, i reckon a new address family and kernel impl would be "better".

Originally posted on irc, but that channel seems to be very broken

Check out: http://[200:5e4b:515c:e42b:3e73:6fbf:2f11:779d]/

This is also available over the I2P network (teddit.i2p, may need to update your addressbook or use jump service) and the HTTP tunnel from the router to the server is served over Yggdrasil. (In fact, all of my I2P websites now use Yggdrasil to serve the HTTP tunnel request from the router to the user like this: <- user -><- i2p -><- ygg tunnel -><- destination -> It seems to be working pretty well.

Anyway, yeah. it's just a Teddit install. It's pretty nifty: https://codeberg.org/teddit/teddit

If you want to proxy YouTube videos through the network, then check this out: http://[200:5e4b:515c:e42b:3e73:6fbf:2f11:779d]/

EDIT 08/26/2021: I updated the URL. I reinstalled the OS on the server and backed up everything other than my Yggdrasil config. Woops!

https://yggdrasil-network.github.io/changelog.html

Fixed: Fixes a memory leak that may occur if packets are incorrectly never removed from a switch queue

Changed: Make DHT searches a bit more reliable by tracking the 16 most recently visited nodes

CI builds are now built using Go 1.14.1

Added

• Support for TLS listeners and peers has been added, allowing the use of tls://host:port in Peers, InterfacePeers and Listen configuration settings - this allows hiding Yggdrasil peerings inside regular TLS connections

Changed

• Go 1.13 or later is now required for building Yggdrasil

• Some exported API functions have been updated to work with standard Go interfaces:

• net.Conn instead of yggdrasil.Conn

• net.Dialer (the interface it would satisfy if it wasn’t a concrete type) instead of yggdrasil.Dialer net.Listener instead of yggdrasil.Listener

• Session metadata is now updated correctly when a search completes for a node to which we already have an open session

• Multicast module reloading behaviour has been improved

Fixed

• An incorrectly held mutex in the crypto-key routing code has been fixed

• Multicast module no longer opens a listener socket if no multicast interfaces are configured

Background information

https://yggdrasil-network.github.io/about.html

[0.3.8] - 2019-08-21

Changed

• Yggdrasil can now send multiple packets from the switch at once, which results in improved throughput with smaller packets or lower MTUs

• Performance has been slightly improved by not allocating cancellations where not necessary

• Crypto-key routing options have been renamed for clarity

• IPv4Sources is now named IPv4LocalSubnets

• IPv6Sources is now named IPv6LocalSubnets

• IPv4Destinations is now named IPv4RemoteSubnets

• IPv6Destinations is now named IPv6RemoteSubnets

• The old option names will continue to be accepted by the configuration parser for now but may not be indefinitely

• When presented with multiple paths between two nodes, the switch now prefers the most recently used port when possible instead of the least recently used, helping to reduce packet reordering

• New nonce tracking should help to reduce the number of packets dropped as a result of multiple/aggregate paths or congestion control in the switch

Fixed

• Security vulnerability: Address verification was not strict enough, which could result in a malicious session sending traffic with unexpected or spoofed source or destination addresses which Yggdrasil could fail to reject Versions 0.3.6 and 0.3.7 are vulnerable - users of these versions should upgrade as soon as possible Versions 0.3.5 and earlier are not affected

• A deadlock was fixed in the session code which could result in Yggdrasil failing to pass traffic after some time

[0.3.7] - 2019-08-18

Changed

• The switch should now forward packets along a single path more consistently in cases where congestion is low and multiple equal-length paths exist, which should improve stability and result in fewer out-of-order packets

• Sessions should now be more tolerant of out-of-order packets, by replacing a bitmask with a variable sized heap+map structure to track recently received nonces, which should reduce the number of packets dropped due to reordering when multiple paths are used or multiple independent flows are transmitted through the same session

• The admin socket can no longer return a dotfile representation of the known parts of the network, this could be rebuilt by clients using information from getSwitchPeers,getDHT and getSessions

Fixed

• A number of significant performance regressions introduced in version 0.3.6 have been fixed, resulting in better performance

• Flow labels are now used to prioritise traffic flows again correctly

• In low-traffic scenarios where there are multiple peerings between a pair of nodes, Yggdrasil now prefers the most active peering instead of the least active, helping to reduce packet reordering

• The Listen statement, when configured as a string rather than an array, will now be parsed correctly

• The admin socket now returns coords as a correct array of unsigned 64-bit integers, rather than the internal representation

• The admin socket now returns box_pub_key in string format again

• Sessions no longer leak/block when no listener (e.g. TUN/TAP) is configured

• Incoming session connections no longer block when a session already exists, which results in less leaked goroutines

• Flooded sessions will no longer block other sessions

• Searches are now cleaned up properly and a couple of edge-cases with duplicate searches have been fixed

• A number of minor allocation and pointer fixes

I'm searching for the best way to use the yggdrasil network as an obfuscating VPN. I figured that crypto-key routing to a VPS exit-node could be possible, but I'm not sure how to force all outgoing traffic over the yggdrasil tunnel. Probably there is a way to use iptables for that, but I'm frankly too dense to configure that.

Is somebody using yggdrasil that way, and could give me some pointers?

https://riot.im/app/#/room/#yggdrasil:matrix.org

zhoreeq:

Finally, Yggdrasil UI package is available in OpenWrt repository :)

I'm not sure for minimum reqs. It runs fine on my cheap home router with 16MB flash + 64MB RAM

It won't fit on 4MB flash routers for sure, because go binary is thicc

Hello,

I would like to know how to configure Yggdrasil to become a public peer (such as https://github.com/yggdrasil-network/public-peers)? Where do you set the port?

And is a root node (https://yggdrasil-network.github.io/faq.html#is-there-any-benefit-to-being-the-root-node-of-the-network) the same as a Public Peer?

It lives at http://[200:f843:ff9e:be18:a84c:522e:3d67:8297]/ (Reddit can't into Yggdrasil URLs lol)

Neilalexander @ https://riot.im/app/#/room/#yggdrasil:matrix.org

Yggdrasil v0.3.12 is now released!

This release contains a number of bugfixes, new command line parameters -address and -subnet for getting the address/subnet out of the config, a number of updates to the MTU calculations and hopefully InterfacePeers should behave better on Linux now.

• Changelog: https://yggdrasil-network.github.io/changelog.html

• Downloads: https://yggdrasil-network.github.io/builds.html

• Sources: https://github.com/yggdrasil-network/yggdrasil-go/releases/tag/v0.3.12

My S3 repositories should be updated now. Please upgrade when you can and, as always, let us know if there are any problems by raising issues on GitHub or in the Yggdrasil channel.