networking-en
Differences
This shows you the differences between two versions of the page.
Previous revision | |||
— | networking-en [2023/04/06 08:01] (current) – [Port] rjversluis | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ======R2Rnet====== | ||
+ | [[: | ||
+ | [[english|Content]] -> [[english# | ||
+ | * **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/ | ||
+ | |||
+ | \\ | ||
+ | =====Mobile clients===== | ||
+ | Mobile clients like __**[[: | ||
+ | See the [[# | ||
+ | |||
+ | |||
+ | \\ | ||
+ | =====The Picture===== | ||
+ | {{: | ||
+ | |||
+ | \\ | ||
+ | =====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 " | ||
+ | Roaming train " | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ====Example NetRoutes==== | ||
+ | <code xml> | ||
+ | < | ||
+ | < | ||
+ | <st id=" | ||
+ | <st id=" | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | \\ | ||
+ | =====Setup===== | ||
+ | {{: | ||
+ | |||
+ | \\ | ||
+ | |||
+ | |||
+ | ====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=" | ||
+ | </ | ||
+ | |||
+ | The rocrail.ini' | ||
+ | |||
+ | <code xml> | ||
+ | <r2rnet id=" | ||
+ | </ | ||
+ | |||
+ | **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: {{: | ||
+ | |||
+ | \\ | ||
+ | ===== Mobile Client Support ===== | ||
+ | Make sure the DHCP client setup is correct to announce the IP address to mobile clients.\\ | ||
+ | |||
+ | ==== Ubuntu & DHCP ==== | ||
+ | Check the **/ | ||
+ | < | ||
+ | send host-name "< | ||
+ | send dhcp-client-identifier 00: | ||
+ | </ | ||
+ | The MAC address, HWaddr, can be obtained with **ifconfig**: | ||
+ | < | ||
+ | eth0 Link encap: | ||
+ | ... | ||
+ | wlan0 Link encap: | ||
+ | ... | ||
+ | </ | ||
+ | |||
+ | |||