Bakeathon network info

Join remotely with Tailscale

Remote participants join the event network with the standard Tailscale client, pointed at our own control server.

Required version: Tailscale 1.80 or newer (older clients are rejected). Check with tailscale version.

Linux / BSD

sudo tailscale up --login-server=https://headscale.nfsv4.dev --accept-routes --accept-dns

macOS / Windows

tailscale login --login-server=https://headscale.nfsv4.dev

macOS and Windows accept routes and DNS by default. On macOS the CLI is /Applications/Tailscale.app/Contents/MacOS/Tailscale if tailscale isn't on your PATH.

Logging in

The command prints a URL. Open it and sign in with Google, or with a Bakeathon account: use Register on the login page, with your email as the username (you'll get a verification email). Returning participants keep their previous node and address.

Node keys last 180 days. If yours has expired, just run the command again.

Check that it works

tailscale status
tailscale ping batman
ping ipa.nfsv4bat.org

Tailnet

Addresses100.64.0.0/10, fd7a:115c:a1e0::/48
DNS100.100.100.100 (MagicDNS)
Domainnfsv4bat.org: tailnet nodes are <hostname>.nfsv4bat.org, the same domain as the room
Room access172.16.0.0/16 is routed through batman (needs --accept-routes on Linux)
Control serverhttps://headscale.nfsv4.dev

MagicDNS answers tailnet names itself and forwards other nfsv4bat.org names (room hosts, Kerberos/LDAP SRV records) to the room DNS server. If you use --accept-dns=false, point nfsv4bat.org at 100.64.0.40 yourself.

In-room network

Network172.16.0.0/16 (netmask 255.255.0.0)
Gateway172.16.0.1 (batman)
DNS172.16.0.1
DHCP pool172.16.1.0 – 172.16.1.253
Domainnfsv4bat.org
Static addresses: wired hosts must use 172.16.0.1 as their default gateway, or remote tailnet participants can't reach them.

Company subnets

Each company has a /24 inside the room's /16. Address 172.16.N.x is named <company>-x.nfsv4bat.org. Room DNS is IPv4-only.

CompanySubnetHost namesRDMA networks
Red Hat172.16.3.0/24redhat-xib 172.17.3.x · vlan 172.18.3.x · roce 172.19.3.x
Oracle172.16.5.0/24oracle-xib 172.17.5.x · vlan 172.18.5.x · roce 172.19.5.x
Hammerspace172.16.10.0/24hs-x
IBM172.16.11.0/24ibm-x
Meta new172.16.12.0/24meta-xib 172.17.12.x · vlan 172.18.12.x · roce 172.19.12.x
Everpure new172.16.13.0/24everpure-x

RDMA names live in sub-domains, e.g. meta-7.ib.nfsv4bat.org. Other reserved subnets: freebsd .2, ms .4, netapp .6, desy .7, cea .8, dell .9.

Kerberos

RealmNFSV4BAT.ORG
KDCkdc.nfsv4bat.org (172.16.0.1), also discoverable via DNS SRV records
LDAPipa.nfsv4bat.org (172.16.0.2)
Client config & keytabsbatman.nfsv4bat.org:/export: krb5.conf and keytabs/

Get a host keytab (self-serve)

Open http://batman.nfsv4bat.org/keytab/. It's only reachable from the room network or the tailnet; tailnet users without routes can use http://100.64.0.40/keytab/.

  1. Enter the host's name (e.g. redhat-20 or steved-f44; it must exist in room DNS) and download the keytab. It holds host/<name>.nfsv4bat.org and nfs/<name>.nfsv4bat.org.
  2. Copy it to the host. Headless hosts are fine: download anywhere, then scp it over.
  3. On the host, install the keytab and the client config, and check it:
sudo install -m 600 redhat-20.keytab /etc/krb5.keytab
sudo curl -fsS -o /etc/krb5.conf.d/bakeathon.conf http://batman.nfsv4bat.org/keytab/krb5.conf
klist -ke /etc/krb5.keytab
sudo kinit -k host/$(hostname -s).nfsv4bat.org && klist

Or straight from a shell on the room network or tailnet:

curl -fsS -o redhat-20.keytab http://batman.nfsv4bat.org/keytab/redhat-20
sudo mount batman.nfsv4bat.org:/export /mnt

User keytabs and key rotation (e.g. after a reinstall or a leaked keytab): contact Ben Coddington.

TLS (RPC-with-TLS certificates)

Self-serve: http://batman.nfsv4bat.org/pki/ (room network or tailnet only; without routes use http://100.64.0.40/pki/). Certificates are issued immediately by the Bakeathon CA, valid for one year.

  1. On your host, make a key and a CSR. The page builds the commands for ED25519, ML-DSA-65 (post-quantum), RSA or ECDSA. Use <host>.nfsv4bat.org as the name (CN and subjectAltName); room or tailnet IPs may be added too.
  2. Upload or paste the CSR, choose server + client, and download the two certificates. Or from a shell:
curl -fsS --data-binary @host.csr 'http://batman.nfsv4bat.org/pki/sign?profile=both' -o host.certs.pem
  1. Install the CA bundle, then point /etc/tlshd.conf at your key and certificates and restart tlshd:
sudo curl -fsS -o /etc/pki/ca-trust/source/anchors/bakeathon-ca.pem http://batman.nfsv4bat.org/pki/ca-chain-bundle.cert.pem
sudo update-ca-trust

Debian/Ubuntu: save it as /usr/local/share/ca-certificates/bakeathon-ca.crt and run sudo update-ca-certificates.

Revocation or a lost key: contact Ben Coddington or Chuck Lever.