sysop.link
(aka cryptoanarchy.org)Anonymous Internet eXchange Pillbox
Located in Gothenburg/Sweden
In a peaceful wardrobe with phat phiber datalink
Shuffling traffic for Yggdrasil, I2P and Tor, and more.
Before connecting to this relay
It defeats the purpose (ie. decentralization, camouflage, etc) if everyone is connecting to a single relay, or a small number of super-relays. Maybe prefer somewhat nearby relays if possible, or even better: Your friends unlisted relays. That said, nothing stops you from connecting here, everyone is welcome.Dont forget to configure your firewall, to handle the yggdrasil tun device correctly.
Public relays
Yggdrasil ID
IPv6: 200:cd69:861c:adfc:96d6:8d85:fdfc:4cdPublic key: 994b3cf1a901b494b93d0101fd99297bc30285501ac32d2fcdefca02d134054b
Yggdrasil connection
Adding ?key=994b3cf1a901b494b93d0101fd99297bc30285501ac32d2fcdefca02d134054b to the end of any of these links requires sysop.link to authenticate with that public key when you connect to it. That way you can be sure its really sysop.link that you connected with. The key is optional but suggested if you connect over the internet. You can specify the ?key=... when connecting over Tor or I2P as well, but the tunnel destinations (ie. the "...b32.i2p" and "...onion"s) are in themselves sufficient authentication.If you connect over both plain Internet and the darknets, yggdrasil will prefer the fastest path, which will likely be the plain internet links. Because the round trip time (RTT) is so high for darknets, the yggdrasil network will almost always avoid routing through the darknets if possible. Therefore you gain nothing from simultanously connecting over both.
Plain Internet yggdrasil link:
Maybe select one, not both.
quic://sysop.link:555?key=994b3cf1a901b494b93d0101fd99297bc30285501ac32d2fcdefca02d134054b
tcp://sysop.link:555?key=994b3cf1a901b494b93d0101fd99297bc30285501ac32d2fcdefca02d134054b
Yggdrasil-I2P tunnels (X+? hops in I2P, where X is your tunnel length and ? is mine):
Select more than one of them if you dont want intermittent connectivity!
Assuming your I2P Socks service is at localhost:4447:
socks://localhost:4447/mm6nn75i3xfy7yc3dlj567gz3eq4qram55beqfw5ogf5lfj6hjoq.b32.i2p:555
socks://localhost:4447/hgtciq2ususgkmomliphhwenaafdd3lvg3xayzhoyyxn2x3uix5a.b32.i2p:555
socks://localhost:4447/3xgziioqsz6q7m3ihcl6k5ojti5vats2jze2ilajnt5a62v3ltfa.b32.i2p:555
Yggdrasil-Tor tunnel (3+3 hops in Tor):
Assuming your Tor Socks service is at localhost:9050:
socks://localhost:9050/iniuzq6i6r4tgbd3shnfgcm6ntg64lc75owmcnjyudgbajq7wvvrzwad.onion:555
Yggdrasil-Tor tunnel (3 hops in Tor to exit node -> internet -> sysop.link):
Assuming your Tor Socks service is at localhost:9050:
socks://localhost:9050/sysop.link:555?key=994b3cf1a901b494b93d0101fd99297bc30285501ac32d2fcdefca02d134054b
I2P over Yggdrasil
Both I2P and Yggdrasil can use each other for transport, both can be overlay networks on top of the others. sysop.link routes between the layers and provides through-hole interconnect, so top layer can talk with below layers and vice versa. This is maybe useful for camouflage, or for creating multi-mode darktube, etc. Read this HOWTO and the i2pd manual for details :PI2P relay within Yggdrasil
[200:cd69:861c:adfc:96d6:8d85:fdfc:4cd]:18143
There are a bunch of other I2P relays in there as well (~100). A few I2P nodes are yggdrasil-only, others are accessible in both yggdrasil and plain internet, and the vast majority (~15k) only via plain internets.
I2P over yggdrasil only works with i2pd, not the java I2Ps. You need to update your [meshnets] section in the config to enable using yggdrasil as transport, and perhaps have a look at the [reseed] section if you fail to find peers.