Technical Note: When adding master to slave inventory, slave uses remote@ instead of admin@
Description
Scope
Solution
This article covers permission issues with nplus1 remote login which cause the slave to use "remote" user name instead of "admin" while trying to ssh into.
Scope
FWC-100D v8.3.3.
Solution
This issue has been reported after upgrading controller to 8.3-3GAbuild-0.
When the master member is added, the slave controller tries to access peer by remote account instead of admin account, so the master member cannot be added at all.
Check if the permission for authorized_keys has been changed to guest:guest by logging into root:
The workaround is to change the permission to remote:remote on the file "remote" under "/data/ssh/authkeys", this automatically changes the permissions of "authorized_keys" under"/data/ssh/authkeys/remote".
If the permissions are seen to be guest guest as shown above then change the permission to remote:remote as shown below:
When the master member is added, the slave controller tries to access peer by remote account instead of admin account, so the master member cannot be added at all.
Check if the permission for authorized_keys has been changed to guest:guest by logging into root:
/data/ssh/authkeys:
total 1
-rw-r--r-- 1 root root 0 Sep 6 15:42 authorized_keys
drwxr-xr-x 2 guest guest 1024 Sep 6 15:42 remote
/data/ssh/authkeys/remote:
total 1
-rwx------ 1 guest guest 248 Sep 6 15:42 authorized_keys
The workaround is to change the permission to remote:remote on the file "remote" under "/data/ssh/authkeys", this automatically changes the permissions of "authorized_keys" under"/data/ssh/authkeys/remote".
If the permissions are seen to be guest guest as shown above then change the permission to remote:remote as shown below:
#cd /data/ssh/authkeys
#ls -l
-rw-r--r-- 1 root root 0 Sep 6 15:42 authorized_keys
drwxr-xr-x 2 guest guest 1024 Sep 6 15:42 remote
#chown -R remote:remote remote