Differences

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

--- global [2024-11-25 15:22] – [5. Subnets in use] victor
+++ global [2025-11-04 08:29] (current) – [2. Registering] victor
@@ Line 5: / Line 5: @@
 ===== - 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.
-A [[https://github.com/bictorv/chaosnet-bridge|Chaosnet bridge]] runs on (the IP, IPv6, and Chaos) host MX12.Victor.SE (also under the alias Router.Chaosnet.NET), accessible by [[protocol#udp|UDP]] or [[protocol#tls|TLS]] on port 42042, or using [[protocol#ip_standard|IP protocol 16]] (over IPv4 or IPv6), as Chaos host 3040.
+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]].
-The MX12 bridge
+See [[protocol#application_layer|here]] (or [[https://chaosnet.net/amber.html|MIT AI Memo 628]]) for more details about the protocols.
-  * 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, [[https://github.com/bictorv/chaosnet-bridge/blob/master/CONTACTS.md|among others]].
-See [[protocol#application_layer|here]] (or [[https://lm-3.github.io/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.
+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.**
   * 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.
-  * 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/TLS.md|here]] for instructions).
+  * 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.
 ==== - If you want to connect a single host ====
@@ Line 53: / Line 53: @@
 ===== - Configuration examples =====
-For configuration examples, please see [[https://github.com/bictorv/chaosnet-bridge/blob/master/EXAMPLES.md|here]].
+For configuration examples, please see [[https://github.com/bictorv/chaosnet-bridge/blob/master/doc/EXAMPLES.md|here]].
 ===== - Subnets in use =====
@@ Line 92: / Line 92: @@
 == #16: GEWT network ==
 Used by SJ.GEWT.NET (a long time ago now).
+== #27: Victor network too ==
+A second subnet for BV.
 == #37: Sanyalnet (hosts 17401-17777) ==