Academic
Publications
MERLIN: MEasure the router level of the INternet

MERLIN: MEasure the router level of the INternet,10.1109/NGI.2011.5985865,Pascal Merindol,Benoit Donnet,Jean-Jacques Pansiot,Matthew Luckie,Young Hyun

MERLIN: MEasure the router level of the INternet   (Citations: 2)
BibTex | RIS | RefWorks Download
In this paper, we present a new router-level Internet mapping tool called MERLIN. MERLIN takes advantage of mrinfo, a multicast management tool that collects all IPv4 multicast enabled interfaces of a router and all its multicast links towards its neighbors. Our new probing tool fixes mrinfo technical limitations and eases the deployment of multicast probing campaign. We deploy and evaluate the performance of MERLIN at large scale. We investigate the completeness of MERLIN by providing a lower bound on the proportion of information that it may miss. We also demonstrate that the use of several vantage points is crucial to circumvent IGMP filtering in order to increase the amount of collected routers. MERLIN is a valuable tool for collecting the router-level Internet topology.
Cumulative Annual
View Publication
The following links allow you to view full publications. These links are maintained by other sources not affiliated with Microsoft Academic Search.
    • ...tasks as follows: (1) if a new router has been discovered, it marks all its local addresses as already seen, (2) if there exist recursive IP addresses to probe, it elapses the probing with the timer ®, (3) otherwise it uses the static list and elapses probes with the timer ¯. Those choices have been made regarding several considerations detailed in [20] in order to reduce the probability to reprobe the same router...

    Pascal Merindolet al. MERLIN: MEasure the router level of the INternet

    • ...Such sudden and significant changes are not due to network dynamics: they are an artifact of mrinfo-rec launched from a single vantage point, making data collection susceptible to IGMP filtering (more collaborating vantage points help to overcome such situations, see Sec. III-D and [21])...
    • ...A complete description of the architecture and a detailed analysis of the collected data are reported in [21] and [22]...
    • ...This recursion first scheme was a design choice that has been made in order to minimize the probability of reprobing a given router (see [21] for details)...
    • ...Interested readers can find more details in [21]...
    • ...As described in [21], the IP interface list of a given router returned by mrinfo may be incomplete (see Sec...
    • ...This situation is illustrated in Fig. 6: a traceroute path consecutively crosses components A and B. Furthermore, as suggested in previous work [21], if a unicast IP address of a multicast responding router is discovered through a traceroute path, then, at the next stage, if this IP responds to one of the monitor, the server aliases this unicast IP address with the previously collected multicast router (the server merges the two responses ...
    • ...7 This lack is due to multicast routers responding with a unicast IP address not present in the list of multicast reported interfaces [21]...
    • ...readers may find explanations about those values in [21]...

    Pietro Marchettaet al. Topology Discovery at the Router Level: A New Hybrid Tool Targeting IS...

Sort by: