Roles & Topology

Each wallhack node operates as one of three roles. Roles are assigned automatically based on your network topology — see Zero Config for how negotiation works.

Entry

Runs on the attacker's machine. Creates a TUN interface — a virtual network device — that routes traffic into the tunnel chain. Any traffic sent to a routed subnet arrives here and is forwarded onward. ICMP echo requests are forwarded through the tunnel, so ping works to addresses on the target network.

wallhack

info: Listening on :6565 (QUIC)
info: Certificate fingerprint: sha256:a1b2c3...

Exit

The far end of the chain. Packets are unwrapped and delivered into the target network. No TUN interface required.

wallhack --connect HOST:PORT

info: Connecting to HOST:PORT...
info: Connected to HOST:PORT

Relay (optional)

An intermediate host. Connects to a previous hop and listens for the next. Used for multi-hop pivoting through segmented networks where no direct path exists between entry and exit.

wallhack --connect HOST:PORT --listen :PORT

info: Connecting to HOST:PORT...
info: Connected to HOST:PORT
info: Listening on :PORT (QUIC)

Transport direction (--listen / --connect) is independent of role — entry and exit nodes can either listen or connect, which is how reverse tunnels work.