Connect to the game network
Set up your WireGuard tunnel, register your SSH key, and reach your team's box and everyone else's services.
Every box and service in the game sits on a private network. You reach it over a WireGuard tunnel that the event site issues to you personally. You need a place on an admitted team first; see Create or join a team.
Get your VPN config
Open Downloads and click Download VPN config. The site generates a key pair for you and hands you the private half once, inside athena-vpn.conf. Save it immediately; it can’t be shown again.
If you lose it, click Regenerate VPN config. You get a new key at the same address, and the old key stops working.
Each player has their own config. Don’t share yours with teammates: they can download their own.
Bring the tunnel up
With WireGuard installed:
sudo wg-quick up ./athena-vpn.conf
and sudo wg-quick down ./athena-vpn.conf to disconnect. The WireGuard desktop and mobile apps import the same file.
The tunnel routes only the game network. Your normal internet traffic, and the event site itself, stay on your usual connection.
Register your SSH key
Open My box, paste one OpenSSH public key on one line (such as ssh-ed25519 AAAA… you@laptop) under SSH keys and click Register key. Ed25519, ECDSA (P-256, P-384 or P-521), RSA of at least 2048 bits and security-key (sk-ssh-ed25519, sk-ecdsa-sha2-nistp256) keys are accepted. A team can have at most 64 active keys between all its members; revoke one to make room for another. Keys are applied to your team’s box within a short time.
The list shows every key registered for your team. Revoke appears next to your own keys and removes that key from the box. An organizer can revoke a key too; register a new one if that happens.
When access stops working
Your VPN config and SSH keys belong to you on your current team. They stop working on the team’s box when you leave the team, a leader removes you, or your account is suspended, and they don’t come back if you rejoin. Download a new VPN config and register your keys again once you’re back on an admitted team.
Reach your box
My box shows your box’s Address. Log in as root:
ssh root@<address>
You have root inside the box, and your services run in it as Docker containers. Port 22 on your own box is for your team only; nobody else can reach it.
Reach other teams
Once the network opens, every team’s services are reachable on their published ports. Team n’s box is at 10.60.<n−1>.1: team 1 at 10.60.0.1, team 2 at 10.60.1.1, and so on. Attack info and the scoreboard identify teams by the same number. Before the network opens, only your own box answers.