Hosting a Lokinet Exit - A Guide for the Lazy

This is a super abridged guide on setting up a lokinet exit node inside docker.

prepare the host

docker using apt:

$ sudo apt install docker docker-compose wget

grab the docker-compose.yml

$ mkdir -p /usr/local/exit/
$ wget https://github.com/oxen-io/oxen-docker/raw/main/lokinet/docker-compose.yml -O /usr/local/exit/docker-compose.yml

turn it on

put the exit node up:

$ cd /usr/local/exit && docker-compose up -d

now get the exit node's .loki address:

$ cd /usr/local/exit && docker-compose exec lokinet print-lokinet-address.sh

client usage

your exit node is now usable, you can turn it on on a lokient client using the lokinet-vpn command:

$ lokinet-vpn --up --exit putyourexitaddresshere

updating

Ocassionally you'll want to update the docker images, you can do that using this command:

$ cd /usr/local/exit && docker-compose pull && docker-compose restart

OH GOD OH FUCK OH GOD

your exit is ready, enjoy the packets.

Custom Images

see our …

Read more ...


Opportunistic SMTP over Lokinet: it could work...

STMP, isn't. It has a lot of auxillery stuff and it's a nightmare to run a mail exchange. That being said, the excessive flexibility of the protocol stack can be a good thing if you know how to use it.

Given you use a postfix + opendkim setup I have devised a super neato near turnkey way to exchange email between mail exchanegs over lokinet while still coexisting with non lokinet mail exchanges.

To do all this install lokinet, persist the snapp keys in /var/lib/lokinet/lokinet.ini in the [network] section keyfile=/var/lib/lokinet/hs.private, then restart lokinet to apply settings. To get your .loki address do a dig @127.3.2.1 -t cname localhost.loki (after restart of course)

The changes needed for the mail exchange side is actually really simple. My dns configs (bind9 style) for my mail exchange are now effectively this:

IN …

Read more ...