I am confused by the following:

        Connection-specific DNS Suffix  . : some address here
        IP Address. . . . . . . . . . . . :
        Subnet Mask . . . . . . . . . . . :
        Default Gateway . . . . . . . . . :

From the above, the gateway for my pc is But when I use the tracert, the first IP address is different as you can see from the following. It is Why?


Tracing route to
over a maximum of 30 hops:

  1    29 ms    <1 ms    <1 ms
  2    <1 ms    <1 ms    <1 ms
  3     1 ms    <1 ms    <1 ms
  4    <1 ms    <1 ms    <1 ms

It looks like the gateway you're using may be using VRRP or HSRP. is a virtual/logical address, which you use as your gateway, but when you trace route one of the physical routers responds. (


Your default gateway isn't always the next hop. In fact it is generally the router of last resort. Your computer will parse the routing table and will only use the default gateway if no other more specific routes match. So do a route print and see what you find there.


From the above, the gateway for my pc is But when I use the tracert, the first IP address is different as you can see from the following. It is Why?

It is rare, but perhaps no longer has a connection to the next hop, but it still has forwarding enabled. If this is the case, with some operating systems, when you attempt to send a packet you will contact, but will return an ICMP redirect with as the address your system be using as a gateway. Since your packet is not actually being forwarded by it wouldn't show up in a trace route.

A quick capture with your favorite sniffer on your client would confirm that this is happening.

ICMP redirects are mostly discouraged these days for security reasons, so having a setup like this is uncommon.

Network Diagram


In my enterprise, the gateways are all redundant. From host side we set gateway to be, but that's a load-balanced IP managed by two routers who are actually and When you traceroute, the outbound packet goes to destination x.x.x.1, but the IGMP reply packet comes from x.x.x.2 or x.x.x.3 depending on which router is active. traceroute shows the IGMP originating address.


It could be @MikeR's answer. It could also be that your machine has a route to the address that doesn't go through the default gateway, but instead goes through Check your host's routing table to see if that's the case.


I was also facing the same problem. I am using Sonicwall device in between. Some firewall settings blocked it from showing the IP in tracert.

For this Please login to DELL SONICWALL --> Firewall Settings -->Advanced

there enable check against Decrement IP TTL for forwarded traffic under Detection Prevention and test it and let me know is that is help full.


I agree with Ryan and I think your computer is parsing your routing table and that's why it's not sending you to default gateway. You can use this to flush your route table:

sudo ip route flush table main

Then you can again run this to make sure your route table is empty:

route -n

Now you can reset your internet so that your route table gets default values, and your problem will be solved.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.