Changes

If you've taken all of the steps described above, the configuration is done. But as with any other configuration, it is always wise to test the set up in order to make sure that it works properly. To test this particular set up, login to any of the routers go to '''Services → Maintenance → CLI'''. Login with user name: '''root''' and the router's admin password. You should then be able to '''ping''' the other router or any of the end devices that you have connected to either of the two router's. To execute a ping command, type '''ping <devices_ip>''' into the console and press the Enter key:  

If you've taken all of the steps described above, the configuration is done. But as with any other configuration, it is always wise to test the set up in order to make sure that it works properly. To test this particular set up, login to any of the routers go to '''Services → Maintenance → CLI'''. Login with user name: '''root''' and the router's admin password. You should then be able to '''ping''' the other router or any of the end devices that you have connected to either of the two router's. To execute a ping command, type '''ping <devices_ip>''' into the console and press the Enter key:  

[[File:Testing relayd.png|border|center|class=tlt-border|600x300px]]

[[File:Networking rutxxx configuration example cli ping v1.png|border|center|class=tlt-border|700x300px]]

Replace <devices_ip> with an actual IP address of a device that is in your network and if the ping requests are successful, it means the configuration is working. You can check the IP addresses of the devices connected to your network in RUT1's '''Status → Network → LAN''' section.  

Replace <devices_ip> with an actual IP address of a device that is in your network and if the ping requests are successful, it means the configuration is working. You can check the IP addresses of the devices connected to your network in RUT1's '''Status → Network → LAN''' section.  

An important issue to bring up is that the two routers will not be able to communicate with each other via their LAN IPs if they have LAN IP addresses in different subnets. If that is the case, there are still a few options you can take without changing either of the routers IP addresses:

An important issue to bring up is that the two routers will not be able to communicate with each other via their LAN IPs if they have LAN IP addresses in different subnets. If that is the case, there are still a few options you can take without changing either of the routers IP addresses:

* When communicating between routers, use RUT2's WAN IP instead of its LAN IP. This will work because RUT1 will lease the WAN IP address to RUT2 from its LAN network. If that is the case you chose, then don't forget to check RUT2's WAN IP after completing the '''[[Relayd#WiFi_WAN|3.2.2]]''' step of this guide

* When communicating between routers, use RUT2's WAN IP instead of its LAN IP. This will work because RUT1 will lease the WAN IP address to RUT2 from its LAN network. If that is the case you chose, then don't forget to check RUT2's WAN IP after completing the '''[[Relayd_RutOS#WiFi_WAN|3.2.2]]''' step of this guide

* Add Static Routes to each router in the '''Network → Routing → Static Routes''' section. This must be done from both ends, i.e., you must configure a route both in RUT1 and in RUT2

* Add Static Routes to each router in the '''Network → Routing → Static Routes''' section. This must be done from both ends, i.e., you must configure a route both in RUT1 and in RUT2