Cluenet.org was a community of computer enthusiasts and other users who came together, pooled resources, and created a distributed infrastructure of servers and services. In other words, it was a "shell account" site. (Not to be confused with the ClueNet.DE ISP, which was run by different people.)
Though the website still exists and some infrastructre is remaining, the project in general had been slowly dying for many years and is now officially closed.
Archived sites:
What I remember, or have gathered from logs:
#chules.net and #clueirc exist on clueirc.net
#clueirc consists of 100–200 people, plus some in the semi-related Arbelos Services channel.
#clueirc (although grawity still keeps LDAP & Kerberos running). Approx. 5 active members and 30 persistent lurkers.
#clueirc, the last remaining service that still was online (and only barely).
A snapshot of an old draft summarizing the Cluenet infrastructure:
ClueIRC is the IRC component of Cluenet. To get a Cluenet account, IRC participation is required, to strengthen the community.
Most services authenticate against Kerberos 5. Services incapable of Kerberos can authenticate by binding to the LDAP server.
CLUENET.ORG
kerberos.cluenet.org
User accounts are kept in an LDAP server. Most servers run their own LDAP mirrors using OpenLDAP's syncrepl.
ldap://ldap.cluenet.org (TLS enabled)
dc=cluenet,dc=org
"Old" authorization mechanism: authorizedService and/or host attributes on user's LDAP entry, checked by Debian's pam_ldap in default configuration. Still used for some services, but considered too inflexible for shell server access.
"New" mechanism as of 2009 – separate ACLs for each server/service pair in LDAP at cn=service,cn=svcAccess,cn=fqdn,ou=servers,dc=cluenet,dc=org, checked by nss-pam-ldapd.
Most Cluenet servers are part of ClueVPN, a mesh VPN using the cluevpn software written by Crispy. For those unable or unwilling to run cluevpn, Equal runs an OpenVPN server. The VPN is IPv4-only, since it's primary purpose is to get around problems created by servers being behind NATs; the biggest ones being lack of reverse DNS (required by Kerberos) and messy port-forwarding.
The VPN uses addresses in 10.156.0.0/16 space, and allocation is managed through the Cluenet website. OpenVPN gateway uses 10.156.210.0/24.