global
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| global [2024-07-02 08:37] – [2.2 If you want to connect your local Chaos network] victor | global [2025-11-04 08:29] (current) – [2. Registering] victor | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ===== - Routing ===== | ===== - Routing ===== | ||
| + | A [[https:// | ||
| - | A [[https:// | + | 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, | ||
| - | The MX12 bridge | + | See [[protocol# |
| - | * 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, | + | |
| - | + | ||
| - | See [[protocol# | + | |
| ===== - Registering ===== | ===== - Registering ===== | ||
| - | To connect to the " | + | To connect to the " |
| + | * To connect using Chaos-over-UDP, | ||
| + | * To connect using Chaos-over-TLS, | ||
| + | I strongly recommend that you join the chaosnet-hackers[at]its.victor.se mailing list. | ||
| ==== - If you want to connect a single host ==== | ==== - 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). | + | 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). Unless there are very special circumstances, |
| To get a compatible Chaosnet address, send an email to bjorn@victor.se and tell me | To get a compatible Chaosnet address, send an email to bjorn@victor.se and tell me | ||
| * the name of the host, including its domain (but do not just invent domains - see below), | * the name of the host, including its domain (but do not just invent domains - see below), | ||
| * what kind of host it is (ITS? Lambda/ | * what kind of host it is (ITS? Lambda/ | ||
| - | * on what IP it is (IPv4 or IPv6). (If you don't have a stable address, you need to use TLS). | + | * on what IP it is (IPv4 or IPv6), if it is stable. (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.) | 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.) | ||
| Line 41: | Line 43: | ||
| * their Chaosnet addresses on your subnet. | * their Chaosnet addresses on your subnet. | ||
| - | **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. | + | < |
| ==== - Dynamic Chaosnet address allocation ==== | ==== - 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. | 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. | ||
| Line 51: | Line 53: | ||
| ===== - Configuration examples ===== | ===== - Configuration examples ===== | ||
| - | For configuration examples, please see also [[https:// | + | For configuration examples, please see [[https:// |
| ===== - Subnets in use ===== | ===== - Subnets in use ===== | ||
| - | The following subnets (in octal) are used/ | + | The following subnets (in octal) are used/ |
| To generate host tables in various form (when you can't use DNS), try [[https:// | To generate host tables in various form (when you can't use DNS), try [[https:// | ||
| Line 71: | Line 73: | ||
| == #7: Victor network (hosts 3401-3777) == | == #7: Victor network (hosts 3401-3777) == | ||
| Special: Default subnet for LMI machines; 3412 used by LMI machines for " | Special: Default subnet for LMI machines; 3412 used by LMI machines for " | ||
| - | BVs home network, over Ethernet, IP, and Unix sockets. | + | BVs home network, over Ethernet, IP, UDP, and Unix sockets. |
| == #10: Bogodyne Metatechnics LLC (hosts 4001-4377) == | == #10: Bogodyne Metatechnics LLC (hosts 4001-4377) == | ||
| Line 84: | Line 86: | ||
| == #14: N3UC network (hosts 6001-6377) == | == #14: N3UC network (hosts 6001-6377) == | ||
| Michael Wyrick' | Michael Wyrick' | ||
| + | |||
| + | == #15: 9grid network (hosts 6401-6777) == | ||
| + | John Floren' | ||
| == #16: GEWT network == | == #16: GEWT network == | ||
| Used by SJ.GEWT.NET (a long time ago now). | Used by SJ.GEWT.NET (a long time ago now). | ||
| + | |||
| + | == #27: Victor network too == | ||
| + | A second subnet for BV. | ||
| == #37: Sanyalnet (hosts 17401-17777) == | == #37: Sanyalnet (hosts 17401-17777) == | ||
| Sanyal Supratim' | Sanyal Supratim' | ||
| + | |||
| + | == #54: Z54 network (hosts 26001-26377) == | ||
| + | Mete Balci' | ||
| == #376: Private non-routed network (hosts 177001-177377) == | == #376: Private non-routed network (hosts 177001-177377) == | ||
global.1719902230.txt.gz · Last modified: by victor
