Scribd Logo
Upload

Welcome to Scribd!

  • 11 views

    CN Lab5

    Uploaded by

    rinoni8941

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    CN Lab5

    Uploaded by

    rinoni8941
    11 views6 pages

    Original Title

    CN lab5

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    11 views6 pages

    CN Lab5

    Uploaded by

    rinoni8941

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 6

    31 Understanding Public IP Address & NAT

    (Network Address Translation)

    31.1 Theory

    31.1.1 Public Address

    A public IP address is assigned to every computer that connects to the Internet where each IP is
    unique. Hence there cannot exist two computers with the same public IP address all over the
    Internet. This addressing scheme makes it possible for the computers to “find each other” online and
    exchange information. User has no control over the IP address (public) that is assigned to the
    computer. The public IP address is assigned to the computer by the Internet Service Provider as
    soon as the computer is connected to the Internet gateway.

    31.1.2 Private Address

    An IP address is considered private if the IP number falls within one of the IP address ranges
    reserved for private networks such as a Local Area Network (LAN). The Internet Assigned Numbers
    Authority (IANA) has reserved the following three blocks of the IP address space for private networks
    (local networks):

    Class Starting IP address Ending IP address No. of hosts

    A 10.0.0.0 10.255.255.255 16,777,216


    B 172.16.0.0 172.31.255.255 1,048,576
    C 192.168.0.0 192.168.255.255 65,536
    Table 31-1: Private IP address table
    Private IP addresses are used for numbering the computers in a private network including home,
    school and business LANs in airports and hotels which makes it possible for the computers in the
    network to communicate with each other. For example, if a network A consists of 30 computers each
    of them can be given an IP starting from 192.168.0.1 to 192.168.0.30.

    Devices with private IP addresses cannot connect directly to the Internet. Likewise, computers
    outside the local network cannot connect directly to a device with a private IP. It is possible to
    interconnect two private networks with the help of a router or a similar device that supports Network
    Address Translation.

    If the private network is connected to the Internet (through an Internet connection via ISP) then each
    computer will have a private IP as well as a public IP. Private IP is used for communication within
    the network whereas the public IP is used for communication over the Internet.

    Ver 13.0 Page 264 of 288


    31.1.3 Network address translation (NAT)

    A NAT (Network Address Translation or Network Address Translator) is the virtualization of Internet
    Protocol (IP) addresses. NAT helps to improve security and decrease the number of IP addresses
    an organization needs.

    A device that is configured with NAT will have at least one interface to the inside network and one to
    the outside network. In a typical environment, NAT is configured at the exit device between a stub
    domain (inside network) and the backbone. When a packet leaves the domain, NAT translates the
    locally significant source address into a globally unique address. When a packet enters the domain,
    NAT translates the globally unique destination address into a local address. If more than one exit
    point exists, each NAT must have the same translation table. NAT can be configured to advertise to
    the outside world only one address for the entire network. This ability provides additional security by
    effectively hiding the entire internal network behind that one address. If NAT cannot allocate an
    address because it has run out of addresses, it drops the packet and sends an Internet Control
    Message Protocol (ICMP) host unreachable packet to the destination.

    Figure 31-1: NAT implementation


    NAT is secure since it hides network from the Internet. All communications from internal private
    network are handled by the NAT device, which will ensure all the appropriate translations are
    performed and provide a flawless connection between internal devices and the Internet.

    In the above figure, a simple network of 4 hosts and one router that connects this network to the
    Internet. All hosts in the network have a private Class C IP Address, including the router's private
    interface (192.168.0.1), while the public interface that's connected to the Internet has a real IP
    Address (203.31.220.134). This is the IP address the Internet sees as all internal IP addresses are
    hidden.

    Ver 13.0 Page 265 of 288


    31.2 Network Setup
    Open NetSim and click Examples > Experiments > Understanding-Public-IP-Address-and-NAT-
    (Network-Address-Translation) > Sample-1 as shown below Figure 31-2.

    Figure 31-2: Experiments List


    NetSim UI displays the configuration file corresponding to this experiment as shown below Figure
    31-3.

    Figure 31-3: Application flow between different LAN

    31.3 Procedure
    The following set of procedures were done to generate this sample:

    Ver 13.0 Page 266 of 288


    Step 1: A network scenario is designed in NetSim GUI comprising of 6 Wired Nodes, 2 L2 Switches,
    and 4 Routers in the “Internetworks” Network Library.

    Step 2: In the INTERFACE (ETHERNET) > NETWORK LAYER of the Wired Nodes, the IP Address
    and the Subnet Mask are set as per the table given below Table 31-2.

    Wired Node IP address Subnet mask

    7 10.0.0.2 255.0.0.0
    8 10.0.0.3 255.0.0.0
    9 10.0.0.4 255.0.0.0
    10 172.16.0.2 255.255.0.0
    11 172.16.0.3 255.255.0.0
    12 172.16.0.4 255.255.0.0

    Table 31-2: IP Address and the Subnet mask for Wired nodes
    Step 3: The IP Address and the Subnet Mask in Routers are set as per the table given below Table
    31-3.

    Router Interface IP address Subnet mask

    Interface_2(WAN) 11.1.1.1 255.0.0.0


    Router 1
    Interface_1(Ethernet) 10.0.0.1 255.0.0.0
    Interface_1(WAN) 11.1.1.2 255.0.0.0
    Router 2
    Interface_2(WAN) 12.1.1.1 255.0.0.0
    Router 3 Interface_1(WAN) 12.1.1.2 255.0.0.0
    Interface_2(WAN) 13.1.1.2 255.0.0.0
    Router 4 Interface_1(WAN) 13.1.1.1 255.0.0.0
    Interface_2(Ethernet) 172.16.0.1 255.255.0.0

    Table 31-3: IP Address and the Subnet Mask for Routers


    Step 4: Right click on the Application Flow App1 CBR and select Properties or click on the
    Application icon present in the top ribbon/toolbar.

    A CBR Application is generated from Wired Node 7 i.e. Source to Wired Node 10 i.e. Destination
    with Packet Size remaining 1460Bytes and Inter Arrival Time remaining 20000µs.

    Additionally, the “Start Time(s)” parameter is set to 50(Figure 31-4), while configuring the application.
    This time is usually set to be greater than the time taken for OSPF Convergence (i.e. Exchange of
    OSPF information between all the routers), and it increases as the size of the network increases.

    Ver 13.0 Page 267 of 288


    Figure 31-4: Application Properties Window
    Step 5: Packet Trace is enabled, and hence we are able to track the route which the packets have
    chosen to reach the destination.

    Step 6: Enable the plots and run the Simulation for 100 Seconds.

    31.4 Output
    After simulation open Packet Trace and filter Packet ID to 1.

    Figure 31-5: Packet Trace


    SOURCE_IP – source node IP (Node)

    DESTINATION_IP – gateway IP/ destination IP (Router/ Node)

    GATEWAY_IP – IP of the device which is transmitting a packet (Router/ Node)

    NEXT_HOP_IP – IP of the next hop (Router/ Node)

    Ver 13.0 Page 268 of 288


    Source node 7 (10.0.0.2) wouldn’t know how to route to the destination and hence its default gateway
    is Router 1 with interface IP (10.0.0.1). So, the first line in the above screenshot specifies packet
    flow from Source Node 7 to L2 Switch 6 with SOURCE_IP (10.0.0.2), DESTINATION_IP (10.0.0.1),
    GATEWAY_IP (10.0.0.2) and NEXT_HOP_IP (10.0.0.1). Since Switch is Layer2 device there is no
    change in the IPs in second line. Third line specifies the packet flow from Router 1 to Router 2 with
    SOURCE_IP (10.0.0.2), DESTINATION_IP (13.1.1.1- IP of the router connected to destination.
    Since OSPF is running, the router is looks up the route to its destination from routing table),
    GATEWAY_IP (11.1.1.1) and NEXT_HOP_IP (11.1.1.2) and so on.

    Ver 13.0 Page 269 of 288

    You might also like