I set up 3 CentOS servers, configured server2 as router between 192.168.1.0/24 and 30.0.0.0/24, but ping
can't get through.
I tried ping 192.168.1.62
from server1, according to tcpdump
on server3, ICMP request is received, but it doesn't generate ICMP response.
23:36:06.436243 IP 30.0.0.2 > 192.168.1.62: ICMP echo request, id 23570, seq 2838, length 64
23:36:07.436212 IP 30.0.0.2 > 192.168.1.62: ICMP echo request, id 23570, seq 2839, length 64
server1:
server2:
server3:
route info on server1:
route info on server3:
Expand the Computer Configuration/Policies/Windows Settings/Security Settings/Windows Firewall with Advanced Security/Windows Firewall with Advanced Security/Inbound Rules node. From the Protocol Type: drop down list select ICMPv4 and click Customize… Check the All ICMP types radio botton and click OK.
Echo-Request and Reply: ICMP packets of echo request and reply are used to test the network layer of destination. In other words, the host at the destination is switched on or off. We can also check the network layer of all the devices on the way from sender to destination.
Enabling Ping:# iptables -D INPUT -p icmp --icmp-type echo-request -j DROP # iptables -D OUTPUT -p icmp --icmp-type echo-reply -j DROP D : This command switch is used to delete the rule. Once the ping is enabled, the server should now respond to ping requests as shown in the below image.
The Internet Control Message Protocol (ICMP) is a protocol that devices within a network use to communicate problems with data transmission. In this ICMP definition, one of the primary ways in which ICMP is used is to determine if data is getting to its destination and at the right time.
I was receiving ICMP packets but did not see them go out. The problem was related to the traffic traversing multiple interfaces and reverse path filtering being on by default...
I've enabled martian source logging first:
$ echo 1 >/proc/sys/net/ipv4/conf/eth2/log_martians
Then there are several options for what to do with them... I'm enabling loosely handling them:
$ sysctl net.ipv4.conf.all.rp_filter=2
See these for details:
Run tcpdump with -e flag and see if the destination MAC address is correct.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With