Bug 2049413

Summary: ping: socket: Operation not permitted
Product: Red Hat Enterprise Linux 8 Reporter: AIKAWA Shigechika <shige>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Frantisek Sumsal <fsumsal>
Severity: high Docs Contact:
Priority: unspecified    
Version: CentOS StreamCC: bstinson, jwboyer, systemd-maint-list
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-02 08:40:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description AIKAWA Shigechika 2022-02-02 07:42:56 UTC 
Description of problem:

$  ping 8.8.8.8
ping: socket: Operation not permitted

Version-Release number of selected component (if applicable):

CentOS-Stream-8-x86_64-20220201

How reproducible:

Steps to Reproduce:
1. clean install
2. ping 8.8.8.8
3. 😭

Actual results:

ping: socket: Operation not permitted

Expected results:

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=1.84 ms
Additional info:

$ diff -u /lib/sysctl.d/50-default.conf /lib/sysctl.d/50-default.conf.fix
--- /lib/sysctl.d/50-default.conf	2022-01-28 01:16:43.000000000 +0900
+++ /lib/sysctl.d/50-default.conf.fix	2022-02-02 16:25:19.466602199 +0900
@@ -39,7 +39,7 @@
 #   #define GID_T_MAX (((gid_t)~0U) >> 1)
 # That's not so bad because values between 2^31 and 2^32-1 are reserved on
 # systemd-based systems anyway: https://systemd.io/UIDS-GIDS.html#summary
--net.ipv4.ping_group_range = 0 2147483647
+net.ipv4.ping_group_range = 0 2147483647

 # Fair Queue CoDel packet scheduler to fight bufferbloat
 net.core.default_qdisc = fq_codel
Comment 1 Frantisek Sumsal 2022-02-02 08:40:56 UTC 

*** This bug has been marked as a duplicate of bug 2037807 ***