Proxy

The Code tab in Claude Desktop can add an SSH connection and run Claude Code on a remote server. The app uploads the program to the server itself and takes care of authentication, so you don’t need to install Claude on the server or sign in there. The catch: if the server’s outbound connection can’t reach Anthropic (a server in a region Anthropic doesn’t serve, such as Hong Kong, gets refused), or you want to pin it to a specific egress, the remote Claude can’t send its requests. The fix is to give Claude on the server its own proxy. It only affects Claude and leaves the rest of the machine’s networking alone. ...

A separate subnet on OpenWrt, bound to its own SSID, with source-based policy routing that sends the entire subnet to a mihomo TUN gateway sitting on a different subnet. Clients configure nothing: join the SSID and traffic is proxied, switch back to the main WiFi and it is direct again. There is one well-hidden trap at the end — ImmortalWRT’s DNS redirect. The gateway itself is built in the previous post: Running mihomo as a LAN gateway with Docker macvlan. ...

I run mihomo in Docker on an N95 mini PC. macvlan gives the container its own LAN address (10.0.0.6), so any device that points its default gateway there gets rule-based proxying — without touching the router’s own routing table. Two things bite you once the container is up: the host and its own macvlan containers cannot reach each other, and you still have to decide how clients switch over to the new gateway. This post covers both. ...