ping now impossible?

[Tom Horsley]

Yesterday, I could run ping. This morning I installed updates
which came with a new kernel, and all attempts to ping
generate this:

tomh> ping marmot
ping: icmp open socket: Operation not permitted

I now have to use sudo in front of ping to make it work.

What the heck happened with this round of updates?

(I see iputils was also an update this morning).

[Harald Hoyer]

On 18.07.2014 14:22, Tom Horsley wrote:
> Yesterday, I could run ping. This morning I installed updates
> which came with a new kernel, and all attempts to ping
> generate this:
>
> tomh> ping marmot
> ping: icmp open socket: Operation not permitted
>
> I now have to use sudo in front of ping to make it work.
>
> What the heck happened with this round of updates?
>
> (I see iputils was also an update this morning).

$ getcap /usr/bin/ping
/usr/bin/ping = cap_net_admin,cap_net_raw+ep

[Tom Horsley]

On Fri, 18 Jul 2014 14:42:11 +0200
Harald Hoyer wrote:
> $ getcap /usr/bin/ping
> /usr/bin/ping = cap_net_admin,cap_net_raw+ep

Yep. If I use setcap to put those back on /usr/bin/ping
it starts working again.

Did the iputils update today remove them somehow I wonder?

[Ed Greshko]

On 07/18/14 20:47, Tom Horsley wrote:
> On Fri, 18 Jul 2014 14:42:11 +0200
> Harald Hoyer wrote:
> > $ getcap /usr/bin/ping
> > /usr/bin/ping = cap_net_admin,cap_net_raw+ep
>
> Yep. If I use setcap to put those back on /usr/bin/ping
> it starts working again.
>
> Did the iputils update today remove them somehow I wonder?

I didn't get any updates to iputils since June 26.

[root@meimei log]# rpm -q iputils
iputils-20140519-1.fc20.x86_64

I'm running F20, of course, and I didn't even see a new iputils in updates-testing.

[Tom Horsley]

On Fri, 18 Jul 2014 20:56:53 +0800
Ed Greshko wrote:
> I'm running F20, of course, and I didn't even see a new iputils in updates-testing.

You're right. I misread the date on the rpm -i output.
I have no idea where the capabilities went, but they
are back now :-).