RSC Part II: Network Layer 3. IP addressing Redes y Servicios de Comunicaciones Universidad Carlos III de Madrid These slides are, mainly, part of the companion slides to the book “Computer Networking: A Top Down Approach” generously made available by their authors (see copyright below). The slides have been adapted, where required, to the teaching needs of the subject above. All material copyright J.F Kurose and K.W. Ross, All Rights Reserved Computer Networking: A Top Down Approach 5 th edition. Jim Kurose, Keith Ross Addison-Wesley, April 2009.

Network LayerII-2 RSC Part II: Network Layer r II. 1 Basic Network layer concepts r II.2 Introduction to IP m Datagram format m ICMP r II.3 IP addressing r II.4 IP in operation m ARP r II.5 Network routing m Link state m Distance Vector m Hierarchical routing r II.6 Routing in the Internet m RIP m OSPF m BGP m Broadcast and multicast

Network LayerII-3 IP Addressing: introduction =

Network LayerII-4 Hierarchical addressing: route aggregation “Send me anything with addresses beginning /20” / / /23 Fly-By-Night-ISP Organization 0 Organization 7 Internet Organization 1 ISPs-R-Us “Send me anything with addresses beginning /16” /23 Organization Hierarchical addressing allows efficient advertisement of routing information: …

Network LayerII-5 Hierarchical addressing: more specific routes ISPs-R-Us has a more specific route to Organization 1 “Send me anything with addresses beginning /20” / / /23 Fly-By-Night-ISP Organization 0 Organization 7 Internet Organization 1 ISPs-R-Us “Send me anything with addresses beginning /16 or /23” /23 Organization

Network LayerII-6 IP addressing: CIDR CIDR: Classless InterDomain Routing m network portion of address of arbitrary length m address format: a.b.c.d/x, where x is number of bits in the network portion of the address Network part (network prefix) host part /23

Network LayerII-7 IP addresses: how to get one? Q: How does organization get prefix part of IP addr? A: gets allocated portion of its provider ISP’s address space ISP's block /20 Organization /23 Organization /23 Organization /23... ….. …. …. Organization /23

Subnetting r A little bit more complex, Variable length subnet mask: / / / XXXXXXXXXX network subnet host Subnet mask: or /25 -> 126 interfaces 2 bits 8 bits 22 bits / / / / XXXXXXXX network subnet host 3 bits 7 bits 22 bits Subnet mask: or /24 -> 254 interfaces XXXXXXXXXX network subnet host 2 bits 8 bits 22 bits Subnet mask: or /24: /24, /24 y /24

Network LayerII-9 Forwarding Network Mask Gateway Interface Internet

Subnetting Network LayerII-10 r Special values: m All 0’s in host part Subnet m All 1’s in host part Broadcast address (2 h -2) possible interfaces in a subnet m Default m /8, /32 Loopback m /4 Multicast XXXXXXXXXXXXXXXX XXXXX XXX network subnet host s bits h bits XXXXXXXXXXXXXXXX XXXXX XXX network subnet host s bits h bits

Network LayerII-11 Addresses and names r For humans, it is convenient to manage names instead of numbers m We can associate a name to an address: Eg it002.lab.it.uc3m.es m A distributed application: Domain Name System (DNS), resolves names into addresses DNS names are hierarchical to distribute their management m Nodes connected to the network need the address of a DNS server to resolve names Manual configuration or DHCP r This is the idea, DNS is a complex application that will be studied in future courses

Network LayerII-12 IP addresses: how to get one? Q: How does network get subnet part of IP addr? A: gets allocated portion of its provider ISP’s address space ISP's block /20 Organization /23 Organization /23 Organization /23... ….. …. …. Organization /23

Network LayerII-13 IP addressing: the last word... Q: How does an ISP get block of addresses? A: ICANN: Internet Corporation for Assigned Names and Numbers m Allocates and registers addresses m manages DNS m assigns domain names, resolves disputes r The Internet Assigned Numbers Authority (IANA), operated by the ICANN (Internet Corporation for Assigned Names and Numbers) m Manages IP address allocation (and parameters of Internet protocols) m Delegates address assignment to RIRs (Regional Internet Registry): American Registry for Internet Numbers (ARIN) for North America and parts of the Caribbean RIPE Network Coordination Centre (RIPE NCC) for Europe, the Middle East and Central Asia Asia-Pacific Network Information Centre (APNIC) for Asia and the Pacific region Latin American and Caribbean Internet Addresses Registry (LACNIC) for Latin America and parts of the Caribbean region African Network Information Centre (AfriNIC) for Africa m ISPs get IP address blocks from RIRs or Local Internet Registry (LIR)

Network LayerII-14 IP addresses: how to get one? Q: How does a host get IP address? r hard-coded by system admin in a file m Windows: control-panel->network->configuration- >tcp/ip->properties m UNIX: /etc/rc.config r DHCP: Dynamic Host Configuration Protocol: dynamically get address from as server m “plug-and-play”

Network LayerII-15 DHCP: Dynamic Host Configuration Protocol Goal: allow host to dynamically obtain its IP address from network server when it joins network Can renew its lease on address in use Allows reuse of addresses (only hold address while connected an “on”) Support for mobile users who want to join network (more shortly) DHCP overview: m host broadcasts “DHCP discover” msg m DHCP server responds with “DHCP offer” msg m host requests IP address: “DHCP request” msg m DHCP server sends address: “DHCP ack” msg

Network LayerII-16 DHCP client-server scenario A B E DHCP server arriving DHCP client needs address in this network

Network LayerII-17 DHCP client-server scenario DHCP server: arriving client time DHCP discover src : , 68 dest.: ,67 yiaddr: transaction ID: 654 DHCP offer src: , 67 dest: , 68 yiaddrr: transaction ID: 654 Lifetime: 3600 secs DHCP request src: , 68 dest:: , 67 yiaddrr: transaction ID: 655 Lifetime: 3600 secs DHCP ACK src: , 67 dest: , 68 yiaddrr: transaction ID: 655 Lifetime: 3600 secs

Network LayerII-18 NAT: Network Address Translation local network (e.g., home network) /24 rest of Internet Datagrams with source or destination in this network have /24 address for source, destination (as usual) All datagrams leaving local network have same single source NAT IP address: , different source port numbers

Network LayerII-19 NAT: Network Address Translation r Motivation: local network uses just one IP address as far as outside world is concerned: m range of addresses not needed from ISP: just one IP address for all devices m can change addresses of devices in local network without notifying outside world m can change ISP without changing addresses of devices in local network m devices inside local net not explicitly addressable, visible by outside world (a security plus). r Private address space: m (10/8 prefix) m (172.16/12 prefix) m ( /16 prefix)

Network LayerII-20 NAT: Network Address Translation Implementation: NAT router must: m outgoing datagrams: replace (source IP address, port #) of every outgoing datagram to (NAT IP address, new port #)... remote clients/servers will respond using (NAT IP address, new port #) as destination addr. m remember (in NAT translation table) every (source IP address, port #) to (NAT IP address, new port #) translation pair m incoming datagrams: replace (NAT IP address, new port #) in dest fields of every incoming datagram with corresponding (source IP address, port #) stored in NAT table

Network LayerII-21 NAT: Network Address Translation S: , 3345 D: , : host sends datagram to , 80 NAT translation table WAN side addr LAN side addr , , 3345 …… S: , 80 D: , S: , 5001 D: , : NAT router changes datagram source addr from , 3345 to , 5001, updates table S: , 80 D: , : Reply arrives dest. address: , : NAT router changes datagram dest addr from , 5001 to , 3345

Network LayerII-22 NAT: Network Address Translation r 16-bit port-number field: m 60,000 simultaneous connections with a single LAN-side address! r NAT is controversial: m routers should only process up to layer 3 m violates end-to-end argument NAT possibility must be taken into account by app designers, eg, P2P applications m address shortage should instead be solved by IPv6

Network LayerII-23 NAT traversal problem r client wants to connect to server with address m server address local to LAN (client can’t use it as destination addr) m only one externally visible NATted address: r solution 1: statically configure NAT to forward incoming connection requests at given port to server m e.g., ( , port 2500) always forwarded to port NAT router Client ?

Network LayerII-24 NAT traversal problem r solution 2: Universal Plug and Play (UPnP) Internet Gateway Device (IGD) Protocol. Allows NATted host to:  learn public IP address ( )  add/remove port mappings (with lease times) i.e., automate static NAT port map configuration NAT router IGD

Network LayerII-25 NAT traversal problem r solution 3: relaying (used in Skype) m NATed client establishes connection to relay m External client connects to relay m relay bridges packets between to connections Client NAT router 1. connection to relay initiated by NATted host 2. connection to relay initiated by client 3. relaying established