Hubs and how to connect to them

Whether you need a hub, how to pick one, and config for hub operators.

All guides

Find every hub, with its link block, in the server list, or download them all from /servers/link-blocks.conf?type=Hub.

Do you need a hub?

No. You can link to any server that adds your block. Hubs exist because long link paths caused latency and split problems early on, and they stayed because they're convenient: their admins agreed to keep them up on reliable hosting.

Picking hubs

  • Ping the hubs from your server and autoconnect to the two or three closest. See Additional configs for servers for the class and autoconnect setup.
  • Keep at least one more hub in your config without autoconnect, as a backup an oper can reroute you to.

Running a hub

Only for hub operators. These two blocks keep hubs reachable to each other and keep users off a hub until it has relinked.

except ban stops a G-line from cutting off another hub. List every hub's IP addresses, from the server list:

except ban {
    type { all; }
    mask *@127.0.0.1;
    // one mask per hub address, for example:
    mask *@192.0.2.10;
    mask *@2001:db8::10;
}

deny link refuses links from anything but hubs until you are connected to your upstream:

deny link {
    mask {
        // every hub's name, prefixed with "!"
        !hub-one.example.org;
        !hub-two.example.org;
    }
    // your upstream hubs
    rule !connected(hub-one.example.org) && !connected(hub-two.example.org);
    type all;
}

Update both when hubs join or leave.

Recovered from the old wiki. See the archived page.