It seems that in your case pihole user can't bind ports bellow 1000.
You could always execute/start the pihole-FTL.service as root. That should work, but it's inconvenient to say the least ...
Tagging @DL6ER for awareness.
That's a route I'm not willing to take.
I ran the command as root and got the following:
root@pihole:~# setcap CAP_NET_BIND_SERVICE,CAP_NET_RAW,CAP_NET_ADMIN+eip /usr/bin/pihole-FTL
Failed to set capabilities on file `/usr/bin/pihole-FTL' (Operation not supported)
The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
Makes me believe, there is something wrong with the pihole-FTL released file?
Not really (I run 3 instances of FTLDNS beta without any issues).
It has something to do with the environment you're running it in, most likely.
What Platform are you running it on ?
rasbian stretch on Pi V2
Raspbian should have capabilities support, but it is odd that it isn't working. Try:
sudo setcap CAP_NET_BIND_SERVICE,CAP_NET_RAW,CAP_NET_ADMIN+eip /usr/bin/pihole-FTL
This is unlikely, however it's not impossible that the file got damaged on your system. Please run
ls -lh /usr/bin/pihole-FTL
sha1sum /usr/bin/pihole-FTL
and tell us the output.
pi@pihole:~ $ sudo setcap CAP_NET_BIND_SERVICE,CAP_NET_RAW,CAP_NET_ADMIN+eip /usr/bin/pihole-FTL
Failed to set capabilities on file `/usr/bin/pihole-FTL' (Operation not supported)
The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
pi@pihole:~ $ ls -lh /usr/bin/pihole-FTL
-rwxr-xr-x 1 root root 1.4M Jun 19 22:28 /usr/bin/pihole-FTL
pi@pihole:~ $ sha1sum /usr/bin/pihole-FTL
cb0b59a1b2fa470c23301767d4002c956426cab7 /usr/bin/pihole-FTL
This matches “pihole-FTL-arm-linux-gnueabi”
So you have the correct file and everything is as expected except that setting capabilities aren't working on your system.
Are you running a custom kernel or file system?
No, the only curious thing there might be, is that I'm running a remote filesystem over NFS.
pi@pihole:~ $ mount
10.1.1.22:/piroot/pihole_jessie_rfs on / type nfs (rw,noatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.1.1.22,mountvers=3,mountproto=tcp,local_lock=all,addr=10.1.1.22)
I'm now not sure if NFSv3 has Linux Capabilities support? I'll try to upgrade to NFSv4..
What file system do you use on the remote hard drive?
It is run with an EXT4 FS.
Then I agree that it must be the NFS part that is causing trouble here. There are a few threads online.
@DL6ER, Agree that NFS is the culprit, and to test this theory I have moved my /usr/bin to the SD-card and ran the above command again and that works like a charm! Also possibly my containment for now.
1 Like
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.