| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| start [2024-09-24 19:01] – [3.1 Historical developments] victor | start [2025-11-04 08:25] (current) – [3.1 Historical developments] victor |
|---|
| ===== - Who used Chaosnet? ===== | ===== - Who used Chaosnet? ===== |
| |
| Chaosnet was developed at MIT, where it was initially implemented for [[wp>Lisp machine|LISP machines]] and [[wp>Incompatible Timesharing System|ITS]], then also for [[wp>TOPS-20]], VMS, Unix, and MINITS. At MIT, there were approximately 447 computers and 17 subnets in use in 1989 (according to ''SYSHST;HSTMIT 1115''). | Chaosnet was developed at MIT, where it was initially implemented for [[wp>Lisp machine|LISP machines]] and [[wp>Incompatible Timesharing System|ITS]], then also for [[wp>TOPS-20]], VMS, Unix, MINITS, and Multics. At MIT, there were approximately 447 computers and 17 subnets in use in 1989 (according to ''SYSHST;HSTMIT 1115''). |
| |
| The main spread in the rest of the world was through LISP machines: the original MIT machines, the [[wp>Lisp Machines|LMI]] and [[wp>Symbolics]] machines, and the [[wp>TI Explorer|Texas Instruments]] machines. Only a few other types of computers ran Chaosnet, but it was apparently popular enough that [[https://docstore.mik.ua/univercd/cc/td/doc/product/software/ssr83/rpc_r/48381.htm|Cisco implemented it in their routers]]. | The main spread in the rest of the world was through LISP machines: the original MIT machines, the [[wp>Lisp Machines|LMI]] and [[wp>Symbolics]] machines, and the [[wp>TI Explorer|Texas Instruments]] machines. Only a few other types of computers ran Chaosnet, but it was apparently popular enough that [[https://docstore.mik.ua/univercd/cc/td/doc/product/software/ssr83/rpc_r/48381.htm|Cisco implemented it in their routers]]. |
| 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]]. |
| |
| |
