Chaosnet wiki

The global Chaosnet site

User Tools

Site Tools

Trace:
local

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
local [2023-04-24 08:16] – [3.3 Chaosnet bridge] victorlocal [2025-11-04 08:28] (current) – [2.2 Connecting your machines to cbridge] victor
Line 1: Line 1:
 ====== - Setting up a local private Chaosnet ====== ====== - Setting up a local private Chaosnet ======
  
-If you want to play around with Chaosnet, connecting two or more of your emulated systems, without connecting to the [[global|Global Chaosnet]], the following is intended to be helpful.+If you want to play around with Chaosnet, connecting two or more of your emulated systems, without connecting to the [[global|Global Chaosnet]], the following is intended to be helpful. See also [[https://github.com/bictorv/chaosnet-bridge/blob/master/doc/EXAMPLES.md|example configs]] for cbridge.
  
 ===== - Background ===== ===== - Background =====
Line 9: Line 9:
 For the [[global|Global Chaosnet]], subnets are allocated per "site". Not everyone might want to connect to the Global Chaosnet, or you might want an isolated subnet for experiments or playing around. For the [[global|Global Chaosnet]], subnets are allocated per "site". Not everyone might want to connect to the Global Chaosnet, or you might want an isolated subnet for experiments or playing around.
  
-In order to minimise address collisions and routing problems, one subnet has been allocated 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. This is similar to the IP [[wp>Private network]]s such as 10.x.y.z or 192.168.x.y.+In order to minimise address collisions and routing problems, one 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. This is similar to the IP [[wp>Private network]]s such as 10.x.y.z or 192.168.x.y.
  
 That subnet is 376 (octal, = 254 decimal) which gives addresses 177001-177377 octal. That subnet is 376 (octal, = 254 decimal) which gives addresses 177001-177377 octal.
Line 23: Line 23:
  
 The IP addresses of the hosts running the PDP10 emulator (for ITS), the CADR emulator (usim), and the Chaosnet bridge (cbridge) are represented by ITSHOST,  CADRHOST, and CBRHOST. The IP addresses of the hosts running the PDP10 emulator (for ITS), the CADR emulator (usim), and the Chaosnet bridge (cbridge) are represented by ITSHOST,  CADRHOST, and CBRHOST.
-These are typically local IP address such as 192.168.0.x or 10.0.0.y, but if they are all running on the same host they can all be 127.0.0.1.+These are typically local IP address such as 192.168.0.x or 10.0.0.y, but if they are all running on the same host they can all be 127.0.0.1. Make sure the addresses match between the different config files, e.g. using 127.0.0.1 consistently (rather than the local "external" IP address such as 10.0.0.42), if you use it.
  
 The UDP port for encapulated Chaosnet packets is by default 42042, but if the hosts are on the same machine the ports for each must be different, e.g. 42043, 42044 etc. Below they are represented by ITSPORT, CADRPORT, and CBRPORT. The UDP port for encapulated Chaosnet packets is by default 42042, but if the hosts are on the same machine the ports for each must be different, e.g. 42043, 42044 etc. Below they are represented by ITSPORT, CADRPORT, and CBRPORT.
Line 60: Line 60:
 </code> </code>
  
-where MIT-OZ should be in your sys/site/hosts.text (which it originally is). The address should match that which is defined in the LISPM system, and should be on the same subnet as the CADR, i.e. have an address in the range 177001-177377.+where MIT-OZ should be in your sys/site/hosts.text (which it originally is). The address should match that which is defined in the LISPM system, and should be on the same subnet as the CADR, i.e. have an address in the range 177001-177377. ((If the CADR doesn't think the server is on a reachable subnet, it will not even try sending packets there!))
  
 This makes all packets to/from the MIT-OZ address (such as the FILE server, TIME server etc) be handled by the "local" backend, and all other packets by the "udp" backend. This makes all packets to/from the MIT-OZ address (such as the FILE server, TIME server etc) be handled by the "local" backend, and all other packets by the "udp" backend.
Line 68: Line 68:
 Advantages: Advantages:
   * you can connect more than two machines   * you can connect more than two machines
-  * you can use [[https://github.com/bictorv/chaosnet-bridge/blob/master/NCP.md|the Chaosnet "API"]] from your unix-like host+  * you can use [[https://github.com/bictorv/chaosnet-bridge/blob/master/doc/NCP.md|the Chaosnet "API"]] from your unix-like host
   * you can at a later stage connect to the Global Chaosnet   * you can at a later stage connect to the Global Chaosnet
   * you can connect to a local Ethernet-based Chaosnet (e.g. for LambdaDelta)   * you can connect to a local Ethernet-based Chaosnet (e.g. for LambdaDelta)
local.1682316973.txt.gz · Last modified: by victor
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki