====== - The global Chaosnet ======
This describes the global, interconnected, Chaosnet. If you just want to set up a local Chaosnet, please see [[local|here for instructions]].

To see what hosts are up on the global Chaosnet, see [[http://up.dfupdate.se/cha/hostat.html|here]]. To see who is logged in on Chaosnet hosts, see [[http://up.dfupdate.se/cha/finger.html|here]].
===== - Routing =====

A [[https://github.com/bictorv/chaosnet-bridge|Chaosnet bridge]] runs on (the IP, IPv6, and Chaos) host MX12.Victor.SE, accessible by [[protocol#tls|TLS]] on port 42042, or using [[protocol#ip_standard|IP protocol 16]] (over IPv4 or IPv6), as Chaos host 3040. Another bridge is running on Chaos.Swenson.ORG (also accessible as Router.Chaosnet.NET), accessible by TLS on port 42042. For convenience, ''Router.Chaosnet.NET'' has both the IPs of MX12.Victor.SE and Chaos.Swenson.ORG.

Both bridges
  * route packets between connected networks,
  * send and process Chaosnet routing (RUT) packets to connected networks (and CHUDP hosts), and
  * respond to the contact names STATUS, TIME, UPTIME and DUMP-ROUTING-TABLE, [[https://github.com/bictorv/chaosnet-bridge/blob/master/doc/CONTACTS.md|among others]].

See [[protocol#application_layer|here]] (or [[https://chaosnet.net/amber.html|MIT AI Memo 628]]) for more details about the protocols.

===== - Registering =====

To connect to the "global" Chaosnet, you need to register a compatible Chaosnet address. **In the normal case, you should connect using Chaos-over-TLS.** 
  * <del>To connect using Chaos-over-UDP, you need a stable IP address and a compatible Chaosnet address, and if you connect directly to MX12 using CHUDP, I need to open the firewall there.</del> 
  * 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 [[https://github.com/bictorv/chaosnet-bridge/blob/master/doc/TLS.md|here]] for instructions).

I strongly recommend that you join the chaosnet-hackers[at]its.victor.se mailing list.


==== - To connect your local Chaos network ====

Set up a [[https://github.com/bictorv/chaosnet-bridge|cbridge]] to handle your local network. Tell Björn the things as below about your cbridge host, and also ask Björn for a separate subnet to use. Do NOT add all your local hosts to subnet 6, but only the cbridge (whose address you get from Björn). See configuration examples below.

To add DNS info (which is mandatory), send Björn
  * the names of the hosts, including domains (but do not just invent domains - see below),
  * what kinds of hosts they are (ITS? Lambda/Explorer/Symbolics Lisp machine? TOPS-20? cbridge? etc), and
  * their Chaosnet addresses on your subnet.

<note>**Note:** all hosts on your local Chaos network should be registered in the DNS (excepting those on private non-routed networks, see below). So when you add hosts later, send the DNS info to Björn.</note>
==== - 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.

==== - If you don't have a domain ====
You can ask to get added to (a subdomain of) Chaosnet.NET.

I am very reluctant to((Read that as "I will not")) add Chaosnet DNS info for domains none of us are in control of, since they might discover and complain, with possible legal and financial results.

===== - Changing your Chaosnet address =====
After joining the Global Chaosnet, you may need to change the Chaosnet addresses of your local hosts. How you do that of course depends on what kind of operating system and emulator you use.

==== Emulators ====

  * For PiDP-10 systems, which typically run a simh KA emulator, see [[https://github.com/simh/simh/blob/master/doc/ka10_doc.doc|the documentation]] and look for "SET CH NODE=".
  * For ITS under klh10, you need to change the `myaddr` parameter of `devdef chaos`.
  * For CADR systems under usim, you may need to change the `bridgechaos` config (but this info may be outdated).

==== Operating systems ====
  * For TOPS-20, edit `SYSTEM:CHAOSNET.ADDRESS` (no changes are needed for the emulator since TOPS-20 uses Chaos-over-IP).
  * For ITS, you need to edit `SYSHST;H3TEXT` and run `:SYSHST;H3MAKE`, ideally *before* you change the emulator configuration (since ITS might not like it if it doesn't find the name of its address).

You also need to make sure the cbridge configuration matches the changes you do: typically you change `link chudp` (e.g. for PiDP-10 or usim systems) and `link ip` (for TOPS-20) lines.

===== - Configuration examples =====

For configuration examples, please see [[https://github.com/bictorv/chaosnet-bridge/blob/master/doc/EXAMPLES.md|here]].

===== - Subnets in use =====
The following subnets (in octal) are used/registered or special. For historical use, see {{hstnet.51.txt|AI:SYSHST;HSTNET >}}.

To generate host tables in various form (when you can't use DNS), try [[https://github.com/Chaosnet/config-files-from-dns|this tool]]. On the Chaosnet, you can also use the [[protocol#host_lookup_stream|HOSTAB]] server at HOSTAB.Chaosnet.NET.

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 (hosts 401-777) ==
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.
Previously used for the Chaos-over-Ethernet at Update, because the old Symbolics 3600 had address 401. 

== #6: Global Chaosnet hub network (hosts 3001-3377) ==
This is for hosts connected to MX12 by Chaosnet over UDP (CHUDP), IP (v4/v6) or over TLS, mainly ITS hosts and cbridge processes. 

Side note: MX12 is named after MX-11, which 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 [[https://github.com/PDP-10/its/blob/1a6115e949ec6b60a3482c2523216afe1023ab25/src/system/chaos.289#L213|SYSTEM;CHAOS >]].

== #7: Victor network (hosts 3401-3777) ==
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, IP, UDP, and Unix sockets.

== #10: Bogodyne Metatechnics LLC (hosts 4001-4377) ==
Allocated for [[https://www.bogodyne.com/|Bogodyne Metatechnics LLC]].

== #11: AMS network (hosts 4401-4777) ==
AMS' home network (AMS.Chaosnet.NET).

== #13: Swenson network (hosts 5401-5777) ==
Eric Swenson's network.

== #14: N3UC network (hosts 6001-6377) ==
Michael Wyrick's network.

== #15: 9grid network (hosts 6401-6777) ==
John Floren's network.

== #16: GEWT network ==
Used by SJ.GEWT.NET (a long time ago now).

== #17: ThePorch network (hosts 7400-7777) ==
Phillip Porch's network.

== #27: Victor network too ==
A second subnet for BV.

== #37: Sanyalnet (hosts 17401-17777) ==
Sanyal Supratim's network.

== #54: Z54 network (hosts 26001-26377) ==
Mete Balci's network.

== #376: Private non-routed network (hosts 177001-177377) ==

In order to minimise address collisions and routing problems, this subnet has been reserved as a private, non-routed subnet. No routing information about that subnet should be sent outside that subnet, no packets from that subnet should be sent to other subnets, and any packets received from that subnet on another subnet should be dropped.