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
--accept-routesis required on Linux, both to reach the in-room network (172.16.0.0/16) and for in-room hosts to reach you (room traffic arrives from its real 172.16.x address). It's off by default there. Already joined? Runsudo tailscale set --accept-routes.--accept-dnslets MagicDNS resolve both tailnet and in-room names. If you run your own resolver, see DNS.- Set a sensible hostname before joining. Your DNS name becomes
<hostname>.nfsv4bat.org, which Kerberos host principals depend on.
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
| Addresses | 100.64.0.0/10, fd7a:115c:a1e0::/48 |
| DNS | 100.100.100.100 (MagicDNS) |
| Domain | nfsv4bat.org: tailnet nodes are <hostname>.nfsv4bat.org, the same domain as the room |
| Room access | 172.16.0.0/16 is routed through batman (needs --accept-routes on Linux) |
| Control server | https://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
| Network | 172.16.0.0/16 (netmask 255.255.0.0) |
| Gateway | 172.16.0.1 (batman) |
| DNS | 172.16.0.1 |
| DHCP pool | 172.16.1.0 – 172.16.1.253 |
| Domain | nfsv4bat.org |
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.
| Company | Subnet | Host names | RDMA networks |
|---|---|---|---|
| Red Hat | 172.16.3.0/24 | redhat-x | ib 172.17.3.x · vlan 172.18.3.x · roce 172.19.3.x |
| Oracle | 172.16.5.0/24 | oracle-x | ib 172.17.5.x · vlan 172.18.5.x · roce 172.19.5.x |
| Hammerspace | 172.16.10.0/24 | hs-x | |
| IBM | 172.16.11.0/24 | ibm-x | |
| Meta new | 172.16.12.0/24 | meta-x | ib 172.17.12.x · vlan 172.18.12.x · roce 172.19.12.x |
| Everpure new | 172.16.13.0/24 | everpure-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
| Realm | NFSV4BAT.ORG |
| KDC | kdc.nfsv4bat.org (172.16.0.1), also discoverable via DNS SRV records |
| LDAP | ipa.nfsv4bat.org (172.16.0.2) |
| Client config & keytabs | batman.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/.
- Enter the host's name (e.g.
redhat-20orsteved-f44; it must exist in room DNS) and download the keytab. It holdshost/<name>.nfsv4bat.organdnfs/<name>.nfsv4bat.org. - Copy it to the host. Headless hosts are fine: download anywhere, then
scpit over. - 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
- Hosts that already have principals get their current keys, so existing copies keep working; new names are created automatically.
- Already have other principals in
/etc/krb5.keytab? Merge instead of replacing:printf 'rkt redhat-20.keytab\nwkt /etc/krb5.keytab\n' | sudo ktutil - Every issued keytab is also saved to
batman.nfsv4bat.org:/export/keytabs/, alongside the clientkrb5.conf:
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.
- 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.orgas the name (CN and subjectAltName); room or tailnet IPs may be added too. - 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
- Install the CA bundle, then point
/etc/tlshd.confat your key and certificates and restarttlshd:
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.
- Classic and post-quantum: make two keys and two CSRs (e.g. ED25519 and ML-DSA-65) and submit each; every key type gets its own pair of certificates.
- Extra names are ignored: names in your CSR that aren't valid here (other domains, old
…nfsv4.devnames, non-room IPs) are left out of the certificate, as long as at least one<host>.nfsv4bat.orgname is present. The result page lists what was left out. - Copies: every issued certificate is also saved to
batman.nfsv4bat.org:/export/certs/<host>.nfsv4bat.org.<keytype>.<server|client>.cert.pem(keytype e.g.ed25519,mldsa65,rsa3072), and the CA bundle to/export/ca-chain-bundle.cert.pem. A new request with the same key type replaces that pair. - Older certificates issued by hand stay valid (same CA); they're at
oracle-102.nfsv4bat.org:/export/certs/. If yours names an old…nfsv4.devhost, just request a new one here.
Revocation or a lost key: contact Ben Coddington or Chuck Lever.