cannot set interface name: Operation not permitted #2192
Labels
bug
Something isn't working
Comments
|
Lokinet typically does not run directly via a user account like this: it needs some additional permissions to create a network tunnel, which are configured in its systemd service file installed as part of the .deb. Try starting it with Lokinet-gui should be trying to do that itself (it prompts you for authentication to start the service, though how that works is system dependent). |
Hello jagerman! I greet you very dear! Thank you for your quick reply and also thank you for your suggested solution! Unfortunately, this did not solve the problem. I did what you said, but Lokinet still won't start so I can use it. Even now, unfortunately, it still behaves like the problem. A connection is not established, unfortunately. I think that's a great pity, because I think the concept of Lokinet is really great! Therefore, I hope for a solution soon so that I can also use Lokinet. I am grateful for any help you can give me! To solve the problem, I have already tried various things myself. Also in the configuration file of Lokinet. But in the end I reset all values back to default, as none of the changes helped. So I probably won't find a solution on my own. So I'm putting all my hopes on you guys, i.e. the Lokinet community and the Lokinet programmers! Well, here is the output I get when I start Lokinet with your suggested solution: |
|
On Saturday, 15 July 2023 06:08:47 EDT eisy wrote:
> ```
> $ lokinet
> ```
>
> Lokinet typically does not run directly via a user account like this: it
> needs some additional permissions to create a network tunnel, which are
> configured in its systemd service file installed as part of the .deb.
>
> Try starting it with `sudo systemctl start lokinet` instead.
>
> Lokinet-gui should be trying to do that itself (it prompts you for
> authentication to start the service, though how that works is system
> dependent).
Hello jagerman! I greet you very dear! Thank you for your quick reply and
also thank you for your suggested solution! Unfortunately, this did not
solve the problem. I did what you said, but Lokinet still won't start so I
can use it. Even now, unfortunately, it still behaves like the problem. A
connection is not established, unfortunately.
I think that's a great pity, because I think the concept of Lokinet is
really great! Therefore, I hope for a solution soon so that I can also use
Lokinet. I am grateful for any help you can give me!
To solve the problem, I have already tried various things myself. Also in
the configuration file of Lokinet. But in the end I reset all values back
to default, as none of the changes helped.
So I probably won't find a solution on my own. So I'm putting all my hopes
on you guys, i.e. the Lokinet community and the Lokinet programmers!
Well, here is the output I get when I start Lokinet with your suggested
solution:
```
***@***.***:~$ sudo systemctl stop lokinet
***@***.***:~$ sudo systemctl start lokinet
Job for lokinet.service failed because the control process exited with error
code. See "systemctl status lokinet.service" and "journalctl -xe" for
details. ***@***.***:~$ systemctl status lokinet.service
● lokinet.service - LokiNET: Anonymous Network layer thingydoo, client
Loaded: loaded (/lib/systemd/system/lokinet.service; disabled; vendor
preset: enabled) Active: activating (auto-restart) (Result: exit-code)
since Sat 2023-07-15 11:26:30 CEST; 4s ago Process: 15092
ExecStart=/usr/bin/lokinet /var/lib/lokinet/lokinet.ini (code=exited,
status=1/FAILURE) Process: 15105 ExecStopPost=/usr/sbin/lokinet-resolvconf
remove /var/lib/lokinet/lokinet.ini (code=exited> Main PID: 15092
(code=exited, status=1/FAILURE)
CPU: 49ms
***@***.***:~$ journalctl -xe
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to
turn off this notice.
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit UNIT has successfully entered the 'dead' state.
Jul 15 11:26:16 unbekannt systemd[3101]:
var-lib-docker-overlay2-9b3cabe6ddd2b002bf51c74cc1f92b6654ac1ddb8aaa> ░░
Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit UNIT has successfully entered the 'dead' state.
Jul 15 11:26:42 unbekannt systemd[3101]:
run-docker-netns-d5668ee0b042.mount: Succeeded. ░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit UNIT has successfully entered the 'dead' state.
Jul 15 11:26:42 unbekannt systemd[3101]:
var-lib-docker-overlay2-7dce1a1f6ea0ee2fcdad841c8d0d0650364955f760da> ░░
Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit UNIT has successfully entered the 'dead' state.
**Jul 15 11:26:52 unbekannt /usr/libexec/gdm-x-session[4339]:
[4340:4527:0715/112652.073587:ERROR:get_updates_p>** lines 2481-2503/2503
(END)
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit UNIT has successfully entered the 'dead' state.
Jul 15 11:26:16 unbekannt systemd[3101]:
var-lib-docker-overlay2-9b3cabe6ddd2b002bf51c74cc1f92b6654ac1ddb8aaa8af42c3
f3ba557e660bd-merged.mount: Succeeded. ░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit UNIT has successfully entered the 'dead' state.
Jul 15 11:26:42 unbekannt systemd[3101]:
run-docker-netns-d5668ee0b042.mount: Succeeded. ░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit UNIT has successfully entered the 'dead' state.
Jul 15 11:26:42 unbekannt systemd[3101]:
var-lib-docker-overlay2-7dce1a1f6ea0ee2fcdad841c8d0d0650364955f760da54a0f41
90a2f15414a8f-merged.mount: Succeeded. ░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit UNIT has successfully entered the 'dead' state.
Jul 15 11:26:52 unbekannt /usr/libexec/gdm-x-session[4339]:
[4340:4527:0715/112652.073587:ERROR:get_updates_processor.cc(264)]
PostClientToServerMessage() fa> ```
can you give the full version of your debian system you have?
the output of the following command should suffice:
$ cat /etc/os-release
additionally do you have the systemd-resolved package installed?
…--
~jeff
|
|
Good day dear jeff, I greet you warmly. Please excuse my very late reply. Thank you for your answer and your help. So I gave up on installing lokinet normally. Instead I compiled lokinet myself. Unlike the normal installation way, this worked wonderfully easy and successfully! Since I let the system compile lokinet, it works flawlessly. This seems to be subjectively (maybe objectively) the cleanest way to install lokinet. But now I would like to answer your questions:
Best regards! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
when i start lokinet, the following error occurs:
To Reproduce
normal installation with apt, start lokinet oder lokinet-gui
Screenshots Or Logs
Device and Operating system (please complete the following information):
The text was updated successfully, but these errors were encountered: