The Experts below are selected from a list of 261 Experts worldwide ranked by ideXlab platform
Bownan Cheng - One of the best experts on this subject based on the ideXlab platform.
-
Characterizing Routing with Radio-to-Router Information in a Heterogeneous Airborne Network
IEEE Transactions on Wireless Communications, 2013Co-Authors: Bownan Cheng, Andrea Coyle, Igor Pedan, Leonid Veytser, S. Mcgarry, James WheelerAbstract:The current generation of long-range, high capacity, military radios are stove-piped systems that work well in a homogeneous environment, but lack interoperability with other radio systems. Each radio provides a subset of disparate link information in non-standard Interfaces and has built-in home-grown Routers running different routing protocols. In a heterogeneous radio system airborne environment, wireless link characteristics change rapidly, often requiring direct link feedback from the radio to make routing decisions. In recent years, much work has been done in developing a common radio-to-Router Interface (R2RI) that standardizes a subset of per-link information to pass to the network layer for use in dynamic MANET routing. While simulations and emulation tests can provide a baseline for how systems might perform, field-tests are crucial to demonstrate capabilities in real-world operating environments. In this paper, we present measurement results from a field test involving several air and ground assets with various radio systems that test an implementation of RFC4938, a radio-to-Router Interface protocol, and its interaction with a dynamic MANET routing protocol. The assets formed a high capacity, dynamically routed aerial IP backbone made of heterogeneous radio technologies over 250 nautical miles (Nm), allowing the passing of military traffic.
-
radio to Router Interface technology and its applicability on the tactical edge
IEEE Communications Magazine, 2012Co-Authors: Bownan Cheng, James Wheeler, Leonid VeytserAbstract:Tactical wireless and mobile networks are the primary networking infrastructure in the Global Information Grid (GIG) to provide end-to-end connectivity to the warfighters at the tactical edge. The highly dynamic nature of tactical edge networks raise a number of challenging issues related to data transport and service delivery in the tactical environment. To address some of these issues, DoD waveforms have increasingly leveraged layer 2 link information to make smart cross-layer multihop routing decisions. Although there has been some measure of success in providing higher end-to-end data delivery, the lack of standard Interfaces between the radio and Router have led to interoperability issues in environments with a heterogeneous mix of radio systems. As a result, there has been increased desire to standardize radio-to-Router Interfaces (R2RIs) as a means to separate radio and Router functionality and to allow greater interoperability between systems. In this article, we examine three R2RI protocols currently being vetted through the Internet Engineering Task Force and currently integrated or under consideration in DoD radio systems (RFC 5578, R2CP, and DLEP), and identify their current use and applicability in the tactical edge. Furthermore, we identify some challenges in implementing any R2RI scheme into emerging systems.
-
comparing radio to Router Interface implementations on experimental cots and open source Routers
Military Communications Conference, 2012Co-Authors: Bownan Cheng, Andrea Coyle, Randy Charland, Paul Christensen, Igor Pedan, Leonid Veytser, James WheelerAbstract:In highly dynamic wireless environments, link metrics such as link quality, availability, and others have become increasingly important to enable smart multi-hop routing decisions. In recent years, a number of radio-to-Router Interface (R2RI) protocols such as Point-to-Point over Ethernet RFC5578, Dynamic Link Exchange Protocol (DLEP), and Radio-Router Control Protocol (R2CP) have emerged to address the need to have a common set of link metrics exposed from the radio to the Router to enhance multi-hop routing decisions. To fully evaluate R2RI functionality and specifications, differing implementations of both radio/client and Router/server-side R2RI protocols must be prototyped and tested. In this paper, we present comparison tests of each of the three (3) radio-to-Router Interfaces with two (2) Router/server-side R2RI experimental/beta R2RI implementations: one on a commercial Cisco Router, and one on an open source Quagga platform. The goal of the comparison is not necessarily to provide a holistic performance comparison (as much of the code is experimental), but to highlight implementation differences and potential issues. In many cases, issues are already resolved in future releases.1
-
MILCOM - Comparing radio-to-Router Interface implementations on experimental CoTs and open source Routers
MILCOM 2012 - 2012 IEEE Military Communications Conference, 2012Co-Authors: Bownan Cheng, Andrea Coyle, Randy Charland, Paul Christensen, Igor Pedan, Leonid Veytser, James WheelerAbstract:In highly dynamic wireless environments, link metrics such as link quality, availability, and others have become increasingly important to enable smart multi-hop routing decisions. In recent years, a number of radio-to-Router Interface (R2RI) protocols such as Point-to-Point over Ethernet RFC5578, Dynamic Link Exchange Protocol (DLEP), and Radio-Router Control Protocol (R2CP) have emerged to address the need to have a common set of link metrics exposed from the radio to the Router to enhance multi-hop routing decisions. To fully evaluate R2RI functionality and specifications, differing implementations of both radio/client and Router/server-side R2RI protocols must be prototyped and tested. In this paper, we present comparison tests of each of the three (3) radio-to-Router Interfaces with two (2) Router/server-side R2RI experimental/beta R2RI implementations: one on a commercial Cisco Router, and one on an open source Quagga platform. The goal of the comparison is not necessarily to provide a holistic performance comparison (as much of the code is experimental), but to highlight implementation differences and potential issues. In many cases, issues are already resolved in future releases.1
-
MILCOM - Integrating radio-to-Router protocols into EMANE
MILCOM 2012 - 2012 IEEE Military Communications Conference, 2012Co-Authors: Leonid Veytser, Bownan Cheng, Randy CharlandAbstract:In highly dynamic wireless environments, link metrics such as link quality, availability, and others have become increasingly important to enable smart multi-hop routing decisions. In recent years, a number of radio-to-Router Interface (R2RI) protocols such as Point-to-Point over Ethernet RFC5578, Dynamic Link Exchange Protocol (DLEP), and Radio-Router Control Protocol (R2CP) have emerged to address the need to have a common set of link metrics exposed from the radio to the Router to enhance multi-hop routing decisions. In the past, testing R2RI required separate processes and proxies to convert layer 2 link metrics into R2RI standard formats. Although useful for allowing legacy radio systems to comply with R2RI formats, the proxy technique is difficult for building large-scale (100+ node) test environments with emulated radios and Routers. In this paper, we describe modifications made to a popular open source link emulator, EMANE, to support emerging radio-to-Router Interface (R2RI) standards, DLEP and R2CP, on several EMANE MAC models including 802.11 and CommEffect. Additionally, a functional evaluation of the system is performed.1
James Wheeler - One of the best experts on this subject based on the ideXlab platform.
-
Characterizing Routing with Radio-to-Router Information in a Heterogeneous Airborne Network
IEEE Transactions on Wireless Communications, 2013Co-Authors: Bownan Cheng, Andrea Coyle, Igor Pedan, Leonid Veytser, S. Mcgarry, James WheelerAbstract:The current generation of long-range, high capacity, military radios are stove-piped systems that work well in a homogeneous environment, but lack interoperability with other radio systems. Each radio provides a subset of disparate link information in non-standard Interfaces and has built-in home-grown Routers running different routing protocols. In a heterogeneous radio system airborne environment, wireless link characteristics change rapidly, often requiring direct link feedback from the radio to make routing decisions. In recent years, much work has been done in developing a common radio-to-Router Interface (R2RI) that standardizes a subset of per-link information to pass to the network layer for use in dynamic MANET routing. While simulations and emulation tests can provide a baseline for how systems might perform, field-tests are crucial to demonstrate capabilities in real-world operating environments. In this paper, we present measurement results from a field test involving several air and ground assets with various radio systems that test an implementation of RFC4938, a radio-to-Router Interface protocol, and its interaction with a dynamic MANET routing protocol. The assets formed a high capacity, dynamically routed aerial IP backbone made of heterogeneous radio technologies over 250 nautical miles (Nm), allowing the passing of military traffic.
-
radio to Router Interface technology and its applicability on the tactical edge
IEEE Communications Magazine, 2012Co-Authors: Bownan Cheng, James Wheeler, Leonid VeytserAbstract:Tactical wireless and mobile networks are the primary networking infrastructure in the Global Information Grid (GIG) to provide end-to-end connectivity to the warfighters at the tactical edge. The highly dynamic nature of tactical edge networks raise a number of challenging issues related to data transport and service delivery in the tactical environment. To address some of these issues, DoD waveforms have increasingly leveraged layer 2 link information to make smart cross-layer multihop routing decisions. Although there has been some measure of success in providing higher end-to-end data delivery, the lack of standard Interfaces between the radio and Router have led to interoperability issues in environments with a heterogeneous mix of radio systems. As a result, there has been increased desire to standardize radio-to-Router Interfaces (R2RIs) as a means to separate radio and Router functionality and to allow greater interoperability between systems. In this article, we examine three R2RI protocols currently being vetted through the Internet Engineering Task Force and currently integrated or under consideration in DoD radio systems (RFC 5578, R2CP, and DLEP), and identify their current use and applicability in the tactical edge. Furthermore, we identify some challenges in implementing any R2RI scheme into emerging systems.
-
comparing radio to Router Interface implementations on experimental cots and open source Routers
Military Communications Conference, 2012Co-Authors: Bownan Cheng, Andrea Coyle, Randy Charland, Paul Christensen, Igor Pedan, Leonid Veytser, James WheelerAbstract:In highly dynamic wireless environments, link metrics such as link quality, availability, and others have become increasingly important to enable smart multi-hop routing decisions. In recent years, a number of radio-to-Router Interface (R2RI) protocols such as Point-to-Point over Ethernet RFC5578, Dynamic Link Exchange Protocol (DLEP), and Radio-Router Control Protocol (R2CP) have emerged to address the need to have a common set of link metrics exposed from the radio to the Router to enhance multi-hop routing decisions. To fully evaluate R2RI functionality and specifications, differing implementations of both radio/client and Router/server-side R2RI protocols must be prototyped and tested. In this paper, we present comparison tests of each of the three (3) radio-to-Router Interfaces with two (2) Router/server-side R2RI experimental/beta R2RI implementations: one on a commercial Cisco Router, and one on an open source Quagga platform. The goal of the comparison is not necessarily to provide a holistic performance comparison (as much of the code is experimental), but to highlight implementation differences and potential issues. In many cases, issues are already resolved in future releases.1
-
MILCOM - Comparing radio-to-Router Interface implementations on experimental CoTs and open source Routers
MILCOM 2012 - 2012 IEEE Military Communications Conference, 2012Co-Authors: Bownan Cheng, Andrea Coyle, Randy Charland, Paul Christensen, Igor Pedan, Leonid Veytser, James WheelerAbstract:In highly dynamic wireless environments, link metrics such as link quality, availability, and others have become increasingly important to enable smart multi-hop routing decisions. In recent years, a number of radio-to-Router Interface (R2RI) protocols such as Point-to-Point over Ethernet RFC5578, Dynamic Link Exchange Protocol (DLEP), and Radio-Router Control Protocol (R2CP) have emerged to address the need to have a common set of link metrics exposed from the radio to the Router to enhance multi-hop routing decisions. To fully evaluate R2RI functionality and specifications, differing implementations of both radio/client and Router/server-side R2RI protocols must be prototyped and tested. In this paper, we present comparison tests of each of the three (3) radio-to-Router Interfaces with two (2) Router/server-side R2RI experimental/beta R2RI implementations: one on a commercial Cisco Router, and one on an open source Quagga platform. The goal of the comparison is not necessarily to provide a holistic performance comparison (as much of the code is experimental), but to highlight implementation differences and potential issues. In many cases, issues are already resolved in future releases.1
-
a testbed to support radio to Router Interface testing and evaluation
Military Communications Conference, 2011Co-Authors: Randy Charland, Paul Christensen, James Wheeler, Bownan ChengAbstract:In highly dynamic airborne and wireless environments, per link information becomes crucial in effectively routing packets throughout the network and preserving application QoS. In recent years, a number of radio-to-Router protocols such as Point-to-Point over Ethernet RFC55781, Dynamic Link Exchange Protocol (DLEP), and Radio-to-Router Control Protocol (R2CP) have emerged to provide per link information from radio-to-Router to help make more informed routing decisions on highly dynamic links operating at various data rates and to possibly provide flow control. In addition, integrating and testing radio-to-Router protocols with both unicast and multicast routing protocols designed to operate in MANET environments provides fundamental insights into the their performance and real-world utility. To effectively evaluate each of the Radio-to-Router protocols and understand some of the practical implementation issues, a flexible testbed supporting multiple emulated DoD radios and their link characteristics, as well as multiple open source and commercial Routers that support radio-aware routing is needed. In this paper, we present a 6-node testbed that supports emulation of several directional, electronic switch-beam, and omnidirectional radio technologies as well as routing technologies to help automate evaluation and testing of RFC5578, DLEP, and R2CP. Specifically, we describe the system setup, some challenges with supporting current DoD radio technologies and temporary solutions, and provide some examples of results and data derived from multiple runs on the emulation network.2
Randolph Marchany - One of the best experts on this subject based on the ideXlab platform.
-
RIM: Router Interface marking for IP traceback
GLOBECOM - IEEE Global Telecommunications Conference, 2006Co-Authors: Ruiliang Chen, Jung Min Park, Randolph MarchanyAbstract:Distributed Denial-of-Service (DDoS) attacks have become a major threat to the Internet. As a countermeasure against DDoS attacks, IP traceback schemes identify the network paths the attack traffic traverses. This paper presents a novel IP traceback scheme called Router Interface Marking (RIM). In RIM, a Router probabilistically marks packets with a Router Interface's identifier. After collecting the packets marked by each Router in an attack path, a victim machine can use the information in the marked packets to trace back to the attack source. Different from most existing IP traceback schemes, RIM marks packets with the information of Router Interfaces rather than that of Router IP addresses. This difference endows RIM with several advantageous features, including fast traceback speed, last-hop traceback capability, small computation overhead, low occurrence of false positives, and enhanced security.
-
GLOBECOM - RIM: Router Interface Marking for IP Traceback
2006Co-Authors: Ruiliang Chen, Jung Min Park, Randolph MarchanyAbstract:Distributed Denial-of-Service (DDoS) attacks have become a major threat to the Internet. As a countermeasure against DDoS attacks, IP traceback schemes identify the network paths the attack traffic traverses. This paper presents a novel IP traceback scheme called Router Interface Marking (RIM). In RIM, a Router probabilistically marks packets with a Router Interface's identifier. After collecting the packets marked by each Router in an attack path, a victim machine can use the information in the marked packets to trace back to the attack source. Different from most existing IP traceback schemes, RIM marks packets with the information of Router Interfaces rather than that of Router IP addresses. This difference endows RIM with several advantageous features, including fast traceback speed, last-hop traceback capability, small computation overhead, low occurrence of false positives, and enhanced security.
-
NISp1-05: RIM: Router Interface Marking for IP Traceback
IEEE Globecom 2006, 2006Co-Authors: Ruiliang Chen, Jung Min Park, Randolph MarchanyAbstract:Distributed Denial-of-Service (DDoS) attacks have become a major threat to the Internet. As a countermeasure against DDoS attacks, IP traceback schemes identify the network paths the attack traffic traverses. This paper presents a novel IP traceback scheme called Router Interface Marking (RIM). In RIM, a Router probabilistically marks packets with a Router Interface's identifier. After collecting the packets marked by each Router in an attack path, a victim machine can use the information in the marked packets to trace back to the attack source. Different from most existing IP traceback schemes, RIM marks packets with the information of Router Interfaces rather than that of Router IP addresses. This difference endows RIM with several advantageous features, including fast traceback speed, last-hop traceback capability, small computation overhead, low occurrence of false positives, and enhanced security.
-
TRACK: A Novel Approach for Defending Against Distributed Denial-of-Service Attacks
2005Co-Authors: Ruiliang Chen, Jung Min Park, Randolph MarchanyAbstract:This paper presents a novel countermeasure against Distributed Denial-of-Service (DDoS) attacks that we call the Router poRt mArking and paCKet filtering (TRACK), which includes the functions of both IP traceback and packet filtering. TRACK is a comprehensive solution that is composed of two components: a Router port marking module and a packet filtering module. The former is a novel packet marking scheme for IP traceback and the latter is a novel packet filtering scheme that utilizes the information gathered from the former component. The Router port marking scheme marks packets by probabilistically writing a Router Interface's port number, a locally unique 6-digit identifier, to the packets it transmits. After collecting the packets marked by each Router in an attacking path, a victim machine can use the information contained in those packets to trace the attack back to its source (i.e., solve the "IP traceback" problem). In the packet filtering component, the information contained in the same packets are used to filter the malicious packets at the upstream Routers (i.e., Routers located in the direction towards the attackers), thus effectively mitigating attacks. Because very little space is required to mark a port number, TRACK allows us to include attack signature information along with the port number within a single packet's IP header. The resulting advantage is three fold: (1) a significantly less number of packets need to be collected to traceback the attack source compared to previous IP traceback schemes, (2) very little computation overhead is required in the traceback process, and (3) scalability: a large number of attackers (i.e., zombies) can be traced back efficiently. Because TRACK uses the Router Interface instead of the entire Router as the "atomic unit" for IP traceback and packet filtering, it can accomplish these tasks with much finer granularity, which helps to lower the false positives. In the paper, we also show that TRACK supports gradual deployment .
Leonid Veytser - One of the best experts on this subject based on the ideXlab platform.
-
Characterizing Routing with Radio-to-Router Information in a Heterogeneous Airborne Network
IEEE Transactions on Wireless Communications, 2013Co-Authors: Bownan Cheng, Andrea Coyle, Igor Pedan, Leonid Veytser, S. Mcgarry, James WheelerAbstract:The current generation of long-range, high capacity, military radios are stove-piped systems that work well in a homogeneous environment, but lack interoperability with other radio systems. Each radio provides a subset of disparate link information in non-standard Interfaces and has built-in home-grown Routers running different routing protocols. In a heterogeneous radio system airborne environment, wireless link characteristics change rapidly, often requiring direct link feedback from the radio to make routing decisions. In recent years, much work has been done in developing a common radio-to-Router Interface (R2RI) that standardizes a subset of per-link information to pass to the network layer for use in dynamic MANET routing. While simulations and emulation tests can provide a baseline for how systems might perform, field-tests are crucial to demonstrate capabilities in real-world operating environments. In this paper, we present measurement results from a field test involving several air and ground assets with various radio systems that test an implementation of RFC4938, a radio-to-Router Interface protocol, and its interaction with a dynamic MANET routing protocol. The assets formed a high capacity, dynamically routed aerial IP backbone made of heterogeneous radio technologies over 250 nautical miles (Nm), allowing the passing of military traffic.
-
radio to Router Interface technology and its applicability on the tactical edge
IEEE Communications Magazine, 2012Co-Authors: Bownan Cheng, James Wheeler, Leonid VeytserAbstract:Tactical wireless and mobile networks are the primary networking infrastructure in the Global Information Grid (GIG) to provide end-to-end connectivity to the warfighters at the tactical edge. The highly dynamic nature of tactical edge networks raise a number of challenging issues related to data transport and service delivery in the tactical environment. To address some of these issues, DoD waveforms have increasingly leveraged layer 2 link information to make smart cross-layer multihop routing decisions. Although there has been some measure of success in providing higher end-to-end data delivery, the lack of standard Interfaces between the radio and Router have led to interoperability issues in environments with a heterogeneous mix of radio systems. As a result, there has been increased desire to standardize radio-to-Router Interfaces (R2RIs) as a means to separate radio and Router functionality and to allow greater interoperability between systems. In this article, we examine three R2RI protocols currently being vetted through the Internet Engineering Task Force and currently integrated or under consideration in DoD radio systems (RFC 5578, R2CP, and DLEP), and identify their current use and applicability in the tactical edge. Furthermore, we identify some challenges in implementing any R2RI scheme into emerging systems.
-
comparing radio to Router Interface implementations on experimental cots and open source Routers
Military Communications Conference, 2012Co-Authors: Bownan Cheng, Andrea Coyle, Randy Charland, Paul Christensen, Igor Pedan, Leonid Veytser, James WheelerAbstract:In highly dynamic wireless environments, link metrics such as link quality, availability, and others have become increasingly important to enable smart multi-hop routing decisions. In recent years, a number of radio-to-Router Interface (R2RI) protocols such as Point-to-Point over Ethernet RFC5578, Dynamic Link Exchange Protocol (DLEP), and Radio-Router Control Protocol (R2CP) have emerged to address the need to have a common set of link metrics exposed from the radio to the Router to enhance multi-hop routing decisions. To fully evaluate R2RI functionality and specifications, differing implementations of both radio/client and Router/server-side R2RI protocols must be prototyped and tested. In this paper, we present comparison tests of each of the three (3) radio-to-Router Interfaces with two (2) Router/server-side R2RI experimental/beta R2RI implementations: one on a commercial Cisco Router, and one on an open source Quagga platform. The goal of the comparison is not necessarily to provide a holistic performance comparison (as much of the code is experimental), but to highlight implementation differences and potential issues. In many cases, issues are already resolved in future releases.1
-
MILCOM - Comparing radio-to-Router Interface implementations on experimental CoTs and open source Routers
MILCOM 2012 - 2012 IEEE Military Communications Conference, 2012Co-Authors: Bownan Cheng, Andrea Coyle, Randy Charland, Paul Christensen, Igor Pedan, Leonid Veytser, James WheelerAbstract:In highly dynamic wireless environments, link metrics such as link quality, availability, and others have become increasingly important to enable smart multi-hop routing decisions. In recent years, a number of radio-to-Router Interface (R2RI) protocols such as Point-to-Point over Ethernet RFC5578, Dynamic Link Exchange Protocol (DLEP), and Radio-Router Control Protocol (R2CP) have emerged to address the need to have a common set of link metrics exposed from the radio to the Router to enhance multi-hop routing decisions. To fully evaluate R2RI functionality and specifications, differing implementations of both radio/client and Router/server-side R2RI protocols must be prototyped and tested. In this paper, we present comparison tests of each of the three (3) radio-to-Router Interfaces with two (2) Router/server-side R2RI experimental/beta R2RI implementations: one on a commercial Cisco Router, and one on an open source Quagga platform. The goal of the comparison is not necessarily to provide a holistic performance comparison (as much of the code is experimental), but to highlight implementation differences and potential issues. In many cases, issues are already resolved in future releases.1
-
MILCOM - Integrating radio-to-Router protocols into EMANE
MILCOM 2012 - 2012 IEEE Military Communications Conference, 2012Co-Authors: Leonid Veytser, Bownan Cheng, Randy CharlandAbstract:In highly dynamic wireless environments, link metrics such as link quality, availability, and others have become increasingly important to enable smart multi-hop routing decisions. In recent years, a number of radio-to-Router Interface (R2RI) protocols such as Point-to-Point over Ethernet RFC5578, Dynamic Link Exchange Protocol (DLEP), and Radio-Router Control Protocol (R2CP) have emerged to address the need to have a common set of link metrics exposed from the radio to the Router to enhance multi-hop routing decisions. In the past, testing R2RI required separate processes and proxies to convert layer 2 link metrics into R2RI standard formats. Although useful for allowing legacy radio systems to comply with R2RI formats, the proxy technique is difficult for building large-scale (100+ node) test environments with emulated radios and Routers. In this paper, we describe modifications made to a popular open source link emulator, EMANE, to support emerging radio-to-Router Interface (R2RI) standards, DLEP and R2CP, on several EMANE MAC models including 802.11 and CommEffect. Additionally, a functional evaluation of the system is performed.1
Christos Papadopoulos - One of the best experts on this subject based on the ideXlab platform.
-
a look at Router geolocation in public and commercial databases
Internet Measurement Conference, 2017Co-Authors: Manaf Gharaibeh, Anant Shah, Bradley Huffaker, Han Zhang, Roya Ensafi, Christos PapadopoulosAbstract:Internet measurement research frequently needs to map infrastructure components, such as Routers, to their physical locations. Although public and commercial geolocation services are often used for this purpose, their accuracy when applied to network infrastructure has not been sufficiently assessed. Prior work focused on evaluating the overall accuracy of geolocation databases, which is dominated by their performance on end-user IP addresses. In this work, we evaluate the reliability of Router geolocation in databases. We use a dataset of about 1.64M Router Interface IP addresses extracted from the CAIDA Ark dataset to examine the country- and city-level coverage and consistency of popular public and commercial geolocation databases. We also create and provide a ground-truth dataset of 16,586 Router Interface IP addresses and their city-level locations, and use it to evaluate the databases' accuracy with a regional breakdown analysis. Our results show that the databases are not reliable for geolocating Routers and that there is room to improve their country- and city-level accuracy. Based on our results, we present a set of recommendations to researchers concerning the use of geolocation databases to geolocate Routers.
-
Internet Measurement Conference - A look at Router geolocation in public and commercial databases
Proceedings of the 2017 Internet Measurement Conference, 2017Co-Authors: Manaf Gharaibeh, Anant Shah, Bradley Huffaker, Han Zhang, Roya Ensafi, Christos PapadopoulosAbstract:Internet measurement research frequently needs to map infrastructure components, such as Routers, to their physical locations. Although public and commercial geolocation services are often used for this purpose, their accuracy when applied to network infrastructure has not been sufficiently assessed. Prior work focused on evaluating the overall accuracy of geolocation databases, which is dominated by their performance on end-user IP addresses. In this work, we evaluate the reliability of Router geolocation in databases. We use a dataset of about 1.64M Router Interface IP addresses extracted from the CAIDA Ark dataset to examine the country- and city-level coverage and consistency of popular public and commercial geolocation databases. We also create and provide a ground-truth dataset of 16,586 Router Interface IP addresses and their city-level locations, and use it to evaluate the databases' accuracy with a regional breakdown analysis. Our results show that the databases are not reliable for geolocating Routers and that there is room to improve their country- and city-level accuracy. Based on our results, we present a set of recommendations to researchers concerning the use of geolocation databases to geolocate Routers.
