[EN] [Solved] Normal user could not run ping after fresh install

[timc]

Error was "ping: icmp open socket: Operation not permitted". I Googled the message and ran "setcap cap_net_raw=ep /bin/ping", which corrected the problem.

I mention this because this has never happened to me before with a Siduction installation.

Tim

[terroreek]

thank you sir, I also got this error and was able to fix it with your instructions.

[jaegermeister]

Brilliant!!! Thanks

[linearJim]

hello,
new siduction user here but long time debian testing user

i had the same problem yesterday with a fresh siduction installation,the solution i found was

Code: [Select]

chmod u+s `which ping'
and i was wondering why did this happen in the first place..and if this is a safe solution (i assume it is not a good idea to have wrong permission on ping)
 

[hendrikL]

hi,

Code: [Select]

apt-get update && apt-get install --reinstall iputils-ping
should solve that problem

greetz hendrik

[linearJim]

Code: [Select]

root@dell:~# apt-get install --reinstall iputils-ping
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 7 not upgraded.
Need to get 0 B/56.5 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 184485 files and directories currently installed.)
Preparing to unpack .../iputils-ping_3%3a20121221-5+b2_amd64.deb ...
Unpacking iputils-ping (3:20121221-5+b2) over (3:20121221-5+b2) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up iputils-ping (3:20121221-5+b2) ...
Setcap worked! Ping(6) is not suid!
thanx!

[melmarker]

the problem was introduced by two things: package changes in debian and problems with aufs - both resolved with the next release, we dropped aufs, use overlayfs right now with a own kernel patch for this.