search

oxen-io / lokinet

Lokinet is an anonymous, decentralized and IP based overlay network for the internet.
https://lokinet.org/
GNU General Public License v3.0
1.72k stars 220 forks source link

Lokinet does not work in Windows 10 x64 #2075

Open absolutep opened 1 year ago

absolutep commented 1 year ago

Describe the bug

Here, I describe various issues that I encountered while using LOKINET v0.9.10 in Windows 10 x64.

1) Whenever Lokinet is started, even after 10 minutes of uptime. Not even the default wiki SNAPP given in oxen document opens.

Ideally, it should open as the application integrates into the network. But it does not at all. Even after multiple tries.

2) Lokinet disconnects my internet when I toggle to see charts or logs. This is seriously irritating.

3) I usually minimise lokinet so that I can do my work. But whenever I open it back again it shuts down my internet.

4) Lokinet does not shut down even after I have exited the application. It does not matter how much time has passed, in background it is always open as can be seen from the screenshot. I have to personally go to task manager each time to END TASK. Also, in OPTS I have specified that "stop the lokinet daemon when exiting the app".

5) Lokinet VPN is a hit and a miss. It works only sometimes and that too after repeated tries. (Only talking about default exit node here). In addition to it, when it works after approximately 15 minutes it shuts down again. I do not know if this is because of the load on default exit node or some other technical issue.

Screenshots Or Logs

As you can see, I can clearly search clearnet even though Lokinet says I am connected to lokinet.

1

Lokinet not shutting down even after exiting the app.

203328688-912835c5-71f8-43a1-b28e-b5b378609435

Device and Operating system (please complete the following information):

majestrate commented 1 year ago

Whenever Lokinet is started, even after 10 minutes of uptime. Not even the default wiki SNAPP given in oxen document opens.

is this probably.loki?

majestrate commented 1 year ago

the flakeyness issues on dns are probably related to https://github.com/oxen-io/lokinet/issues/2073

the logs issue is something that i can see could be an issue if we have a lot of backlog that the gui does not consume. this can be made into its own issue.

Lokinet does not shut down even after I have exited the application.

lokinet gui does an "exit to tray" which is imo wrong behavior but for whatever reason i was told windows users expected this as default. you need to exit it from the tray icon itself.

majestrate commented 1 year ago

issue on exit behavior made: https://github.com/oxen-io/lokinet-gui/issues/35

jagerman commented 1 year ago

Whenever Lokinet is started, even after 10 minutes of uptime. Not even the default wiki SNAPP given in oxen document opens.

I believe we have a fix for this that should make it into a build this week. If you want to try a test build, https://oxen.rocks/tewinget/loki-network/more-verbose-logging/lokinet-windows-x64-20221118T214554Z-50a498214.zip contains the fix. (Note that this is an unsigned build and Windows will give a nag screen about it.)

majestrate commented 1 year ago

Whenever Lokinet is started, even after 10 minutes of uptime. Not even the default wiki SNAPP given in oxen document opens.

I believe we have a fix for this that should make it into a build this week. If you want to try a test build, https://oxen.rocks/tewinget/loki-network/more-verbose-logging/lokinet-windows-x64-20221118T214554Z-50a498214.zip contains the fix. (Note that this is an unsigned build and Windows will give a nag screen about it.)

once that branch is cleaned up it can fix #2073

majestrate commented 1 year ago

(or we can extract the one line diff we need into a commit)

jagerman commented 1 year ago

Lokinet does not shut down even after I have exited the application. It does not matter how much time has passed, in background it is always open as can be seen from the screenshot. I have to personally go to task manager each time to END TASK.

The "X" button only closes the GUI window, it does not exit: rather lokinet sets itself up as an active system tray icon without having an active window (like many background services on windows, e.g. Steam, driver panels, network settings, VPNs). Exiting requires right-click -> Quit on the lokinet icon, just like Steam, my UPS monitoring app, and various other VPN services.

majestrate commented 1 year ago

fair.

majestrate commented 1 year ago

(posted on wrong issue)

absolutep commented 1 year ago

Whenever Lokinet is started, even after 10 minutes of uptime. Not even the default wiki SNAPP given in oxen document opens.

is this probably.loki?

I am talking about this SNAPP = https://docs.oxen.io/products-built-on-oxen/lokinet/snapps/accessing-snapps

absolutep commented 1 year ago

Whenever Lokinet is started, even after 10 minutes of uptime. Not even the default wiki SNAPP given in oxen document opens.

I believe we have a fix for this that should make it into a build this week. If you want to try a test build, https://oxen.rocks/tewinget/loki-network/more-verbose-logging/lokinet-windows-x64-20221118T214554Z-50a498214.zip contains the fix. (Note that this is an unsigned build and Windows will give a nag screen about it.)

once that branch is cleaned up it can fix #2073

I can wait for stable version when it is issued. Thanks.

absolutep commented 1 year ago

Lokinet does not shut down even after I have exited the application. It does not matter how much time has passed, in background it is always open as can be seen from the screenshot. I have to personally go to task manager each time to END TASK.

The "X" button only closes the GUI window, it does not exit: rather lokinet sets itself up as an active system tray icon without having an active window (like many background services on windows, e.g. Steam, driver panels, network settings, VPNs). Exiting requires right-click -> Quit on the lokinet icon, just like Steam, my UPS monitoring app, and various other VPN services.

Ah! Okay! Thanks for clarifying that. I did not know. Also, I do not use Steam - so whatever parallels you are trying to create is going over my head.

Further, when ever I click on "X" in Lokinet GUI - I expect application to completely quit - just like other applications do so in Windows 10 when "X" is clicked-on. I think there is no need to complicate this function.

I'd request to reinstate the normal functionality of "X" button in GUI of Lokinet. If I wanted to let Lokinet run in background, I would much rather just minimize the GUI of lokinet application and let it work in background than clicking on "X" & wondering why is it not quitting.

Exiting requires right-click -> Quit on the lokinet icon, just like Steam, my UPS monitoring app, and various other VPN services.

As for this, I see no Lokinet icon anywhere which is right-clickable. Not on desktop anyway.

The way I access Lokinet is through Start icon and when I right-click, what happens is as described in the screenshot.

1

absolutep commented 1 year ago

New update somewhat fixed point (5) although I did select always connect to exit node while installing the new update.

Now, with default exit node - lokinet connection seems to work for longer duration.

Downloading seems fine (max speed 500KBps) but uploading and browsing of the clearnet are still not working properly.

SNAPPs aforementioned still not working.