Differences

This shows you the differences between two versions of the page.

--- mpls_traceroute [2014/02/08 20:57] – samer
+++ mpls_traceroute [2014/02/15 23:38] (current) – samer
@@ Line 6: / Line 6: @@
 For example, a traceroute to ''www.univ-rennes1.fr'' reveals the different hops toward the destination:
-<code>
+<code shell>
 $ traceroute -P icmp www.univ-rennes1.fr
 traceroute to frontalhttp.univ-rennes1.fr (129.20.126.100), 64 hops max, 72 byte packets
@@ Line 21: / Line 21: @@
 </code>
-Examining the detail of the received ICMP time exceeded messages with Wireshark reveals an ICMP Multi-part extension that carries the MPLS label as it arrived to the hop sending the message. In the following capture, we note that ''te4-2-rouen-rtr-021.noc.renater.fr'' received label 53, most probably from the MPLS edge router ''renater-ix1.sfinx.tm.fr''.
+Examining the detail of the received ICMP time exceeded messages with Wireshark reveals an ICMP Multi-part extension that carries the MPLS label as it arrived to the hop sending the message. In the following capture, the router ''te4-2-rouen-rtr-021.noc.renater.fr'' received label 53, most probably from the MPLS edge router ''renater-ix1.sfinx.tm.fr''.
-<code>
+<code shell>
 No.     Time           Source                Destination           Protocol Length Info
 5.947446000    193.51.189.50         192.168.1.24          ICMP     182    Time-to-live exceeded (Time to live exceeded in transit)
@@ Line 50: / Line 50: @@
 </code>
-[[http://www.bitwizard.nl/mtr | MTR]] is an adapted tool for capturing the MPLS label switching with a traceroute-like command:
+In order to easily visualise the label switching, [[http://www.bitwizard.nl/mtr | MTR]] produces a traceroute-like result with labels used at each hop:
-<code>
+<code shell>
-$mtr -e www.univ-rennes1.fr
+$ mtr -e www.univ-rennes1.fr
 . neufbox
 . 129.112.16.109.rev.sfr.net