Installation codes for installing Lokinet on Fedora?

Hello,

I am trying to find the correct terminal codes for installing Lokinet on Fedora.

I tried the install codes from this page:

It does not work on Fedora. I get a lot of this:

sudo: apt: command not found

I emailed Session support (the makers of Lokinet) twice for help. All they did was tell me to use the same codes that are on the page above. But I think those codes are for Debian.

I then found these pages:

https://rpm.oxen.io/

But the codes do not work either.

I translated this French post and tried some of the codes:

https://forums.fedora-fr.org/d/74954-installation-et-utilisation-de-lokinet-sur-fedora

I found this but don’t know what to do with it:

There is this comment that I found from a couple of years ago:

“Those who are not using a distribution derived from Debian or Ubuntu will probably have to build the Lokinet software from source. This process entails installing several software development tools; therefore, I think I can safely say that Linux Newbies who are not using a Debian or Ubuntu derived distribution will probably not be able to install the Lokinet software on their Linux computers.”

(Source: https://cheapskatesguide.org/articles/lokinet.html)

Does anyone know how to install Lokinet on Fedora?

Thanks.

Tested in Fedora 41:

sudo rpmkeys --import https://rpm.oxen.io/public.gpg \
    /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-37-$(arch)
sudo dnf config-manager addrepo \
    --from-repofile=https://rpm.oxen.io/fedora/oxen.repo
sudo dnf install lokinet --enable-repo=oxen --releasever=37
sudo systemctl enable lokinet.service --now

If your intention is to use Session, or the Oxen network, I suggest reading that post.

As I assume you are not very experienced (as you tried to use apt on Fedora) that may be a tiny bit too technical XD I also didnt understand everything.

In short: Session has taken the Signal protocol, converted it to “their own implementation” (which is bad) and made it insecure. Putting some “custom” onion network behind that doesn’t fix the primary flaw.

I was also interested in Session, but for example Software like SimpleX looks way better and you can also host your own servers. That runs on the tor network.

Thank you Vladislav.

That seemed to work…

I put this into the terminal:

$ sudo systemctl status lokinet

This is what came back…
[sudo] password for user:
â—Ź lokinet.service - LokiNET: Anonymous Network layer thingydoo, client
Loaded: loaded (/usr/lib/systemd/system/lokinet.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf, 50-keep-warm.conf
Active: active (running) since Sat 2025-02-01 15:45:46 -05; 4min 50s ago
Invocation: b57e85e51b344c2fa55c9e5145e7c42f
Main PID: 2333 (lokinet)
Status: “v0.9.11 client | known/connected: 3/2 | paths/endpoints 0/0 [ !!! Low Build Success Rate (0.0%) !!! ]”
Tasks: 8 (limit: 4193)
Memory: 8.9M (peak: 11.4M swap: 476K swap peak: 480K)
CPU: 1.432s
CGroup: /system.slice/lokinet.service
└─2333 /usr/bin/lokinet /var/lib/lokinet/lokinet.ini

Feb 01 15:50:36 fedora lokinet[2333]: [2025-02-01 15:50:36] [+4m50.004s] [path:warning|llarp/path/pathbuilder.cpp:3>
Feb 01 15:50:36 fedora lokinet[2333]: [2025-02-01 15:50:36] [+4m50.254s] [path:warning|llarp/path/pathbuilder.cpp:3>
Feb 01 15:50:36 fedora lokinet[2333]: [2025-02-01 15:50:36] [+4m50.254s] [:warning|llarp/service/endpoint.cpp:118] >
lines 1-17

It says it is active. But when I did an IP address check, it shows my actual IP, so I am not sure why it is not working.


Do you have the Fedora code for the GUI?

You need to specify a valid exit node to activate the connection:

lokinet-vpn --down
lokinet-vpn --up --exit exit_node_name
lokinet-vpn --status

It looks like their GUI client is not available for Fedora.

Okay. Thank you for the help and your time.

1 Like