<![CDATA[Traceroute command shows the last hop's DNS entry and IP address for ALL hops]]>Traceroute command shows the last hop's DNS entry and IP address for ALL hops.

Example:
Tracing route to www.google.com [172.217.10.100]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms pfSense.local [192.168.1.1]
2 9 ms 7 ms 9 ms lga34s15-in-f4.1e100.net [172.217.10.100]
3 9 ms 12 ms 9 ms lga34s15-in-f4.1e100.net [172.217.10.100]
4 21 ms 22 ms 28 ms lga34s15-in-f4.1e100.net [172.217.10.100]
5 21 ms 20 ms 21 ms lga34s15-in-f4.1e100.net [172.217.10.100]
6 22 ms 23 ms 21 ms lga34s15-in-f4.1e100.net [172.217.10.100]
7 22 ms 22 ms 24 ms lga34s15-in-f4.1e100.net [172.217.10.100]
8 22 ms 24 ms 24 ms lga34s15-in-f4.1e100.net [172.217.10.100]
9 21 ms 24 ms 21 ms lga34s15-in-f4.1e100.net [172.217.10.100]
10 23 ms 23 ms 24 ms lga34s15-in-f4.1e100.net [172.217.10.100]
11 19 ms 25 ms 21 ms lga34s15-in-f4.1e100.net [172.217.10.100]
12 22 ms 22 ms 20 ms lga34s15-in-f4.1e100.net [172.217.10.100]

Its showing this on a trace route iphone app on wifi and also on windows 10 tracert command.

Any idea why the hops in between don't resolve the proper ip / name?

]]>https://forum.netgate.com/topic/151485/traceroute-command-shows-the-last-hop-s-dns-entry-and-ip-address-for-all-hopsRSS for NodeThu, 15 Oct 2026 07:42:21 GMTFri, 20 Mar 2020 12:58:00 GMT60<![CDATA[Reply to Traceroute command shows the last hop's DNS entry and IP address for ALL hops on Fri, 20 Mar 2020 13:10:23 GMT]]>I found another thread with a solution. Aparently its a bug when you have CODEL limiters on to fix bufferbloat.

I created a floating firewall rule for IPV4 and IPV6 ICMP all, any direction, and apply immediately.

Credit, this thread : https://forum.netgate.com/topic/142274/traceroute-not-working-from-lan-to-any-internet-destination

]]>https://forum.netgate.com/post/898037https://forum.netgate.com/post/898037Fri, 20 Mar 2020 13:10:23 GMT