[Networking] "gateway" vs. traceroute
My router reports a "gateway" IP address of one thing, e.g. 188.8.131.52, but traceroutes never go through that IP. Rather the next hop will be some other IP address, e.g. 184.108.40.206. Is this some sort of load-balancing thing? If so, could someone explain to me how it's implemented, or point me to an online resource?
Google MPLS. Also, if you are PPPoE the trace could be stripping out the PPPoE concentrator IP.
Thanks very much! (I'm not on PPPoE by the way.) Looks like I have some reading to do!
|reply to nycdave |
Not sure how MPLS would come into this particular problem.
But I see 2 possibilities, 1: The gateway is not reducing the TTL by 1 thus the packet goes trough without expiring, or 2: The gateway is responding to the TTL expired with a different one of its IP addresses and the first Verizon hop you see is probably really it.
I'm leaning on #2
ASUS M4A79T Deluxe | AMD Phenom II x3 720 BE AM3 w/4 Cores @ 3.41Ghz(OC) | 8GB DDR3 Memory @ 1600mhz | Sapphire ATI HD4870 1GB 800mhz/1000mhz(OC) | 2x500GB HDD's Raid 0 | Windows 7 Ultimate x64| Windstream DSL 12m (14.9m Sync)/766k
|reply to uncle6 |
When a router has two or more IPs such as your gateway router at Verizon it will always show you the WAN IP of that router that your route is using, which is it's link to the next hop.
Not always, but it can.