Proposal: Dropping MIPS/ARMv5 Support for Nym VPN OpenWrt
Looking for community feedback on whether to continue supporting older architectures (MIPS, MIPSEL, ARMv5) for the OpenWrt builds.
The Problem
These are 32-bit platforms that lack hardware support for 64-bit atomic operations. Every time an upstream dependency uses AtomicU64 (common in Rust async/networking code), the build breaks and requires manually patching the crate.
Weāre already maintaining patches for 5 crates (schemars, coarsetime, prometheus, gateway-client, credential-verification), and boringtun just broke the build. This pattern will continue as the codebase evolves.
Unaffected Architectures
The following targets build cleanly with no patches:
From what I can tell, GL.inet Flint v1 is aarch64. The standalone armv7 binary runs because the aarch64 kernel can execute 32-bit ARM binaries, but opkg strictly checks package architecture metadata.
aarch64_generic should work. Share the output of the opkg command just to be sure though.
cannot connect to mixnet, credentials were accepted and account is valid, works on android and linux x64
Sun Feb 15 15:50:04 2026 daemon.info nym-vpnd[19237]: 2026-02-15T15:50:04.735500Z INFO perform_initial_authentication{gateway=2JAVMSBKVvV5DAw8fsdsUjtaaTcwjzPvm4jMzaLGVzJJ gateway_address=ws://141.227.186.52:9000/}: nym_gateway_client::client: close time.busy=1.97ms time.idle=160ms
Sun Feb 15 15:50:04 2026 daemon.info nym-vpnd[19237]: 2026-02-15T15:50:04.735541Z INFO nym_gateway_client::client: Claiming more bandwidth with existing credentials. Stop the process now if you don't want that to happen.
Sun Feb 15 15:50:04 2026 daemon.info nym-vpnd[19237]: 2026-02-15T15:50:04.735560Z WARN nym_gateway_client::client: Not enough bandwidth. Trying to get more bandwidth, this might take a while
Sun Feb 15 15:50:06 2026 daemon.info nym-vpnd[19237]: 2026-02-15T15:50:06.564981Z ERROR nym_gateway_client::client: failed to claim ecash bandwidth with the gateway...: gateway returned an error response: the provided ticket failed to get verified
Sun Feb 15 15:50:06 2026 daemon.info nym-vpnd[19237]: 2026-02-15T15:50:06.565041Z INFO nym_gateway_client::client: attempting to revert ticket withdrawal...
Sun Feb 15 15:50:06 2026 daemon.info nym-vpnd[19237]: 2026-02-15T15:50:06.566174Z ERROR nym_client_core::client::base_client: Could not authenticate and start up the gateway connection - gateway returned an error response: the provided ticket failed to get verified
Sun Feb 15 15:50:06 2026 daemon.info nym-vpnd[19237]: 2026-02-15T15:50:06.566724Z WARN nym_registration_client::builder: mixnet build/connect error: failed to connect to mixnet
Sun Feb 15 15:50:06 2026 daemon.info nym-vpnd[19237]: 2026-02-15T15:50:06.567489Z ERROR nym_vpn_lib::tunnel_state_machine::tunnel_monitor: Error: Tunnel monitor exited with error
Sun Feb 15 15:50:06 2026 daemon.info nym-vpnd[19237]: Caused by: tunnel error
Sun Feb 15 15:50:06 2026 daemon.info nym-vpnd[19237]: Caused by: registration client error
Sun Feb 15 15:50:06 2026 daemon.info nym-vpnd[19237]: Caused by: failed to connect to mixnet
Is there a way to see whether amneziaWg is installed or used by nymvpn? When I search for amnezia in Luci-software i cannot find it (did already restart after installation; gl-inet beryl ax mt-3000, OS information: Linux (OpenWrt 24.10.4) (aarch64), kernel: 6.6.110
Itās a kernel module, not sure if LuCI shows those in the UI.
To check if you have it do:
lsmod | grep amnezia
This will show you loaded kernel modules (filtered for amnezia). If you see it here, the VPN is using it. Currently the app checks if you have the kernel module, if yes it will use amnezia-wg, if no it will use standard wireguard. Note: you need OpenWrt 23.05+ for amnezia-wg.
Could potentially add an option to toggle between amnezia and standard.
root@klint:~# nym-vpnc account forget
Failed to forget account: internal error: Unable to forget account while connected
Error: internal error: Unable to forget account while connected