tycho
Guru (not...)
- Joined
- Aug 9, 2011
- Messages
- 652
- Reaction score
- 272
I've been very happy with how knockd works on my Cloud@Cost Asterisk 12/FreePBX12/Ubuntu 14 instance (installed per http://nerdvittles.com/?p=11041). So happy that I thought I might try to install it on my PogoMobile (installed per http://nerdvittles.com/?p=10560).
No go, as least as I am attempting it.
The NV article offers installation approaches for "RedHat/Fedora/CentOS/ScientificLinux servers", for "Ubuntu/Debian servers", and for "ARM-based servers". I wasn't sure which of the second two to pick. Yes, my PogoMobile is ARM-based, but it runs Debian, and I thought maybe when you stated "ARM-based servers" you might be talking about the OS (i.e, perhaps ArchLinux or similar). So, I tried the Debian script. No workie:
OK, that made sense, but I hope I hadn't broken anything on my otherwise fine-working system (did I?) But, even given the above error message, the installation wraps up saying this:
That's a big fib, of course, because knockd had NOT been enabled. It wasn't even installed.
I then decided to turn to the "Arm-based system" script. After a few go-rounds I read through the script and noted the things that, if pre-existing, would stop the script from completing (knockd.conf, IIRC at this time). I deleted those remainders from the prior botched install and the script completed. But:
(Once again, the install finished up claiming "Install Complete. knockd has been enabled as requested." Fibber McGhee).
So: I have an "armel" system, inconsistent from the required "armhf" system. I looked about for a (plain?) "armel" version of knockd and may have found one but I'm uncertain if this will fly. Perhaps I can re-write ths script to include a package from the following instead of the offending armhf package:
https://packages.debian.org/wheezy/armel/knockd/filelist
Or, does the knockd ship then just pass me by?
No go, as least as I am attempting it.
The NV article offers installation approaches for "RedHat/Fedora/CentOS/ScientificLinux servers", for "Ubuntu/Debian servers", and for "ARM-based servers". I wasn't sure which of the second two to pick. Yes, my PogoMobile is ARM-based, but it runs Debian, and I thought maybe when you stated "ARM-based servers" you might be talking about the OS (i.e, perhaps ArchLinux or similar). So, I tried the Debian script. No workie:
Code:
dpkg: error processing knockd_0.5-3_amd64.deb (--install):
package architecture (amd64) does not match system (armel)
Errors were encountered while processing:
knockd_0.5-3_amd64.deb
sed: can't read /etc/default/knockd: No such file or directory
./knock-U.sh: line 103: /etc/init.d/knockd: No such file or directory
OK, that made sense, but I hope I hadn't broken anything on my otherwise fine-working system (did I?) But, even given the above error message, the installation wraps up saying this:
Code:
Install Complete. knockd has been enabled as requested.
Knock ports for access to XXX.XXX.XXX.XXX set to TCP: XXXX XXXX XXXX
To enable remote access, issue these commands from any remote server:
nmap -p ___ && nmap -p ___ && nmap -p ___
Install iOS PortKnock or Android PortKnocker on smartphone. Read knock.FAQ.
That's a big fib, of course, because knockd had NOT been enabled. It wasn't even installed.
I then decided to turn to the "Arm-based system" script. After a few go-rounds I read through the script and noted the things that, if pre-existing, would stop the script from completing (knockd.conf, IIRC at this time). I deleted those remainders from the prior botched install and the script completed. But:
Code:
dpkg: error processing knockd_0.5-3ubuntu1_armhf.deb (--install):
package architecture (armhf) does not match system (armel)
Errors were encountered while processing:
knockd_0.5-3ubuntu1_armhf.deb
sed: can't read /etc/default/knockd: No such file or directory
./knock-ARM.sh: line 101: /etc/init.d/knockd: No such file or directory
(Once again, the install finished up claiming "Install Complete. knockd has been enabled as requested." Fibber McGhee).
So: I have an "armel" system, inconsistent from the required "armhf" system. I looked about for a (plain?) "armel" version of knockd and may have found one but I'm uncertain if this will fly. Perhaps I can re-write ths script to include a package from the following instead of the offending armhf package:
https://packages.debian.org/wheezy/armel/knockd/filelist
Or, does the knockd ship then just pass me by?