Verify It Works

After setting up the hub and at least one exit node, verify that traffic is actually routed through your device.

The Test

On your server (where the hub runs):

curl --proxy socks5://localhost:1080 https://httpbin.org/ip

Expected: The IP address in the response is your exit node's IP (your phone's carrier IP, your home broadband IP, etc.) — not the server's datacenter IP.

Compare

# Direct from server — shows the datacenter IP
curl https://httpbin.org/ip

# Through Restunnel — shows the exit node's residential IP
curl --proxy socks5://localhost:1080 https://httpbin.org/ip

If both return the same IP, the proxy isn't routing through the exit node. Check that:

1. The exit node is connected (check hub logs or the dashboard)
2. You're using the correct proxy port (default :1080 for SOCKS5, :1081 for HTTP CONNECT)

Named Node Selection

If you have multiple exit nodes, you can route through a specific one:

# Route through the node labeled "vienna-home"
curl --proxy socks5://vienna-home:x@localhost:1080 https://httpbin.org/ip

See Node Selection for more details.

HTTP CONNECT

The hub also provides an HTTP CONNECT proxy on port 1081:

curl --proxy http://localhost:1081 https://httpbin.org/ip

Both proxy protocols route through the same exit nodes. Use whichever your tools support.