Aiden Adds Per-Network Wi-Fi Proxy Routing for Its Device Agent

Major Update: We merged PR #652 in the open-source Aiden firmware repository, adding per-network Wi-Fi proxy routing. The change reduces repeated environment edits when you move Aiden between configured Wi-Fi networks with different connection requirements.

The problem we fixed

Before this update, changing networks could require you to edit proxy environment variables again. Different networks might need a direct connection, a particular proxy protocol, or destinations that bypass the proxy. Reapplying those choices manually made it harder to keep the active environment aligned with the network currently in use.

The merged implementation associates proxy behavior with each configured Wi-Fi network. When the active network changes, managed Aiden paths can refresh against that network’s assigned behavior instead of relying on a repeated manual change.

What changes in Aiden

Config Web’s Wi-Fi connection dialog now supports system default, direct, HTTP, HTTPS, SOCKS5, and SOCKS5H modes for each configured network. It also supports a network-specific NO_PROXY bypass list, so destinations that should not use the proxy can remain separate from proxied traffic.

The active network environment is provided to managed commands and login shells through a local listener at 127.0.0.1:18080. Managed Agent connections refresh when the proxy scheme or bypass rules change. SOCKS5H remains distinct from SOCKS5 because it preserves destination DNS resolution through the proxy.

These settings live with the network definition in Config Web. You can therefore keep one behavior for a home network, another for a restricted network, and a direct mode where a proxy is unnecessary. The implementation describes the supported modes and refresh path in the reviewed firmware change; it does not extend that list to every possible proxy arrangement.

What you can do now

You can associate a proxy policy with each configured Wi-Fi network and let managed Aiden paths adopt the active policy after a network change. Managed commands, login shells, and Agent connections receive a consistent environment without requiring the same proxy values to be edited in several places.

This is useful when the same device moves between networks with different egress rules. A direct connection can remain direct, an HTTP or HTTPS proxy can be selected where required, and SOCKS5 or SOCKS5H can be reserved for networks that need those protocols. NO_PROXY rules can be kept with the network that needs them.

The current boundary

The work in PR #652 is merged repository code with documented validation. Go, system environment, Config Web, shell, and related tests passed, and the firmware binary build passed. Luckfox validation covered service health, the SOCKS5H environment, web access, and a Qwen request.

These results document the reviewed implementation and test path. They do not establish deployment to every Aiden device or product, support for every network or endpoint, or any general privacy, security, speed, or uptime guarantee. Inspect PR #652 for the change record and follow Aiden’s continued open-source development.