sysop.link

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.

Yggdrasil ID

IPv6: 200:cd69:861c:adfc:96d6:8d85:fdfc:4cd
Public 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. For example you can connect to a local yggdrasil node and through it you connect via the friend-to-friend meshnet (thay may route over random darknets) until you reach some set of I2P-enabled yggdrasil nodes, which lets you connect to the I2P network. HOWTO

I2P relay within Yggdrasil
[200:cd69:861c:adfc:96d6:8d85:fdfc:4cd]:18143

There are a bunch of other I2P relays in there as well. In general if you just get I2P to work over yggdrasil it will autoconfigure, so you dont need to specify peers manually. If not, you might have to fiddle with the settings for how it obtains the list of peers at bootup (see [meshnets], [reseed] in i2pd.conf).