Why does the host respond to hping2 and not ping packet?

You ping a target IP to check if the host is up. You do not get a response. You suspect ICMP is blocked at the firewall. Next you use hping2 tool to ping the target host and you get a response. Why does the host respond to hping2 and not ping packet?
(exhibit)

You ping a target IP to check if the host is up. You do not get a response. You suspect ICMP is blocked at the firewall. Next you use hping2 tool to ping the target host and you get a response. Why does the host respond to hping2 and not ping packet?

A.
Ping packets cannot bypass firewalls

B.
You must use ping 10.2.3.4 switch

C.
Hping2 uses stealth TCP packets to connect

D.
Hping2 uses TCP instead of ICMP by default

Explanation:
hping2 is a network tool able to send custom ICMP/UDP/TCP packets and to display target replies like ping does with ICMP replies. It handles fragmentation and arbitrary packet body and size, and can be used to transfer files under supported protocols. Using hping2, you can: Test firewall rules, Perform [spoofed] port scanning, Test net performance using different protocols, Packet size, TOS (type of service), and Fragmentation, Do path MTU discovery, Transfer files (even between really Fascist firewall rules), Perform traceroute-like actions under different protocols, Fingerprint remote OSs, Audit a TCP/IP stack, etc. hping2 is a good tool for learning TCP/IP.



Leave a Reply 1

Your email address will not be published. Required fields are marked *