Detection of network hops and latency through an opaque tunnel and detection misconfiguration of tunnels

A non-transitory computer-readable medium comprising instructions that, when executed, cause one or more processors associated with a client to perform steps of:

• requesting a trace to a destination with a signature inserted into a trace packet;
• receiving a response to the trace packet;
• determining whether the response includes tunnel info;
• in response to determining that the response does not include the tunnel info, providing details obtained from the response to a service where the details include parameters associated with a service path between the client and the destination;
• in response to determining that the response includes the tunnel info, segmenting the service path into a plurality of legs, causing a trace for each of the plurality of legs, aggregating details for each of the plurality of legs based on responses to the trace for each of the plurality of legs, and including a second signature in a second trace packet to an egress router to detect a network path, wherein the aggregating details includes aggregating network hops, packet drops, and latency for each of the plurality of legs;
• receiving a response from the second trace packet;
• when the response does not include a flag, utilizing details from the response for a leg between the client and the egress router;
• and
• when the response includes the flag, determining the second trace packet went on a wrong network path where the second trace packet was sent over a tunnel to a tunnel server.

A client comprising:

• one or more processors and memory comprising instructions that, when executed, cause the one or more processors to
• request a trace to a destination with a signature inserted into a trace packet;
• receive a response to the trace packet;
• determining whether the response includes tunnel info;
• in response to determining that the response does not include the tunnel info, provide details obtained from the response to a service where the details include parameters associated with a service path between the client and the destination;
• and
• in response to determining that the response includes the tunnel info, segment the service path into a plurality of legs, cause a trace for each of the plurality of legs, aggregate details for each of the plurality of legs based on responses to the trace for each of the plurality of legs, and include a second signature in a second trace packet to an egress router to detect a network path, wherein the aggregating details includes aggregating network hops, packet drops, and latency for each of the plurality of legs;
• receive a response from the second trace packet;
• when the response does not include a flag, utilize details from the response for a leg between the client and the egress router;
• and
• when the response includes the flag, determine the second trace packet went on a wrong network path where the second trace packet was sent over a tunnel to a tunnel server.