CIS225_2.3_NAT_PAT_Port_Forwarding_Corey_Adams
docx
keyboard_arrow_up
School
ECPI University, Greensboro *
*We aren’t endorsed by this school
Course
225
Subject
Information Systems
Date
Nov 24, 2024
Type
docx
Pages
2
Uploaded by corada5995
2.3 In-Class Activity: NAT / PAT / Port Forwarding
How does NAT / PAT extend the life of IPv4?
IPv4, the current version of IP, supports more than 4 billion addresses. Considering the Internet's
phenomenal growth, however, that represents a relatively meagre allotment. To extend the reach of the IPv4 address space, companies have turned to using private IPv4 addresses through a public-to-private address translation technique known as network address translation (NAT).
But this method has a few limitations. So, a new technique called Realm-Specific Internet Protocol (RSIP) promises to pick up where NAT leaves off.
How does NAT / PAT make network management easier?
Due in large part to alleged NAT support on consumer devices, many people are confused about what NAT really is. Network Address Translation is used for many purposes, including but certainly not limited to, saving IP addresses. NAT is a feature of a router that will translate IP addresses. When a packet comes in, it will be rewritten to forward it to a host that is not the IP destination. A router will keep track of this translation, and when the host sends a reply, it will translate back the other way.
Briefly describe a couple of possible scenarios when two companies merge, and both
are using IPv4 with NAT/ PAT and their inside IP range is 10.0.0.0/8. Describe some
possible complications that may arise with each scenario and how these might be
overcome.
A complete list of special-use IPv4 networks may be found in RFC 3330. There are private IPv4 addresses, such as 1.0.0.0/8 and 2.0.0.0/8, that have since been allocated to the dwindling IPv4 pool. Use of these addresses are problematic and not recommended. Also, avoid using
169.254.0.0/16, which according to RFC 3927 is reserved for "Link-Local" auto configuration. It
should not be assigned by DHCP or set manually, and routers will not allow packets from that subnet to traverse outside a specific broadcast domain. There is sufficient address space set aside by RFC 1918, so there is no need to deviate from the list shown in Table RFC 1918 Private IP Address Space. Improper addressing will result in network failure and should be corrected.
How does NAT / PAT running on IPv4 complicate the migration to IPv6?
One of the main factors is that changing the Internet Protocol (IP) cannot be done one connection
at a time. A sending system that creates an IPv6 packet needs all the routers, firewalls, and load balancers that are in its path to understand and be able to process the IPv6 packet. Plus, the receiving system needs to able to understand the IP packet for everything to work correctly. We cannot just upgrade a server and a client application; it also requires upgrading everything in between.
In IP networking, a private network is a computer network that uses private IP address space. Both the IPv4 and the IPv6 specifications define private IP address ranges. These addresses are commonly used for local area networks (LANs) in residential, office, and enterprise environments. Private network addresses are not allocated to any specific organization. Anyone may use these addresses without approval from regional or local Internet registries. Private IP address spaces were originally defined to assist in delaying IPv4 address exhaustion. IP packets originating from or addressed to a private IP address cannot be routed through the public Internet.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help