{"id":1655,"date":"2014-07-02T16:02:04","date_gmt":"2014-07-02T20:02:04","guid":{"rendered":"https:\/\/infotechguy.net\/?p=1655"},"modified":"2022-08-26T09:48:22","modified_gmt":"2022-08-26T13:48:22","slug":"nat-traversal-ipsec","status":"publish","type":"post","link":"https:\/\/infotechguy.net\/?p=1655","title":{"rendered":"What is NAT-Traversal??"},"content":{"rendered":"

Hi All, been awhile since my last post, however I believe this to be a good one!. So…the question arose the other day regarding NAT-Traversal. What is that? Why do we have it? What does it do? Most network engineers have heard of NAT-traversal before when configuring their Firewalls and VPN Clients, etc. But, I wanted to take a minute to explain where NAT-Traversals (NAT-T) need came from and the reason we still use it.<\/p>\n

In order to understand NAT-Traversal, we need to understand two Networking concepts. First we need to understand “The Network Flow”. HOw do two hosts on a Network maintain a communication session. The second, is Network Address Translation. Yes NAT’ing, is a big part of IPv4 networks, they are so common place that you are probably using NAT’ing right now when reading this article.<\/p>\n

The Network Flow.<\/h2>\n

So in a typical end-to-end connectivity the network traffic flow is maintained by 4 main parameters.<\/p>\n

    \n
  1. Destination IP<\/strong><\/li>\n
  2. Destination Port<\/strong><\/li>\n
  3. Source IP<\/strong><\/li>\n
  4. Source Port<\/strong><\/li>\n<\/ol>\n

    These 4 parameters provide a seamless flow of packets back and forth to each end-to-end device within a communication. It is how packets carrying your data arrive at their destination and it is how a return response knows how to get back to the requesting device. The IP requirement is usually pretty straight forward, it’s like the address of a house. You have to know the TO<\/strong> and FROM <\/strong>fields when sending a mail letter. So where does this port information come into play?? So Port number is like a sub-address of where the mailbox is located on a house. Usually a home will only have one mailbox, but imagine the same scenario with an apartment building or housing complex..Many mailboxes at a single address. Now depending on where you live you may need to prepend or add a apartment number to the address. Translate this same concept to port numbers. If my address is 123 North St<\/strong> and I am sending to 789 South St.<\/strong> My courier knows how to drive to each destination, but it doesn’t know where to put the actual mail envelopes since it is an apartment building with hundreds of apartments. This is where the port number comes in. So if on my envelope I put 123 North St. Apt#100<\/strong> and I am sending to 789 South St. Apt#201. My mail will be delivered not only to the correct address but the correct mailbox.<\/p>\n

    I like using the apartment analogy, because it makes us think about Address and Ports being used together to deliver mail. An address and port combination is called a Socket <\/a>in the networking world.<\/p>\n

    Now in a typical request scenario, a client forms the TCP\/IP datagram. A Client’s machine fills in the destination IP and Destination Port based on the target and application type generating the request. For example, when you type http:\/\/ <\/strong>in your browser, the browser application knows to use port 80 as the Destination Port. The client then fills in it’s own IP address for the Source IP, and the OS chooses a Source Port at random. We call this random Source Port, the Ephemeral Port<\/a>.<\/p>\n

    A typical TCP\/IP communication header.<\/h5>\n

    Sent Packet:<\/span><\/p>\n

    \n\n\n\n\n
    Dst IP<\/td>\nDst Port<\/td>\nSrc IP<\/td>\nSrc Port<\/td>\n<\/tr>\n
    192.168.10.10<\/td>\n80<\/td>\n192.168.1.100<\/td>\n49152<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    Return Packet:<\/span><\/p>\n

    \n\n\n\n\n
    Dst IP<\/td>\nDst Port<\/td>\nSrc IP<\/td>\nSrc Port<\/td>\n<\/tr>\n
    192.168.1.100<\/td>\n49152<\/td>\n192.168.10.10<\/td>\n80<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    <\/p>\n

    A Brief NAT’ing Lesson<\/h3>\n

    How this works is a Network device in-between the source and destination networks, usually a Router or Firewall<\/strong>, performs Network Address Translation. When NAT’ing occurs the Network(Router or Firewall) device needs to maintain what has been translated, so it can be untranslated when it returns. The Network(Router or Firewall) device performing the NAT’ing creates it’s own local table of addresses it has translated. It maintains the identification of which packets have been translated by taking into account the random source port from above. Remember the<\/strong> Ephemeral Port<\/a>. This random source port is easy way for the Network device to keep track of open connections being translated.<\/p>\n

    NAT’ing Example #1. In this example I am showing a packet before it passes through a router performing NAT’ing, “untranslated”, and showing a packet after it passess through a router performing NAT’ing, “translated”. Translating Source IP from 192.168.1.100 to 2.2.2.2)
    \n<\/em>
    \nUntranslated Packet<\/span><\/strong><\/p>\n

    \n\n\n\n\n
    Dst IP<\/td>\nDst Port<\/td>\nSrc IP<\/td>\nSrc Port<\/td>\n<\/tr>\n
    8.8.8.8<\/td>\n80<\/td>\n192.168.1.100<\/td>\n49152<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    Translated Packet<\/span><\/strong><\/p>\n

    \n\n\n\n\n
    Dst IP<\/td>\nDst Port<\/td>\nSrc IP<\/td>\nSrc Port<\/td>\n<\/tr>\n
    8.8.8.8<\/td>\n80<\/td>\n2.2.2.2<\/td>\n49152<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    NAT’ing Example #2. In this example I am showing how a router performing the NAT’ing maintains a NAT table of packets it has translated and untranslated. The example below also shows different Source IPs connecting to the same Destination IP. These Source IPs will need to be translated to a different address, 2.2.2.2.<\/em><\/p>\n

    Local NAT Table<\/span><\/strong><\/p>\n

    \n\n\n\n\n\n\n\n
    Original Source IP<\/td>\nTranslated Source IP<\/td>\nSource Port<\/td>\nDestination IP<\/td>\nDestination Port<\/td>\n<\/tr>\n
    192.168.1.100<\/td>\n2.2.2.2<\/td>\n49152<\/td>\n8.8.8.8<\/td>\n80<\/td>\n<\/tr>\n
    192.168.1.101<\/td>\n2.2.2.2<\/td>\n49943<\/td>\n8.8.8.8<\/td>\n80<\/td>\n<\/tr>\n
    192.168.1.102<\/td>\n2.2.2.2<\/td>\n49563<\/td>\n8.8.8.8<\/td>\n80<\/td>\n<\/tr>\n
    192.168.1.104<\/td>\n2.2.2.2<\/td>\n49234<\/td>\n8.8.8.8<\/td>\n80<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    Notice: The Soure Port is unique to each original IP. Both the Source IP, Source Port, and Destination IP and Destination Port are used together to maintain the Translation table, allowing the correct packets to be untranslated on their return. Sounds similar to “The Network Flow” from above right?<\/em><\/p>\n

    The problem.<\/strong><\/h3>\n

    In world of IPSEC, we do not<\/span> use TCP or UDP protocols, in fact we use a completely different Network Layer Protocol<\/a>(ICMP,ESP, OSPF, RIP,EIGRP,etc) \u00a0instead of a Transport Layer Protocol (TCP\/UDP). \u00a0In fact, the protocol is used to protect and hide<\/span> the original IP information, which is the whole point of IPSec<\/strong>. IPSec<\/strong> uses an encapsulating protocal called Encapsulating Security Payload(ESP)<\/strong> to take the original IP information and securely encasulate it via encryption. This prevents wire-tapping or network sniffers from discovering the original IP information while it is in transit. This ESP protocol includes only a Source IP, Destination IP, and a ESP Header and Footer to maintain session state information. No TCP\/UDP port information can be used to create a NAT table binding!!!
    \n    \"\"<\/a>
    \n<\/strong><\/p>\n

    Notice: There is no TCP\/UDP Port information!! It has been replaced by the ESP protocol.<\/em><\/p>\n

    The issue arises, when a Client attempts to initiate an ESP connection behind a network(Router or Firewall) device that performs Network Address Translation (NAT). NAT’ing involves the manipulation of the IP Header and TCP\/UDP port information to maintain sessions states as stated in the above section. The Network(Router or Firewall) device is unable to maintain a unique translation state with these packets and therefor a IPSec tunnel cannot be formed.<\/p>\n

    The Solution:<\/h3>\n

    NAT-Traversal to the rescue!!<\/strong> NAT-Traversal encapsulates the datagram yet again with a UDP Packet. By doing so, the Packet now includes a Destination Port and Source Port! We can now successfully perform NAT’ing and maintain the connection state in the NAT table.<\/p>\n

    NAT-T Dst\/Src port added to original ESP datagram:<\/strong>
    \n    \"\"<\/a><\/p>\n

    NAT-T Encapsulation Datagram:
    \n    \"\"<\/a>
    \n<\/strong><\/p>\n

    VPN Passthrough<\/h6>\n

    I wanted to mention this feature, because it is very common among home routers utilizing Network address translation. VPN Passthrough is a Consumer router specific technology, used by Routers that cannot support VPN technologies natively. Meaning the router does not perform VPN, the client’s computer does. Such as a VPN Client, etc. The original issue of NAT’ing a ESP packet is still present, however the router does not support NAT-Traversal. If VPN Passthrough is enabled on the consumer router, the router inspects VPN traffic originating from it’s internal network devices and maintains a table similar to the NAT-T table, but via some other propritary means.<\/p>\n

    The Requirement.<\/strong><\/h3>\n

    Both ends need to support NAT-Traversal, since a UDP port is used instead of the ESP Layer 3 protocol. NAT detection also takes place at the start of a IPsec communication, called NAT-discovery. If during NAT discovery, NAT-Traversal is not detected, the IPSec will not be brough up over NAT-Traversal and will use straight ESP.<\/p>\n

    Configuring NAT-Travesal on a Cisco ASA 5500<\/h6>\n
    ASA# config terminal \nASA(config)# crypto isakmp nat-traversal 20 \nexit<\/pre>\n
    Configuring NAT-Travesal on Openswan<\/h6>\n
    openswan# vi \/etc\/ipsec.conf \nconfig setup \n   nat_traversal = yes<\/pre>\n
    <\/h6>\n
    Notice: This will enable NAT-Traversal globally on the ASA, but remember both sides have to agree and support NAT-Traversal for it to actually work and be used.<\/em><\/p>\n
     <\/p>\n","protected":false},"excerpt":{"rendered":"
    Hi All, been awhile since my last post, however I believe this to be a good one!. So…the question arose the other day regarding NAT-Traversal. What is that? Why do we have it? What does...<\/p>\n","protected":false},"author":2,"featured_media":4277,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[55,112],"class_list":["post-1655","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-network","tag-cisco","tag-security-2"],"_links":{"self":[{"href":"https:\/\/infotechguy.net\/index.php?rest_route=\/wp\/v2\/posts\/1655","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/infotechguy.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/infotechguy.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/infotechguy.net\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/infotechguy.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1655"}],"version-history":[{"count":1,"href":"https:\/\/infotechguy.net\/index.php?rest_route=\/wp\/v2\/posts\/1655\/revisions"}],"predecessor-version":[{"id":4154,"href":"https:\/\/infotechguy.net\/index.php?rest_route=\/wp\/v2\/posts\/1655\/revisions\/4154"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/infotechguy.net\/index.php?rest_route=\/wp\/v2\/media\/4277"}],"wp:attachment":[{"href":"https:\/\/infotechguy.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1655"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/infotechguy.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1655"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/infotechguy.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1655"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}