Also see nullroute hosts.
Nullroute doesn't run anything serious, it is just a place for experiments. This means that servers come and go, the services are often misconfigured, the only account is "
grawity", and there really isn't anything worth offering.
That said, I've learned a lot by simply tinkering around with various network services. And it's much easier to study a working implementation than hundreds of pages of RFCs, so that's what I'm doing here. (Much like other people pretend they run an army of elves…)
I sometimes grab copies of various old websites or FTP sites (frequently just weeks before they go down). A few of those are accessible as mirrors.
I'm AS4242423827 on the dn42 network, and AS206633 on the Internet.
Three's a small collection of interesting Usenet and mailing-list posts which is accessible through anonymous IMAP, at
imap://email@example.com/Public and subdirectories.
Central configuration for my servers – user accounts, NIS databases, other stuff – is kept in an LDAP directory at
dc=nullroute,dc=eu,dc=org, sneakily replicated over Cluenet core servers (which also host the
dc=cluenet,dc=org tree), most of which is anonymous-readable.
The network has a Kerberos 5 realm
NULLROUTE.EU.ORG, with cross-realm links to CLUENET.ORG, KYRIASIS.COM, and NATHAN7.EU (with their owners being vaguely aware of this). The Kerberos database is also stored in LDAP, as OpenLDAP syncrepl is much fancier than native MIT Krb5 "kprop" (which so far has depended on cron-based polling).
Some services on the network use X.509 certificates from the internal NullCA, or OpenSSH certificates from SSH CA.
I've also tried to set up BrowserID, RADIUS, SAML, TACACS, and probably a few more protocols that I can't remember. Things I learned trying to make FreeRADIUS work turned out to be quite useful at my day job just two weeks later…
Other things that may or may not be running at any particular moment: