02-02-2019 06:52 AM - edited 03-05-2019 11:14 AM
Yesterday, I tried using normal traceroute to see my hops to Google DNS. Every time I issued that command on my router, it would fail before hitting the internet. Even when I tried an extended traceroute, without a source, it would fail before getting out onto the internet. I was told to use an extended traceroute and source the IP address of that router's LAN... That allowed a successful traceroute to Google DNS, displaying all of the hops used to get there.
What would cause an extended traceroute or ping, require a specific source address range and/or VLAN to give accurate communication information?
Thanks,
Jelani
02-02-2019 07:14 AM
It just means that there was a route back to the IP you used as the source for the traceroute whereas without that it used the IP of the exit interface for which there was no route back.
That is a bit unusual if this is an internet connected router but I have see that behaviour in MPLS networks where the CE to PE subnet is not necessarily advertised between sites.
Jon
02-02-2019 07:30 AM
Hi, Jon.
Actually, the next hop from the last (MPLS) router displayed, should have been the gateway of another internal (Internet) router. From that Internet router, the next hop should been via its public facing interface. And, then a list of ISP routers should have displayed.
MPLS Hub Router -> LAN GW on Internal Internet Router -> Public Facing Interface on Internal Internet Router -> ISP Routers... -> Google DNS.
02-02-2019 07:35 AM - edited 02-02-2019 07:51 AM
If it is MPLS then you may just be advertising the LAN network to the rest of the network.
Difficult to say but it does sound like the behaviour I have seen before.
Jon
02-02-2019 07:42 AM
So, Jon, you're saying that other devices aren't aware how to get to the PE's equipment for internet connectivity in an MPLS network?
02-02-2019 07:50 AM
It's difficult to tell without seeing routing tables etc.
What I am saying though is that with MPLS you don't necessarily need to advertise the CE to PE link in which case if you ping from the CE there might not be a route back.
But of course you would need to advertise the LAN behind the CE so there should always be routes back.
Whether that is your problem like I say it is diffcult to say.
Jon
02-02-2019 07:57 AM
What's appropriate to post, when it comes to workplace network device configs?
Curious...
02-02-2019 08:01 AM
It's up to you and your company policy really.
Obviously you would need to remove any sensitive information and the configurations contain public IPs then best to replace some of the octets with "x" or something similar, our just use private IPs and make it clear what you have done.
Jon
02-02-2019 07:20 AM
Hello,
can you post the config of your router ? We might spot something unusual...normally, traceroute and ping use the outgoing interface by default, and hence, should succeed...
02-02-2019 07:35 AM
Hi, Georg.
Anything, in particular?
02-02-2019 08:03 AM
Thanks, Jon. Appreciate your feedback.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide