Radarcape:Miscellaneous: Difference between revisions

From Beast Wiki
Jump to navigation Jump to search
imported>Dl4mea
imported>Dl4mea
Line 1: Line 1:
=== Using SOCAT to copy TCP to a file ===
=== Using SOCAT to copy TCP to a file ===
   socat -u TCP:localhost:10002 OPEN:radarcape.bin,creat
   socat -u TCP:localhost:10002 OPEN:radarcape.bin,creat
=== Tunneling a port to another Radarcape ===
First, generate a SSH key pair on the local Radarcape
cd ~/.ssh
dropbearkey -t rsa -f id_rsa
Set attributes of ~, .ssh and authorized_keys are set to 600.
Next, copy the public key given from above command to the server folder ~/.ssh/authorized_keys. Mind that the attributes of ~, .ssh and authorized_keys are set to 600.
On the local Radarcape, add the command below to cape.sh. Please remember that cape.sh runs without user settings, so you need to specify the path to the SSH key absolute.
./autossh -M 6667 -f -p <server_ssh_port> -i /home/root/.ssh/id_rsa -N -R *:8002:localhost:80 -R *:1302:localhost:10003 -R *:2202:localhost:22 root@<server_domain> &
Now the local Radarcape is accessible on <server_domain> under port 8002, 1302 and 2202.
== Server Settings ==
== Server Settings ==


If the server is also a Radarcape, and in case that you want to get access from external devices to the ports through the tunnel, you need to add switch "'''-a'''" to the dropbear startup file '''/lib/systemd/system/[email protected]'''.
If the server is also a Radarcape, and in case that you want to get access from external devices to the ports through the tunnel, you need to add switch "'''-a'''" to the dropbear startup file '''/lib/systemd/system/[email protected]'''.

Revision as of 09:10, 4 October 2013

Using SOCAT to copy TCP to a file

 socat -u TCP:localhost:10002 OPEN:radarcape.bin,creat

Server Settings

If the server is also a Radarcape, and in case that you want to get access from external devices to the ports through the tunnel, you need to add switch "-a" to the dropbear startup file /lib/systemd/system/[email protected].