A ping (ICMP traffic) from my VM to e.g. netbraintech.com takes a different path than an Web request (HTTP(S)) traffic to netbraintech.com:
(1) ping: VM => hop A => hop B => hop C => internet border router => Internet.
(2) Web: VM => hop A => hop X => web-proxy => hop Y => internet border router => Internet.
However, NetBrain can only map the 1st (ping type) path because it’s not aware that VMs in our company are configured with proxy settings for Web traffic.
Therefore, to get the 2nd path, I have to trace 2 separate paths: from VM to proxy; from proxy to internet.
With the following enhancement to the path trace tool NetBrain could perhaps trace both paths on my behalf and stitch them together into a single path:
- add an optional “Proxy” field to path trace tool;
- if it’s blank, do a normal path trace;
- if it has a device name, trace from source to that device, then from that device to destination.
I’m aware of Path IP and Gateway fix-up rules, but when using them, the trace from source to proxy is displayed as a single step whereas in reality it’s not.