Display route IP for request timeout hop issue.
Display route IP for request timeout hop issue.
I've been experimenting with routing and wondered if using tracert on Windows can reveal the IP of a non-responsive hop. It seems the route works fine despite ICMP being disabled, but you're looking for the router it passed through. Having that IP would be very useful.
You can explore https://gsuite.tools/traceroute. However, I'm uncertain if it provides the results you're looking for.
Regrettably, every router I use is set up for internal networks only, which means outside websites can't access any information.
I'm not sure about the configuration. You probably have physical access to the router, and it should display the correct address even if it ignores tracert requests. I recall in college we created a simulated GRE tunnel with a transparent middle router—tracert didn't detect it at all. Maybe that's not important here. If you don't have access, it seems like you might be trying to do something others don't want you to know about.
It’s a demo setup, so everything works as expected. Enabling ICMP would make the devices visible, but you asked if there’s a way to see their IPs without that step. Traceroute should show all routers involved, even if some don’t respond to ping—this is meant to reveal the path. You mentioned knowing the IPs already, but in this environment two routes exist and it’s timing out at the right point, making it hard to identify which router is being used.
From my perspective it behaves differently. The only known connection is the router. When instructed to reach an invalid address, it forwards the request to the router. It then waits for a reply before proceeding. The computer doesn't recognize the client until the router confirms its existence. If a router in the tracert rejects the response, it won't forward and the computer won't update its knowledge. It simply moves to the next hop. For clarity, someone with more expertise @leadeater can explain this better.
Tracert relies on routers responding with their IP addresses, not sending a specific request. It waits for replies that include the requested information. The routers detect this by acknowledging the query, which is how they know you're asking for feedback.
Traceroute transmits packets with a TTL beginning at 1 and rising by one for each hop until it reaches the target. Since the receiving router will lower the TTL by one, it stops when it hits zero and returns a time exceeded alert to the client. Continue increasing the TTL and sending another packet; the routers interface typically provides the destination IP address in these responses. Some routers may ignore these messages or allow filtering via a firewall, which usually doesn't respond unless explicitly set. Edit: Note that for certain clients, it might use UDP and randomly choose an unused port, resulting in a port unreachable message instead.