Nytro Posted February 19, 2013 Report Posted February 19, 2013 Autonomous NAT TraversalAndreas Muller Nathan Evans Christian GrothoffNetwork Architectures and ServicesTechnische Universit¨at M¨unchenEmail: fmueller,evans,grothoffg@net.in.tum.deSamy KamkarEmail: samy@samy.plAbstract—Traditional NAT traversal methods require the helpof a third party for signalling. This paper investigates a newautonomous method for establishing connections to peers behindNAT. The proposed method for autonomous NAT traversaluses fake ICMP messages to initially contact the NATed peer.This paper presents how the method is supposed to work intheory, discusses some possible variations, introduces variousconcrete implementations of the proposed approach and evaluatesempirical results of a measurement study designed to evaluatethe efficacy of the idea in practice.I. INTRODUCTIONA large fraction of the hosts in a typical peer-to-peer networkare in home networks. Most home networks use networkaddress translation (NAT) [1] to facilitate multiple computerssharing a single global public IP address, to enhance securityor simply because the provider’s hardware often defaults tothis configuration. Recent studies have reported that up to 70%of users access P2P networks from behind a NAT system [2].This creates a well-known problem for peer-to-peer networkssince it is not trivial to initiate a connection to a peer behindNAT. For this paper, we will use the term server to refer to apeer behind NAT and the term client for any other peer tryingto initiate a connection to the server.Unless configured otherwise (protocols such as the InternetGateway Device Protocol [3] are counted as configurationin this context), almost all NAT implementations refuse toforward inbound traffic that does not correspond to a recentmatching outbound request. This is not primarily an implementationissue: if there are multiple hosts in the private network,the NAT is likely unable to tell which host is the intended recipient.Configuration of the NAT is not always an alternative;problems range from end-user convenience and capabilities ofthe specific NAT implementation to administrative policies thatmay prohibit changes to the NAT configuration (for example,due to security concerns).Since NAT systems prohibit inbound requests that do notmatch a previous outbound request, all existing NAT traversaltechniques (aside from those changing the configuration of theNAT system) that we are aware of require some amount ofactive facilitation by a third party [4], [5]. The basic approachin most of these cases is that the server in the private networkbehind the NAT is notified by the third party that the clientwould like to establish a connection. The server then initiatesthe connection to the client. This requires that the servermaintains a connection to a third party, that the client is ableto locate the responsible third party and that the third partyacts according to a specific protocol.The goal of this paper is autonomous NAT traversal,meaning NAT traversal without a third party. Using thirdparties increases the complexity of the software and potentiallyintroduces new vulnerabilities. For example, if anonymizingpeer-to-peer networks (such as GNUnet [6] or Tor [7]) usedthird parties for NAT traversal, an attacker may be able tomonitor connections or even traffic volumes of peers behindNATs which in turn might enable deanonymization attacks [8],[9]. Another problem is that the decrease in available globallyroutable IPv4 addresses [10] will in the near future sharplyreduce the fraction of hosts that would be able to facilitateNAT traversal.Download:http://samy.pl/pwnat/pwnat.pdf Quote
begood Posted February 19, 2013 Report Posted February 19, 2013 (edited) fucking awesome !! e brilianta metoda ! Edited February 19, 2013 by begood Quote