nonresponsive hop in traceroute * * * over speedfusion

Product Discussion Peplink Balance
1

Over a speedfusion connection to a fusionhub, if I do a traceroute:

  1. The first hop is the gateway IP on the balance
        • the second hop appears as nonresponsive
  3. the third hop is the gateway IP of the fusionhub

Is there a way to eliminate the nonresponsive hop for traceroute/mtr, or make it respond? Or does it have to show in tracert, but not respond to tracert, because of how a vpn tunnel works? Every time I do a tracert from windows which makes the nonresponsive hop slow as it waits sequentially for * … * … * before doing the next hop, I’m curious about the nature of the nonresponsive hop.

2

A non-responsive hop in a traceroute is likely a router/firewall/interface that is configured not to respond to those requests.

If that second hop is something within your control, you need to see if it’s blocking ICMP traffic.