Site Tools


router_to_router_ssh

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
Last revisionBoth sides next revision
router_to_router_ssh [2023/05/23 17:33] – [Example] -change to subhead1-condense, formatting-make numbering continguous hogwildrouter_to_router_ssh [2023/05/23 18:06] – [Overview] -added subhead "Setting up/Eablishing a tunnel" hogwild
Line 11: Line 11:
   * As seen below, for switching wireless radio(s) on or off on a schedule (not shown).   * As seen below, for switching wireless radio(s) on or off on a schedule (not shown).
  
- \\+=====  Setting up/Establishing a Tunnel =====
  
 Follow these steps to generate a Keypair and establish an SSH tunnel: Follow these steps to generate a Keypair and establish an SSH tunnel:
  
-  - On the primary router (the one issuing SSH commands) generate a Keypair by typing the command: \\ "dropbearkey -t rsa -f ~/.ssh/id_dropbear" \\ \\ This will display a result similar to that shown below. Leave this window open, as you'll need it for step 2. \\ \\ \\ {{:pasted:20210921-152323.png}} \\ \\  +  - On the primary router (the one issuing SSH commands) generate a Keypair by typing the command: \\ "dropbearkey -t rsa -f ~/.ssh/id_dropbear" \\ \\ This will display a result similar to that shown below. Leave this window open, as you'll need it for step 2. \\ \\ {{:pasted:20210921-152323.png?744}} \\ \\  
-  - Copy the Public key portion from the primary router and paste it into the “Authorized Keys” field in secondary router: \\ \\ {{:pasted:20210921-152415.png}} \\ \\  +  - Copy the Public key portion from the primary router and paste it into the “Authorized Keys” field in secondary router: \\ \\ {{:pasted:20210921-152415.png?739}} \\ \\  
-  - Note that a pre-existing, and unrelated key was redacted above. \\ \\  +  - In the above screenshot, a pre-existing, unrelated key was redacted. \\ \\  
-  - Now, connect to the secondary router via an SSH session (running on the primary router). The example below uses the //nvram// command to display the hostname. The first command string ("ssh root@192.168.10.1 nvram get lan_hostname")** **executes the command on the secondary router and then it [nvram get lan_hostname] is executed locally, on the primary router. \\ \\ \\ {{:pasted:20210921-152503.png}}+  - Now, connect to the secondary router via an SSH session (running on the primary router).  \\ The example below uses the //nvram// command to display the hostname. \\ The first command string ("ssh root@192.168.10.1 nvram get lan_hostname")** **executes the command on the secondary router and then it [nvram get lan_hostname] is executed locally, on the primary router. \\ \\ \\ {{:pasted:20210921-152503.png?741}}
  
-===== Example =====+ \\ 
 + 
 + \\ 
 + 
 + 
 +===== Usage Example =====
  
 This example will enable/disable the eth1 5Ghz WiFi interface on the secondary router. (Temperature is shown only when the interface is enabled).  \\  \\ This example will enable/disable the eth1 5Ghz WiFi interface on the secondary router. (Temperature is shown only when the interface is enabled).  \\  \\
  
-  - This screenshot shows the status display of the Primary router before before the command is run: \\ \\ {{:pasted:20210921-152542.png}} \\ \\  +  - This screenshot shows the status display of the Primary router before before the command is run: \\ \\ {{:pasted:20210921-152542.png?736}} \\ \\  
-  - Now, we run execute the command (//ssh root@192.168.10.1 radio toggle 1//): \\ \\ {{:pasted:20210921-152607.png}} \\  +  - Now, we run the command (//ssh root@192.168.10.1 radio toggle 1//): \\ \\ {{:pasted:20210921-152607.png?744}} \\ \\  
-  - This shows the status display after the command is run\\ {{:pasted:20210921-152637.png}} \\  \\ If the same command is repeated, the eth1 interface will be disabled on the primary router.+  - This shows the status display after the command is run: \\ \\ {{:pasted:20210921-152637.png?761}} \\  \\ Since "radio toggle 1" is  a toggle switch, if the same command is repeated, the eth1 interface will be disabled on the primary router. 
 + 
 +\\ 
 + 
 + \\
  
  
 ===== Notes ===== ===== Notes =====
  
-  * SSH must be enabled on both routers. +  * The SSH daemon must be enabled on both routers. 
-  * The key generated will be erased after a reboot of the primary router. +  * The key generated will be erased after a reboot of the Primary router.
     * Either keep a copy of the "id_dropbear" file offline (on a flash drive, or CIFS Client share) for restoration, or;     * Either keep a copy of the "id_dropbear" file offline (on a flash drive, or CIFS Client share) for restoration, or;
-    * Be prepared to repeat the procedure (steps 1 and 2) after a reboot, removing any redundant key from the secondary router.+    * Be prepared to repeat (steps 1and 2.) after a reboot, removing any redundant key from the secondary router.
   * This guide was produced using [[https://www.chiark.greenend.org.uk/~sgtatham/putty/|PuTTY]] v0.76 and FreshTomato release 2021.5.   * This guide was produced using [[https://www.chiark.greenend.org.uk/~sgtatham/putty/|PuTTY]] v0.76 and FreshTomato release 2021.5.
   * Inspiration was provided by [[https://blog.michael.franzl.name/2017/09/03/set-passwordless-ssh-login-dropbear-client/|this]] article.    * Inspiration was provided by [[https://blog.michael.franzl.name/2017/09/03/set-passwordless-ssh-login-dropbear-client/|this]] article. 
router_to_router_ssh.txt · Last modified: 2023/05/24 02:08 by hogwild