Chaosnet wiki

The global Chaosnet site

User Tools

Site Tools


The global Chaosnet

This describes the global, interconnected, Chaosnet.

1. Routing

A Chaosnet bridge runs on (the IP, IPv6, and Chaos) host MX-11.Chaosnet.NET (also under the alias Router.Chaosnet.NET), accessible by UDP or TLS on port 42042, or using IP protocol 16 (over IPv4 or IPv6), as Chaos host 3040.

The MX-11 bridge

  • routes packets between connected networks,
  • sends and processes Chaosnet routing (RUT) packets to connected networks (and CHUDP hosts), and
  • responds to the contact names STATUS, TIME, UPTIME and DUMP-ROUTING-TABLE, among others.

See here (or MIT AI Memo 628) for more details about the protocols.

2. Registering

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 (see here for instructions).

2.1 If you want to connect a single host

A single host can be connected if it can use a non-local link layer, i.e. Chaos-over-{ TLS, UDP, IP, IPv6 }. To connect a host which only uses Ethernet or unix sockets, you need to set up a local network and a cbridge (see next section).

To get a compatible Chaosnet address, send an email to and tell me

  • the name of the host, including its domain (but do not just invent domains - see below),
  • what kind of host it is (ITS? Lambda/Explorer/Symbolics Lisp machine? cbridge?), and
  • on what IP it is (IPv4 or IPv6). (If you don't have a stable address, you need to use TLS).

You should (most likely) have an address on subnet 6 (range 3001-3377). (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 and pick a free one, but don't forget to tell Björn as soon as possible. And pick one on net 6 (range 3001-3377).

2.2 If you want to connect your local Chaos network

Set up a cbridge to handle your local network. Tell Björn the things as above about your cbridge host, and also ask Björn for a separate subnet to use (in emergencies, pick a subnet between 17 and 171 octal, avoiding those listed below - and 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

  • the names of the hosts, including domains (but do not just invent domains - see below),
  • what kinds of hosts they are, and
  • their Chaosnet addresses on your subnet.

2.3 Dynamic Chaosnet address allocation

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.

3. If you don't have a domain

You can ask to get added to Chaosnet.NET.

4. Configuration examples

Some simple examples - see also here.

To configure your ITS running under klh10 to connect directly to the global net, use this in your klh10.ini:

devdef chaos ub3 ch11 addr=764140 br=6 vec=270 myaddr=NNNN chip=3040/

where NNNN is your Chaosnet address on net 6 (3001-3377). (You need to tell me about it so I can open the firewall.)

To configure your ITS to connect through your cbridge, use this:

devdef chaos ub3 ch11 addr=764140 br=6 vec=270 myaddr=NNNN chip=MMMM/a.b.c.d

where NNNN is your local subnet address of the ITS, and MMMM is the local subnet address of your cbridge, and a.b.c.d is the IP of your cbridge. For cbridge.conf, use link chudp a.b.c.X host NNNN where a.b.c.X is the (local) IP of the klh10/ITS.

If your klh10/ITS and your cbridge run on the same host, you need to use different UDP ports for them. For example, you can change the klh10 config to use port 42043 by using

devdef chaos ub3 ch11 addr=764140 br=6 vec=270 myaddr=NNNN chip=MMMM/a.b.c.d chudpport=42043

and then use link chudp a.b.c.X:42043 host NNNN in cbridge.conf.

5. Subnets in use

The following subnets (in octal) are used/registered or special. See also AI:SYSHST;HSTNET > for historical use.

Note that while there are technically 255 subnets (excluding 0), only 172 (octal) different nets fit in a routing table pkt, and the DUMP-ROUTING-TABLE protocol only lists subnets up to 172.

#1: Update Computer Club

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. Used for the Chaos-over-Ethernet at Update, because the old Symbolics 3600 has address 401.

#6: Global Chaosnet hub network

This is for hosts connected to MX-11 by Chaosnet over UDP (CHUDP), IP (v4/v6) or over TLS, mainly ITS hosts and cbridge processes.

Side note: MX-11 was a Chaos gateway at MIT; one of its addresses was 3040 which is on net 6; address 3040 is the default for routes in ITS, see SYSTEM;CHAOS >.

#7: Victor network

Special: Default subnet for LMI machines; 3412 used by LMI machines for “Amnesia” (hosts that don't know their address). BVs home network, over Ethernet and Unix sockets.

#10: Bogodyne Metatechnics LLC

Allocated for Bogodyne Metatechnics LLC.

#11: AMS network

AMS' home network (AMS.Chaosnet.NET).

#13: Swenson network

Eric Swenson's network.

#16: GEWT network

Used by SJ.GEWT.NET.

global.txt · Last modified: 2020-12-16 09:29 by victor