Pogoplug Pro ssh access July 26, 2017 03:46PM |
Registered: 7 years ago Posts: 9 |
Re: ssh access July 26, 2017 04:32PM |
Admin Registered: 14 years ago Posts: 19,561 |
ssh root@debian.localor
ssh root@192.168.0.220
Re: ssh access July 26, 2017 04:35PM |
Registered: 7 years ago Posts: 9 |
Re: Pogoplug Pro ssh access July 26, 2017 04:55PM |
Admin Registered: 14 years ago Posts: 19,561 |
Re: Pogoplug Pro ssh access July 26, 2017 05:08PM |
Registered: 7 years ago Posts: 9 |
Re: Pogoplug Pro ssh access July 27, 2017 12:41PM |
Registered: 8 years ago Posts: 162 |
Re: Pogoplug Pro ssh access July 27, 2017 03:42PM |
Admin Registered: 14 years ago Posts: 19,561 |
Quote
2. Login the Pogo OS and setup to kill the Pogo process permanently, and some do some cleanup.
2A. Find the Pogo dynamic IP address in your router, or use some scanning program such as Linux nmap, IOS Fing,... And then use the credential that you have set up previously for stock Pogo OS during intial set up to boot new U-boot and/or Debian kernel (remember that root/password ?).
After logging in, you can kill pogoplug process so it won't interfere with normal opration:
killall hbwd
2B. Edit the file /etc/init.d/rcS to kill pogoplug service permanently.
Find the line which contains "hbmgr.sh start" and comment out the whole line, and add a new line to start dropbear:
###/etc/init.d/hbmgr.sh start
/usr/sbin/dropbear
2C. Comment out these lines to ensure booting without NAND checksum errors:
#if /usr/local/cloudengines/bin/blparam | grep ethaddr > /tmp/ethaddr; then
# . /tmp/ethaddr
#fi
#rm -f /tmp/ethaddr
#if /usr/local/cloudengines/bin/blparam | grep cedebug > /tmp/cedebug; then
# . /tmp/cedebug
#fi
#rm -f /tmp/cedebug