diff options
authorNeels Hofmeyr <nhofmeyr@sysmocom.de>2017-05-10 16:46:26 +0200
committerNeels Hofmeyr <nhofmeyr@sysmocom.de>2017-05-11 10:34:03 +0000
commitcceb0f56ab0fffd20d7d255e23c7d98405df88fc (patch)
parent47de6b0a2455e9d356f82ae1e1aa15d65af42730 (diff)
readme: add some ssh details
2 files changed, 15 insertions, 0 deletions
diff --git a/doc/README-sysmobts.txt b/doc/README-sysmobts.txt
index 695c685..a1fffc0 100644
--- a/doc/README-sysmobts.txt
+++ b/doc/README-sysmobts.txt
@@ -34,6 +34,10 @@ SSH ACCESS
Copy the SSH public key from the system/user that runs the tester to the BTS
authorized keys file so the tester will be able to deploy binaries.
+ scp my_key.pub $sysmobts:
+ ssh $sysmobts
+ cat my_key.pub >> ~/.ssh/authorized_keys
It is also advisable to configure the eth0 network interface of the BTS to a
static IP address instead of using DHCP. To do so adjust /etc/network/interfaces
and change the line
diff --git a/doc/README.txt b/doc/README.txt
index 1edd742..80bbad8 100644
--- a/doc/README.txt
+++ b/doc/README.txt
@@ -95,6 +95,17 @@ possibly other) hardware: place the main unit's public SSH key on the sysmoBTS.
Log in via SSH at least once to accept the BTS' host key.
+Jenkins Configuration
+(TODO: jenkins build slave details)
+When adding an entry to jenkins' known_hosts file, be aware that you need to
+add an actual RSA host key. Using 'ssh' to access the main unit may work, but
+jenkins will still fail to access it in the absence of a full RSA host key:
+ ssh-keyscan -H $my_main_unit_ip_addr >> ~jenkins/.ssh/known_hosts
osmo-gsm-tester watches /var/tmp/osmo-gsm-tester for instructions to launch