| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| start [2024-11-18 11:05] – [2. Who used Chaosnet?] victor | start [2026-04-15 13:31] (current) – [3. Who now uses Chaosnet?] victor |
|---|
| * [[https://github.com/Chaosnet/Chaosnet-for-4.1BSD|4.1BSD]] Unix under the simh emulator | * [[https://github.com/Chaosnet/Chaosnet-for-4.1BSD|4.1BSD]] Unix under the simh emulator |
| * The [[https://github.com/Chaosnet/minits|MINITS]] operating system under the simh emulator | * The [[https://github.com/Chaosnet/minits|MINITS]] operating system under the simh emulator |
| * [[wp>TOPS-20]] (work in progress) | * [[wp>TOPS-20]] (work in good progress) |
| * [[wp>Multics]] (work in progress) under the [[https://gitlab.com/dps8m/dps8m/|DPS8M]] emulator | * [[wp>Multics]] (work in good progress) under the [[https://gitlab.com/dps8m/dps8m/|DPS8M]] emulator |
| * [[wp>OpenVMS|VMS]] (work in progress) | * [[wp>OpenVMS|VMS]] (work in progress) |
| * most linux-like operating systems (Linux, OpenBSD, macOS) using the NCP interface of the [[https://github.com/bictorv/chaosnet-bridge|Chaosnet bridge]] program. | * most linux-like operating systems (Linux, OpenBSD, macOS) using the NCP interface of the [[https://github.com/bictorv/chaosnet-bridge|Chaosnet bridge]] program. |
| With more systems in more places, the need for a more complex [[https://github.com/bictorv/chaosnet-bridge|Chaosnet bridge]] program arose, which integrated the previous functionalitites, with routing between them, and also gradually added support for more link layers (encapsulation in TLS and in IPv4/IPv6). By encapsulating Chaosnet packets in modern protocols, the scope was extended from the very local network (a single host in the case of unix sockets, or a local network in the case of Ethernet) to a **//[[global|global Chaosnet]]//**. | With more systems in more places, the need for a more complex [[https://github.com/bictorv/chaosnet-bridge|Chaosnet bridge]] program arose, which integrated the previous functionalitites, with routing between them, and also gradually added support for more link layers (encapsulation in TLS and in IPv4/IPv6). By encapsulating Chaosnet packets in modern protocols, the scope was extended from the very local network (a single host in the case of unix sockets, or a local network in the case of Ethernet) to a **//[[global|global Chaosnet]]//**. |
| |
| In 2020, the Chaosnet transport layer (a Network Control Program or [[https://github.com/bictorv/chaosnet-bridge/blob/master/NCP.md|NCP]]) was added to the bridge program. This makes it reasonably easy to adapt existing programs to use Chaosnet, and also to write application and servers using Chaosnet. Now also modern Linux/Unix/macOS-based computers can be Chaosnet nodes, and you can log in to your ITS system using [[rfc>734|Supdup]] [[https://github.com/PDP-10/supdup|over Chaosnet]]. | In 2020, the Chaosnet transport layer (a Network Control Program or [[https://github.com/bictorv/chaosnet-bridge/blob/master/doc/NCP.md|NCP]]) was added to the bridge program. This makes it reasonably easy to adapt existing programs to use Chaosnet, and also to write application and servers using Chaosnet. Now also modern Linux/Unix/macOS-based computers can be Chaosnet nodes, and you can log in to your ITS system using [[rfc>734|Supdup]] [[https://github.com/PDP-10/supdup|over Chaosnet]]. |
| |
| |
