Verified on Ubuntu 24.04 arm64 and armhf (systemd containers + simulated LAN):
- Install / reinstall / uninstall
- Start on boot
- Update on start (a stale cache is replaced with v14.9.4 automatically)
- Re-download and restart after the plugin requests an update (
uu.update) - Booting offline (starts from the cache if present; without a cache, keeps retrying and starts once the network is back)
- The plugin connects to NetEase's servers (
106.2.95.34:16000) withuu_status=0; the iptables self-test rules are added/removed correctly - LAN clients with gateway/DNS pointed at this machine get internet access (including with a FORWARD DROP policy) and DNS resolution
- Firewall rules are restored within a minute after being deleted; stopping the service removes the plugin and all gateway rules
- armv7 (H3C BX54 plugin, 32-bit ARM userland): install, login to NetEase's servers, LAN client internet and DNS via this machine, automatic restart after the plugin crashes (stale guardian process cleaned up), start on boot, uninstall
- Upgrade from the old directory layout (
/opt/uu/musl/lib) to per-architecture directories - Non-4K page kernel: on Ubuntu's 64K-page arm64 kernel (QEMU VM) the plugin and guardian run normally and log in to NetEase's servers
- Dual-stack network: AAAA queries to this machine return no addresses while A queries work; no IPv6 forwarding or router advertisements; leftover IPv6 forwarding rules from the earlier RA-based version are removed on upgrade
Docker image (Docker on an arm64 host, container on a bridge network as the LAN):
- arm64 and arm/v7 images: SN file generated on first start, plugin downloaded and logged in (
uu_status=0), plugin iptables rules added --privileged(like RouterOS) and unprivileged (NET_ADMIN+/dev/net/tun+--sysctl); nft and legacy iptables backends- A LAN client with gateway/DNS pointed at the container gets internet access; AAAA filtering; environment variables override
uu.conf - Restart reuses the cached package from
/etc/uu/cache; an SN file with the wrongproductnameis corrected and the right plugin downloaded;docker stopstops the plugin and dnsmasq cleanly - Not verified: an actual RouterOS device, macvlan (
docker-compose.yml)
amd64 image (QEMU emulation, see x86_64):
- Same image layout built for arm64 (the plugin still runs through the bundled
qemu-aarch64): plugin downloaded, started under QEMU together with the guardian (/proc/PID/exeis QEMU, process namesuuplugin/xuplugin-guardi), logged in (uu_status=0), plugin iptables rules added,uuctl restartanddocker stopwork - Patched vs. stock QEMU with a test program:
SO_MARK,IP_MTU,IP_TRANSPARENT,SO_ORIGINAL_DSTandNETLINK_NETFILTERonly work with the patch; TUN creation and interface ioctls work with both - CI runs
docker/test-amd64.shon an x86_64 runner without binfmt_misc for aarch64 - Not verified: real acceleration through the emulated plugin, CPU usage under game traffic
Not verified: binding in the phone app and real game acceleration (requires a real LAN, a UU account and game devices); please test after deployment.