This describes various resources for the “global” Chaosnet. Other source of information include
Chaosnet implementations include
A DNS server for CHaosnet class data is available at Psilocybe.Update.UU.SE. It currently runs the following domains:
and the root domain, so assumedly knows everything about Chaosnet.
Network names appear in CH-ADDR.NET, in the spirit of RFC 1101. They are at labels corresponding to the subnet address with zero host part, e.g. 400.ch-addr.net for subnet 1, 3000.ch-addr.net for subnet 6, etc.
If you have a stable IP address, constantly running machine, which is publicly accessible on port 53, you can be a secondary nameserver. That would be helpful, as it improves redundancy and performance.
To make use of DNS in ITS, see dqdev - more work is needed to adapt more networking programs. To make use of DNS on an LMI Lambda or TI Explorer lisp machine, use my DNS resolver implementation (which also plays nicely with my DHCP implementation).
In the Chaosnet bridge program, there is support for a DNS server over Chaosnet (by forwarding/recursion over UDP) so Chaos-only hosts can make use of it. This should allow non-IP hosts such as CADR systems to make use of DNS.
The MX-11 bridge
To connect to the “global” Chaosnet, you need to register a compatible Chaosnet address. To connect using Chaos-over-UDP, you need a stable IP address and a compatible Chaosnet address, and if you connect directly to MX-11, I need to open the firewall there. To connect using Chaos-over-TLS, you do not need a stable IP address, but you do need a certificate issued by my Certificate Authority.
To get a compatible Chaosnet address, send an email to email@example.com and tell me
If you connect using Chaos-over-UDP, you should probably have an address on subnet 6 (range 3001-3377), at least if you have a reasonably stable host. (Ideally, run a cbridge and put your local hosts on a subnet behind it - see configuration examples below.)
In emergencies, you can list occupied addresses e.g. by
host -c ch -l ch-addr.net. psilocybe.update.uu.se and pick a free one, but don't forget to tell Björn as soon as possible. And to keep things simple, pick one on net 6.
Set up a cbridge to handle your local network. Tell Björn the things as above for single hosts, and also ask Björn for a separate subnet to use (in emergencies, pick a random subnet between 17 and 171 octal - but don't forget to tell Björn!). Do NOT add all your local hosts to subnet 6, but only the cbridge. See configuration examples below.
To add DNS info, send Björn
I'm thinking about this. The old WHO-AM-I and TI-WHO-AM-I protocols are not quite sufficient, and full-blown DHCP is a bit overkill.
You can ask to get added to aosnet.CH.
To configure your ITS running under klh10, use this in your klh10.ini:
devdef chaos ub3 ch11 addr=764140 br=6 vec=270 myaddr=NNNN chip=3040/router.aosnet.ch
where NNNN is your Chaosnet address on net 6 (3001-3377). (You need to tell me about it so I can open the firewall.)
More might appear, also see here.
The following subnets (in octal) are used/registered or special. See also AI:SYSHST;HSTNET >.
Note that while there are technically 255 subnets (excluding 0), only 172 nets fit in a routing table pkt, and the DUMP-ROUTING-TABLE protocol only lists subnets up to 172.
Special: the TI-WHO-AM-I protocol broadcasts on that subnet to find out its address, and it is probably often default for old Real machines, e.g. Lispms. Currently used for the Chaos-over-Ethernet at Update, because the old Symbolics 3600 has address 401.
This is now for hosts connected to MX-11 by Chaos-over-UDP (CHUDP), mainly ITS hosts and cbridge processes.
Special: Default subnet for LMI machines; 3412 used by LMI machines for “Amnesia” (hosts that don't know their address). Currently BVs home network, over Ethernet and Unix sockets.
Currently AMS' home network (AMS.AOSNET.CH).
Used by Eric Swenson for the home network.
Used by SJ.GEWT.NET (and MX-11 bridges to it).