Publication: Diseño y desarrollo de un sistema de detección de NATS para un monitor de tráfico residencial
Loading...
Identifiers
Publication date
2013-09
Defense date
2013-09-30
Authors
Advisors
Tutors
Journal Title
Journal ISSN
Volume Title
Publisher
Impact
Export
Abstract
Según el grupo de trabajo behave del IETF, el funcionamiento de NAT, aunque está definido
como un estándar varía de una implementación a otra. Esto es debido a que ciertos aspectos
del estándar no están definidos o determinados completamente, por lo que los diferentes
fabricantes y desarrolladores que han implementado soluciones NAT han definido
comportamientos diferentes.
Con el fin de crear un sistema de detección fiable del tipo de NAT existente en una red
concreta, se especificó una serie de pruebas utilizando el protocolo STUN para determinarlo
desde la propia red.
Para facilitar el despliegue en redes de usuarios de Internet residenciales se decide desarrollar
el sistema de detección en un sistema empotrado que permita un despliegue sencillo y rápido.
Dado que dicho sistema empotrado debe estar dotado de conexión a redes fiable, se elige el
router como sistema empotrado para llevar a cabo el despliegue.
Por diferentes motivos detallados en el proyecto, se considera que el firmware OpenWrt es el
adecuado para llevar a cabo esta tarea de detección del tipo de NAT y recopilación de dicha
información en un sistema centralizado.
Para facilitar la evaluación de la información recopilada, se ha considerado necesaria la
creación de un framework web.
This project aims to create a tool capable of identifying the type of NAT (Network Address Translation) used in the domestic network of any user, distinguishing between different implementations and network configurations used by each ISP (Internet Service Provider) and Internet user. NAT has been used as a temporal solution to solve the shortage problem of existing IP addresses in the IPv4 protocol, in which 32 bits addresses are used (which means 2^32 different addresses). NAT is about translating a private address space into a public address space and backwards, in a transparent way for both endpoints (IP Network Address Translator (NAT) Terminology and Considerations [RFC2663]). Once the use of NAT spread, the STUN (Session Traversal Utilities for NAT) protocol was created. STUN provides functionalities to other protocols in order to detect the connectivity between the two endpoints, as well as to keep associations made by the NAT (Session Traversal Utilities for NAT (STUN) [RFC5389]). Right now, the different types of NAT aren’t subjected to any standard, but each manufacturer develops its own implementation of NAT, which is multiple types of NAT exist. The behave group from the IETF created a recommendation about the different types of NAT which can be used depending on each specific case. However, it’s only a recommendation, not a standard. Thereby, lots of types of NAT have been created, apart from the ones detailed by the behave group. Finally, this project deals with creating a tool which is able to detect the different types of NAT recommended by the behave group, even though many more types exist.
This project aims to create a tool capable of identifying the type of NAT (Network Address Translation) used in the domestic network of any user, distinguishing between different implementations and network configurations used by each ISP (Internet Service Provider) and Internet user. NAT has been used as a temporal solution to solve the shortage problem of existing IP addresses in the IPv4 protocol, in which 32 bits addresses are used (which means 2^32 different addresses). NAT is about translating a private address space into a public address space and backwards, in a transparent way for both endpoints (IP Network Address Translator (NAT) Terminology and Considerations [RFC2663]). Once the use of NAT spread, the STUN (Session Traversal Utilities for NAT) protocol was created. STUN provides functionalities to other protocols in order to detect the connectivity between the two endpoints, as well as to keep associations made by the NAT (Session Traversal Utilities for NAT (STUN) [RFC5389]). Right now, the different types of NAT aren’t subjected to any standard, but each manufacturer develops its own implementation of NAT, which is multiple types of NAT exist. The behave group from the IETF created a recommendation about the different types of NAT which can be used depending on each specific case. However, it’s only a recommendation, not a standard. Thereby, lots of types of NAT have been created, apart from the ones detailed by the behave group. Finally, this project deals with creating a tool which is able to detect the different types of NAT recommended by the behave group, even though many more types exist.
Description
Keywords
Redes de comunicación, NAT (Network Address Translation), Protocolos de comunicación