Hi everyone,
A customer of mine has a problem when she traceroutes from a management server.
She goes through a router which connects to a peering lan for BGP. The router peers with around 20 other routers on this LAN.
Basically the traceroute goes:
Server - Router A - Customer A - Customer B
It should go
Server - Router A - Customer A
In ip it is: (IP's made up!)
100.100.100.34 - 100.100.100.254 - 200.200.200.10 - 200.200.200.12
Now it gets worse:
When she does an extended traceroute from Router A it works fine to everywhere! It also works fine if she does a traceroute from the server to 200.200.200.10! All other addresses on the lan report this problem apart from 2 others 200.200.200.18 and 200.200.200.254.
Even worse when she does a recorder ping the packets hits the correct ip first time the same when she does a recorder traceroute.
We have no visibility of the other peering routers so I cannot see the config but I cannot understand why a packet destined for one ip on a lan would be responded to by another and then finally passed on to its final destination. I can't see how it can be a routing issue because an extended traceroute from the lan the server is on works fine?????
Any suggestions appreciated,
