Server not responding to ICMP requests

ApleLois · April 27, 2024, 6:20pm

Hi,
I have 4 servers running on rocky linux at a datacenter in Chicago but one is not answering to ping requests.


[(01:51 PM)][(root@server)] [(~)] $ ip r
default via 208.117.37.129 dev enp68s0f0 proto static metric 100
208.117.37.129 dev enp68s0f0 proto static scope link metric 100 

[(01:56 PM)][(root@server)] [(~)] $ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp68s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 7c:c2:55:23:cd:3c brd ff:ff:ff:ff:ff:ff
    inet 208.117.*.*/32 scope global noprefixroute enp68s0f0
       valid_lft forever preferred_lft forever
    inet6 fe80::7ec2:55ff:fe23:cd3c/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: enp68s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 7c:c2:55:23:cd:3d brd ff:ff:ff:ff:ff:ff
4: enp68s0f2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 7c:c2:55:23:cd:3e brd ff:ff:ff:ff:ff:ff
5: enp68s0f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 7c:c2:55:23:cd:3f brd ff:ff:ff:ff:ff:ff
    
[(01:58 PM)][(root@server)] [(~)] $ ifconfig
enp68s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 208.117.*.*  netmask 255.255.255.255  broadcast 0.0.0.0
        inet6 fe80::7ec2:55ff:fe23:cd3c  prefixlen 64  scopeid 0x20<link>
        ether 7c:c2:55:23:cd:3c  txqueuelen 1000  (Ethernet)
        RX packets 520286825  bytes 181418408778 (168.9 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 703930349  bytes 873242718055 (813.2 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp68s0f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 7c:c2:55:23:cd:3d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 165  bytes 10362 (10.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp68s0f2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 7c:c2:55:23:cd:3e  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        
[(01:59 PM)][(root@server)] [(~)] $ netstat -nr
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         208.117.37.129  0.0.0.0         UG        0 0          0 enp68s0f0
208.117.37.129  0.0.0.0         255.255.255.255 UH        0 0          0 enp68s0f0

[(01:59 PM)][(root@server)] [(~)] $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp68s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 7c:c2:55:23:cd:3c brd ff:ff:ff:ff:ff:ff
    inet 208.117.*.*/32 scope global noprefixroute enp68s0f0
       valid_lft forever preferred_lft forever
    inet6 fe80::7ec2:55ff:fe23:cd3c/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: enp68s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 7c:c2:55:23:cd:3d brd ff:ff:ff:ff:ff:ff
4: enp68s0f2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 7c:c2:55:23:cd:3e brd ff:ff:ff:ff:ff:ff
5: enp68s0f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 7c:c2:55:23:cd:3f brd ff:ff:ff:ff:ff:ff        

[(02:00 PM)][(root@server)] [(~)] $ cat /proc/sys/net/ipv4/icmp_echo_ignore_all
0

sspencerwire · April 27, 2024, 8:56pm

Can you explain your subnet address of /32? That’s a single address, rather than a network. I’m just guessing here, but shouldn’t that be a /24 so that it can even see the gateway?

ApleLois · April 28, 2024, 5:46pm

I edited the network, but still same issue, cannot ping ip

[(01:43 PM)][(root@server)] [(~)] $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp68s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 7c:c2:55:23:cd:3c brd ff:ff:ff:ff:ff:ff
    inet 208.117.*.*/24 brd 208.117.37.255 scope global noprefixroute enp68s0f0
       valid_lft forever preferred_lft forever
    inet6 fe80::7ec2:55ff:fe23:cd3c/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: enp68s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 7c:c2:55:23:cd:3d brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.105/24 brd 192.168.1.255 scope global noprefixroute enp68s0f1
       valid_lft forever preferred_lft forever
    inet6 fe80::5921:4268:264e:d217/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
4: enp68s0f2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 7c:c2:55:23:cd:3e brd ff:ff:ff:ff:ff:ff
5: enp68s0f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 7c:c2:55:23:cd:3f brd ff:ff:ff:ff:ff:ff

iwalker · April 28, 2024, 7:08pm

Double check the subnet mask for the 208.117.x.x address because it may not be /24 - ask your ISP or whoever provides you with the public IP address range. In which case, either the IP address is wrong, or the subnet mask. Also that interface must have a default gateway configured for it to work and reply to ping.

ganphx · April 28, 2024, 8:19pm

You need to assign 208.117.37.129/32 to f0 if this is your public interface. On f1, 192.168.1.105 is incorrect, it would need to be 192.168.1.0/24 or a VALID SUBNET.
You also need to turn on IP forwarding on this host if this is your gateway to your other hosts.
You will NOT be able to ping any of your hosts unless you assign IP addresses to your other hosts either statically or using DHCP and have a properly configured firewall setup.
If your ISP assigned you additional public IP addresses for each host, then you will need to use them in your setup instead of the private 192.168.1.0/24 addresses.

jlehtone · April 28, 2024, 9:04pm

What do you mean? The 192.168.1.105/24 is a valid address config. It tells that the IP address of this interface is 192.168.1.105 and that the subnet is 192.168.1.0/24.

How does the config of this machine differ from configs of the others?

Who is trying to ping the machine? (From same subnet or from elsewhere?)

Topic		Replies	Views
Sharing Internet via NAT on Rocky 8.8 Rocky Linux General rocky-linux-8	5	1057	January 21, 2024
Firewall d block ICMP for all allowing only few subnets Rocky Linux General rocky-linux-8	1	325	December 9, 2023
Network interface not showing in ip command Rocky Linux General	1	858	August 25, 2023
Multiple NICs on different subnets routing Rocky Linux General	2	488	August 25, 2023
Rocky Linux 9.0 connects but does not download Rocky Linux General	18	1198	August 24, 2023

Server not responding to ICMP requests

Related Topics