Bird
0
0

You run ping -c 3 192.168.1.1 and get replies, but traceroute 192.168.1.1 shows no hops. What could explain this?

hard📝 Application Q9 of 15
Linux CLI - Networking Commands
You run ping -c 3 192.168.1.1 and get replies, but traceroute 192.168.1.1 shows no hops. What could explain this?
AThe IP address is invalid
BTraceroute is blocked by firewall but ping is allowed
CPing is showing cached results
DThe network cable is unplugged
Step-by-Step Solution
Solution:

  1. Step 1: Analyze ping success and traceroute failure

    Ping replies mean connectivity; traceroute failure suggests ICMP or UDP packets blocked.

  2. Step 2: Understand firewall impact

    Firewalls can block traceroute packets but allow ping, explaining the difference.

  3. Final Answer:

    Traceroute is blocked by firewall but ping is allowed -> Option B

  4. Quick Check:

    Firewall blocking traceroute = ping works, traceroute fails [OK]
Quick Trick: Firewalls can block traceroute but allow ping [OK]
Common Mistakes:
  • Assuming IP invalid despite ping success
  • Thinking ping caches results
  • Ignoring physical connection status

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Linux CLI Quizzes
Networking Commands - scp and rsync for file transfer - Quiz 12easy Networking Commands - ping for connectivity testing - Quiz 13medium Pipes and Redirection - Why pipes chain commands into workflows - Quiz 12easy Pipes and Redirection - tee for splitting output - Quiz 11easy Pipes and Redirection - tee for splitting output - Quiz 14medium Pipes and Redirection - stderr redirection (2>, 2>>) - Quiz 7medium Process Management - ps (list processes) - Quiz 3easy Process Management - systemctl for service management - Quiz 15hard Searching and Finding - Why finding files saves time - Quiz 2easy Text Processing - tr (translate characters) - Quiz 6medium