son now after the last debug approaches with @code-zm, ive installed the last version and it looks promising.
The error is gone.
if i tried to set the seed and login, it comes an timeout and if i tried this again there comes the following error:
Failed: Failed to set account: an account is already stored Error: an account is already stored
And the Connection Wheel is processing but the connection seems not established.
regards
Added custom DNS, logs in the app, and bug fixes.
Working 100% for me.
Very nice.
For me, he same problem accures again. The Panel where I can set LAN-Access is gone in the webpage.
Bugs, that I have found are:
I guess its the same with allow lan access.
minor bug: 1.22.1 is installed - on the webpage it sais 1.22.0-beta
I removed LAN policy option and just set the default to always on. In my opinion, this makes sense because a router always should be reachable by devices on the LAN.
The account persistence bug youāre getting is odd though. Iāll look further into it today and see if I can replicate it. As of now, I have restarted my test device many times and the account persists across reboots.
Also, which problem are you referring to here? You cannot access via LAN devices or something else?
Sorry, same problem means:
I connect to nym network and cant access the router, neither ssh nor webpage.
Can you run the diagnostic script again?
Also - try this as a sanity check first before connecting:
nym-vpnc lan set allow
Here you are. The json is set correctly. It seems that I need to set everything manually per nym.vpnc *** set *** commands.
Like the account information.
Hello! Iām here to contribute some feedback with 3 different OpenWrt devices I own. Currently running into some problems with the first router Iām configuring;
Device: Gli.Net GL-MT6000
OpenWrt vers: 24.10.4
Arch: aarch64_cortex-a53
Problem 1: DHCP seems to just entirely stop working whenever the VPN is turned on. Old devices stay connected and are tunnelled perfectly, but any new devices are blocked out from obtaining an IP from the router. Connecting via static IP works perfectly fine, but DHCP does not. How can I fix this strange issue?
Problem 2: Jank after reboot. When the routerās back on, Iām always disconnected, and the daemon reports me as logged out. After restarting it once or twice, it remembers my credentials and connects me successfully. Is this something which can be fixed? Would a killswitch be possible?
Thank you for making this port, I greatly appreciate your work!
I have a thing, which is not an issue, but an implementation missing, I think.
Each time the router restart, I have to click āconnectā on the VPN.
Wouldn t that be possible to remember the old selection of the previous node, and reconnect automatically on thoses node, when the router restart?
Thanks for the bug reports and suggestions, patch coming out soon with fixes.
The reboot issue seems to stem from nym-vpnd using /var/lib/nym-vpnd as its config location. On openwrt /var is a symlink for /tmp meaning it resides in RAM and gets erased on reboot.
The DHCP issue is from firewall rules. Need to add a new rule for it and should be good to go.
Having the VPN connect on reboot is a good QOL feature, will add this to the next release. As far as having the kill switch, itās currently only on when the VPN is connected, which if we set the VPN to connect automatically on reboot it will effectively be āalways onā.
Thanks for running this again. I see in your firewall rules thereās an existing table setup inet vpn_table that seems like it could be causing issues.
Does your router have some existing VPN setup? Those rules could be breaking it.
Yes. There is WG and OpenVPN installed on it. Usually I only use wg. When I try NYM I close existing connections
Fixes are ready!
Changes:
/etc instead of /var for config dataInstall the latest .ipk for your arch here:
Will be adding amnezia-wireguard support this weekend!
Hey, thanks a ton for your feedback ! This is exactly the stuff we need from the community.
Iām really starting to think that a separate repo that would host the packages, build instructions and some useful scripts is the way to go.
Itās difficult to track issues here to be honest ā¦ 
now to your 3 observations :
problem 1: I also ran into DHCP issues on the ancient 21.04 release (their custom GL.INET fork of OpenWRT on XE-3000 ) but it was mostly DNS related, first on the router itself ( had to do ssh into the router and try running a bunch of commands to change some settings using nym-vpnc ) and then the clients were not routed properly - I could ping stuff but couldānt resolve anything.
Note that this was late at night before my flight back to Prague from Greece lol
@code-zm I doubt that the issue with new clients not getting a new address assigned is a firewall issue, itās something else and it sounds like a super funny bug or misconfig .
2 weeks ago when I tested it on that device (GL.INET XE-3000 ) that could have been and most likely it was caused by firewall but this seems kinda different imho.
Problem 2 : AMAZING OBSERVATION ! This shouldnāt be happening that youāre disconnected after reboot and gotta be simple enough to fix that.
Thanks a ton, now let me fire up some other device I have here to replicate the issues you reported.
Can we make a poll and vote on a question of a new repository that would host everything as written above at the beginning ?
Yeah, just verified that itās an err on our side with the reboot. Itās a simple fix though. Working on it now (also gonna include the latest changes from upstream nym-vpn-client repo )