vovan/hamachi-proxy repository overview

SOCKS5 proxy reachable only via a Hamachi (LogMeIn) VPN network. Run in country A, connect from country B, exit with A's IP.

Source & docs: https://github.com/vovanmozg/hamachi-proxy-docker⁠

• Bound to ham0 only — never exposed to the public internet
• Access barrier = Hamachi network ID + password (no SOCKS5 auth, since most Chrome SOCKS extensions don't implement RFC 1929)
• Outbound to RFC1918 / link-local / loopback is blocked (no LAN pivot)
• amd64 only (Hamachi ships no other arch)

⁠Run

docker-compose.yml:

services:
  hamachi-proxy:
    image: vovan/hamachi-proxy:latest
    container_name: hamachi-proxy
    restart: unless-stopped
    cap_add: [NET_ADMIN]
    devices: ["/dev/net/tun:/dev/net/tun"]
    volumes: ["./hamachi-state:/var/lib/logmein-hamachi"]
    dns: ["1.1.1.1", "8.8.8.8"]
    environment:
      HAMACHI_NETWORK_ID:       ${HAMACHI_NETWORK_ID:?set in .env}
      HAMACHI_NETWORK_PASSWORD: ${HAMACHI_NETWORK_PASSWORD:?set in .env}
      HAMACHI_NICK:             ${HAMACHI_NICK:?set in .env}

.env next to it (mode 0600):

HAMACHI_NETWORK_ID=my-unique-network-id
HAMACHI_NETWORK_PASSWORD=long-random
HAMACHI_NICK=my-proxy-server

docker compose up -d

State lives in ./hamachi-state/ (bind mount, survives docker compose down -v and docker volume prune). On first run the container does hamachi login, sets the nick, and creates the network. Watch docker compose logs -f until you see:

[entrypoint] ready — SOCKS5 at 25.x.x.x:1080 ...

The 25.x.x.x is your server's ham0 IP — share it with clients.

⁠Client

1. Install Hamachi: https://vpn.net/⁠
2. hamachi login && hamachi do-join "$HAMACHI_NETWORK_ID" "$HAMACHI_NETWORK_PASSWORD"
3. SOCKS5 in browser / OS: host=<server-ham0-ip> port=1080 (no auth)

Firefox: enable Proxy DNS when using SOCKS v5 to avoid DNS leaks.

⁠Tuning

Defaults HAM0_MTU=1280 / HAM0_MSS=1200 work on tight paths (mobile, NAT). Raise via container env for more throughput on clean paths.