Differences

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

@@ Line 1: / Line 1: @@
+======R2Rnet======
+[[:english#automatic mode|{{  :automat.png}}]][[:english|{{  :rocrail-logo-35.png}}]]
+[[english|Content]] -> [[english#automatic mode|Automatic Mode]] -> **[[english#operating_mode|Operating Mode]]**
+  * **R2Rnet**
+ \\
+The R2Rnet supports roaming trains traveling from system to system.\\
+This technology can be usefull for XXL layouts or modular setups.\\
+Boundaries of Rocrail systems should be also power district boundaries; A roaming train will be set to zero velocity if it has left a system.\\
+ \\
+=====UDP Multicast=====
+R2Rnet uses the UDP Multicast protocol for communicating with all systems.\\
+**Note:** Some routers/switches do not handle UDP Multicast; Check for supported hardware.\\
+ \\
+=====Mobile clients=====
+Mobile clients like __**[[:android:androc2-en|andRoc]]**__ and __**[[:wio:overview-en|WIO]]**__ will write a R2RNet request for available server connections. All enabled R2RNet servers will respond to this with hostname, port and plan title.\\
+See the [[#enable|Enable]] option.\\
+ \\
+=====The Picture=====
+{{:r2rnet-overview.png?300}}\\
+ \\
+=====NetRoutes=====
+NetRoutes are stored in a separate file, and are provided by only one system in the R2Rnetwork; The other systems will request them.\\
+Every system has its own namespace which is used in setting up the netroutes.\\
+Block "b1" for system "r1" is formatted like this: "r1::b1"\\
+Roaming train "NS2403" on system "r1" will be prefixed on all other systems like this: "r1::NS2403"\\
+ \\
+====Example NetRoutes====
+<code xml>
+<plan>
+  <stlist>
+    <st id="r1::b2-r2::b1" bka="r1::b2" bkb="r2::b1"/>
+    <st id="r2::b2-r1::b1" bka="r2::b2" bkb="r1::b1"/>
+  </stlist>
+</plan>
+</code>
+ \\
+=====Setup=====
+{{:rocrailini-r2rnet-en.png?800}}\\
+\\
+====ID====
+Server ID.\\
+====Address====
+UDP Multicast IP address, default **224.0.1.20**.\\
+====Port====
+UDP Multicast IP port, default **8051**.\\
+==== Local IP ====
+Only required if the PC has **more than one network interfaces** installed; In all other cases: Leave empty!\\
+IP address of the **PC's network interface** which is used for communication with the WIOs to make sure the traffic runs on the right one.\\
+ \\
+====NetRoutes====
+The NetRoutes file name in case this server is route master.\\
+===Poll===
+If the NetRoutes file does not exist locally, it will be requested periodically.\\
+====Enable====
+Enable R2Rnet.\\
+This option should be set in case clients are trying to look up a Rocrail Server. (Rocview, andRoc, WIOesp, WIOpi)\\
+ \\
+Every Rocrail system must be setup with an unique client connection, so if one or more systems reside on the same computer they should use different port numbers.\\
+<code xml>
+  <tcp port="8051"/>
+</code>
+The rocrail.ini's need to be extended with a **r2rnet** node:\\
+<code xml>
+  <r2rnet id="r1" enable="true" port="8051"/>
+</code>
+**Note:** Make sure that no other service is running on the same port!\\
+ \\
+=====Startup=====
+All playing systems must be started and initialized according the real situation on the layout and activating the **auto** mode.\\
+Only one system should have access to the netroutes file to prevent conflicts.\\
+The rest of the operation equals to running a layout stand alone.\\
+ \\
+=====Open Issues=====
+  * Remote switch commands in NetRoutes.
+  * Signal commands for the exiting (remote)block.
+  * Second next block at system boundaries.
+ \\
+=====Files=====
+  * Minimal setup with 2 systems: {{:r1r2-r2rnet.zip}}
+ \\
+===== Mobile Client Support =====
+Make sure the DHCP client setup is correct to announce the IP address to mobile clients.\\
+==== Ubuntu & DHCP ====
+Check the **/etc/dhcp/dhclient.conf** or **/etc/dhcp3/dhclient.conf** file if the following line is active and set to the right MAC address:
+<code>
+send host-name "<hostname>";
+send dhcp-client-identifier 00:1b:9e:44:5f:cb;
+</code>
+The MAC address, HWaddr, can be obtained with **ifconfig**:
+<code>
+eth0      Link encap:Ethernet  HWaddr 00:1a:92:fc:0d:5d
+...
+wlan0     Link encap:Ethernet  HWaddr 00:1b:9e:44:5f:cb
+...
+</code>