DOCSLIB.ORG

Host Auto Configuration (Bootp, Dhcp)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Announcements I. HW5 online today, due in 1 week! HOST AUTO CONFIGURATION (BOOTP, DHCP) Internet Protocols CSC / ECE 573 Fall, 2005 N. C. State University copyright 2005 Douglas S. Reeves 2 Today’s Lecture I. Auto configuration II. BOOTP III. DHCP AUTO CONFIGURATION copyright 2005 Douglas S. Reeves 3 Host Autoconfiguration Host Autoconfiguration (cont’d) • What are the networking parameters needed to • Choices of configuration configure a host? – static (in configuration file on the local disk) • Essential – dynamic (from a server) – Own IP address • How do you ask a server to send configuration – subnet mask information if you don’t have an IP address? – gateway (default router) IP address – DNS server IP address • Many others would be useful, as well copyright 2005 Douglas S. Reeves 5 copyright 2005 Douglas S. Reeves 6 1 Protocol Choices Minimal: Reverse ARP (RARP) – requests IP address corresponding to MAC address – can only provide the client’s IP address Better: BOOTP BOOTP – provides many other configuration parameter values Best: DHCP – provides limited lifetimes on configuration information copyright 2005 Douglas S. Reeves 7 BOOTstraP Protocol (RFCs 951,1542) BOOTP Messages • Single message exchange from server to client • Client (host) uses the limited broadcast IP – provides many items needed at startup, in addition to address (255.255.255.255) to broadcast the the IP address BOOTP Request on the local net – source IP address = 0.0.0.0 (used only during bootstrapping) S2 #3 Memory Image H1 H2 S1 Request #1 BOOTP Request – multi-homed hosts issue one BOOTP Request for each interface #2 BOOTP Reply #4 Memory Image • BOOTP server responds, may use the limited broadcast address as destination of the BOOTP • BOOTP can tell clients where to get a “memory Reply image” (startup program) copyright 2005 Douglas S. Reeves 9 copyright 2005 Douglas S. Reeves 10 BOOTP Reliability BOOTP Message Format • BOOTP runs over UDP • Length = 236 bytes + Options – client is responsible for ensuring reliable Field # Interpretation communication Bytes Operation Type 1 Request or Reply • if no Reply after sufficient time, timeout and Hardware Type 1 e.g., Ethernet retransmit Request Length of physical address 1 6 for Ethernet – wait “random” delay before retransmission (between 0 and 4 s) # of Hops 1 Initialized to 0, relays increment – double timeout value each time (exponential backoff) Transaction ID 4 For matching Reply with Request Seconds (since booting 2 For prioritizing / forwarding Requests started) Flags 2 To indicate response should be broadcast copyright 2005 Douglas S. Reeves 11 copyright 2005 Douglas S. Reeves 12 2 BOOTP Message Format (cont’d) Address Fields Field # Interpretation Bytes • Client Request Client IP Address 4 0 if client doesn’t know – client fills in as many fields as known, zeroes otherwise Your IP Address 4 IP address to use (returned by – Server IP Address? server) Server IP Address 4 If client wants specific server to – Server Host Name? respond – Client IP Address? Relay’s IP Address 4 (Discussed later) Client Hardware Address 16 So server can unicast response to • Server Reply client Server Hostname 64 If client wants specific server to – if server specified by client, only that server responds respond 236 + options – fills in whatever fields were set to zeroes by client Boot File Name 128 Name of file containing memory image (in Request, type of OS desired) Options variable (Discussed later) copyright 2005 Douglas S. Reeves 14 BOOTP Options Field BOOTP Relays • Encoding of each option: TLV format • BOOTP Relay Agents permit a machine to – T = type or tag (1 byte) contact a BOOTP server on a non-local network – L = length (1 byte) • If a server decides to relay a Request… – V = value of option (N bytes) – it puts its own IP interface address in the Relay IP • Examples of options Address field – and forwards to the BOOTP server – subnet mask – clients ignore the field in a – client host name Relay IP Address Reply – memory image size – time of day – gateway IP addresses – DNS server IP addresses copyright 2005 Douglas S. Reeves 15 copyright 2005 Douglas S. Reeves 16 BOOTP Relays (cont’d) • Destination server sends Reply message to the relay agent (server) – all Replies received by a relay agent are intended for clients on its directly-connected network DHCP • A Relay Agent examines the Relay IP address, Your IP Address, and Client Hardware Address to deliver the Reply message to the client copyright 2005 Douglas S. Reeves 17 3 Dynamic Host Configuration Protocol Dynamic Configuration (RFCs 2131, 2132) • RARP and BOOTP are designed for a relatively • Extends BOOTP to handle dynamic address static environment assignment – “leases” an address for a limited time (from 1 sec to • Problems forever) – need to assign one machine different IP addresses at – backwards-compatible with BOOTP clients, message different times format is the same – need to reuse pool of IP addresses (clients only use addresses temporarily) • Solution: dynamic address assignment mechanism copyright 2005 Douglas S. Reeves 19 copyright 2005 Douglas S. Reeves 20 DHCP (cont’d) DHCP Client State Diagram • DHCP server DHCPOFFER / - R INIT VE CO – is given a set of addresses to manage IS PD D HC HC - / D P - N K A / C C – leases addresses to clients e K A s / s - N e a r P SELECT i e l C p r H – informs client of lease period (during which it will not x D o e T Lease reaches 87.5% / S lease same address to another client) r E of expiration time / e U f f Q REBIND DHCPREQUEST o E RENEW t R c P e C - • At end of the lease period, the client must either l / H e CK s D A CP - H D / renew the lease, or stop using the address K REQUEST C A 50% P es / C ach me H i DH re n t CP D ase tio pa AC Le ira ST ra K (i xp UE m nc f e Q / ete lu o RE e rs de CP s E ) / s DH a S - le A l E e L c E BOUND n R a P C C H D copyright 2005 Douglas S. Reeves 21 copyright 2005 Douglas S. Reeves 22 DHCP Client State Diagram DHCP Messages DHCPOFFER / - • Same format at BOOTP messages R INIT VE CO IS PD D HC HC • Client should set to 1 if it - / D P Broadcast Flag - N K A / C C e K A s / s - N e does not have a valid IP address already a r P SELECT i e l C p r H x D o e T Lease reaches 87.5% / S r message includes configuration E of expiration time, or • DHCPOFFER e U f f Q REBIND REBIND time / o E RENEW parameters, such a t R DHCPREQUEST Your IP Address c P e C - l / H e CK s D A CP - H D / • Same as BOOTP, plus some additional K Options REQUEST C A 50% P es ones C , ach me H i DH re n t e / CP D se tio im pa AC Lea ira L t ra K (i exp WA me nc f E T / te lu o EN ES e rs de r R U s E ) / s o EQ a S - PR le A HC l E D e L c E BOUND n R a P C C H D copyright 2005 Douglas S. Reeves 23 copyright 2005 Douglas S. Reeves 24 4 DHCPINFORM Message Some Example Options Fields • If client already has IP address but requests other • IP information configuration parameters from the server – subnet mask – host name and domain name (for client) • Server unicasts to client a DHCPACK with – IP forwarding option parameters, but – default IP TTL – Does not allocate new IP address – interface MTU, maximum datagram reassembly size – broadcast address to use – Does not provide lease times – static routes option copyright 2005 Douglas S. Reeves 25 copyright 2005 Douglas S. Reeves 26 Example Options Fields (cont’d) Example DHCP Request (Selected Fields) Ethernet II, Src: 152.14.62.39 (00:11:43:41:28:ed), Dst: Broadcast • Bootstrapping information (ff:ff:ff:ff:ff:ff) – local time Internet Protocol, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 – boot file size (255.255.255.255) – image server, root path User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67) – relay agents to use • Other Bootstrap Protocol – ARP cache timeout intervals Message type: Boot Request (1) Hardware type: Ethernet – application parameters Hardware address length: 6 • Lots of “vendor-specific” parameters Transaction ID: 0xc9ea1fd2 Bootp flags: 0x0000 (Unicast) 0... .... .... .... = Broadcast flag: Unicast Client IP address: 0.0.0.0 (0.0.0.0) Your (client) IP address: 0.0.0.0 (0.0.0.0) Next server IP address: 0.0.0.0 (0.0.0.0) Relay agent IP address: 0.0.0.0 (0.0.0.0) copyright 2005 Douglas S. Reeves 27 Client MAC address: 152.14co.p6yri2gh.t 320905 D(o0ug0la:s1 S.1 R:e4eve3s:41:28:ed) 28 Example DHCP Request (Selected Fields) Example DHCP ACK (Selected Fields) Option 50: Requested IP Address = 152.14.62.39 Ethernet II, Src: 152.14.62.3 (00:08:7c:25:bf:fd), Dst: 152.14.62.39 Option 12: Host Name = “mulberry" (00:11:43:41:28:ed) Internet Protocol, Src: 152.14.19.3 (152.14.19.3), Dst: 152.14.62.39 Option 55: Parameter Request List (152.14.62.39) 1 = Subnet Mask User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68) 15 = Domain Name 3 = Router Bootstrap Protocol Message type: Boot Reply (2) 6 = Domain Name Server Transaction ID: 0xc9ea1fd2 44 = NetBIOS over TCP/IP Name Server Bootp flags: 0x0000 (Unicast) 31 = Perform Router Discover Client IP address: 0.0.0.0 (0.0.0.0) 33 = Static Route Your (client) IP address: 152.14.62.39 (152.14.62.39) Next server IP address: 0.0.0.0 (0.0.0.0) Relay agent IP address: 152.14.19.3 (152.14.19.3) Client MAC address: 152.14.62.39 (00:11:43:41:28:ed) copyright 2005 Douglas S.
Recommended publications
  • XEP-0347: Internet of Things - Discovery

    XEP-0347: Internet of Things - Discovery

    XEP-0347: Internet of Things - Discovery Peter Waher mailto:peterwaher@hotmail:com xmpp:peter:waher@jabber:org http://www:linkedin:com/in/peterwaher Ronny Klauck mailto:rklauck@informatik:tu-cottbus:de xmpp:TBD http://www-rnks:informatik:tu-cottbus:de/~rklauck 2018-11-03 Version 0.5.1 Status Type Short Name Deferred Standards Track iot-discovery This specification describes an architecture based on the XMPP protocol whereby Things can be in- stalled and safely discovered by their owners and connected into networks of Things. Legal Copyright This XMPP Extension Protocol is copyright © 1999 – 2020 by the XMPP Standards Foundation (XSF). Permissions Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the ”Specification”), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specifi- cation, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or sub- stantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or pub- lisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation. Warranty ## NOTE WELL: This Specification is provided on an ”AS IS” BASIS, WITHOUT WARRANTIES OR CONDI- TIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.
  • Well Known TCP and UDP Ports Used by Apple Software Products

    Well Known TCP and UDP Ports Used by Apple Software Products

    Well known TCP and UDP ports used by Apple Languages English software products Symptoms Learn more about TCP and UDP ports used by Apple products, such as OS X, OS X Server, Apple Remote Desktop, and iCloud. Many of these are referred to as "well known" industry standard ports. Resolution About this table The Service or Protocol Name column lists services registered with the Internet Assigned Numbers Authority (http://www.iana.org/), except where noted as "unregistered use." The names of Apple products that use these services or protocols appear in the Used By/Additional Information column. The RFC column lists the number of the Request For Comment document that defines the particular service or protocol, which may be used for reference. RFC documents are maintained by RFC Editor (http://www.rfc- editor.org/). If multiple RFCs define a protocol, there may only be one listed here. This article is updated periodically and contains information that is available at time of publication. This document is intended as a quick reference and should not be regarded as comprehensive. Apple products listed in the table are the most commonly used examples, not a comprehensive list. For more information, review the Notes below the table. Tip: Some services may use two or more ports. It is recommend that once you've found an instance of a product in this list, search on the name (Command-F) and then repeat (Command-G) to locate all occurrences of the product. For example, VPN service may use up to four diferent ports: 500, 1701, 1723, and 4500.
  • Lesson-13: INTERNET ENABLED SYSTEMS NETWORK PROTOCOLS

    Lesson-13: INTERNET ENABLED SYSTEMS NETWORK PROTOCOLS

    DEVICES AND COMMUNICATION BUSES FOR DEVICES NETWORK– Lesson-13: INTERNET ENABLED SYSTEMS NETWORK PROTOCOLS Chapter-5 L13: "Embedded Systems - Architecture, Programming and Design", 2015 1 Raj Kamal, Publs.: McGraw-Hill Education Internet enabled embedded system Communication to other system on the Internet. Use html (hyper text markup language) or MIME (Multipurpose Internet Mail Extension) type files Use TCP (transport control protocol) or UDP (user datagram protocol) as transport layer protocol Chapter-5 L13: "Embedded Systems - Architecture, Programming and Design", 2015 2 Raj Kamal, Publs.: McGraw-Hill Education Internet enabled embedded system Addressed by an IP address Use IP (internet protocol) at network layer protocol Chapter-5 L13: "Embedded Systems - Architecture, Programming and Design", 2015 3 Raj Kamal, Publs.: McGraw-Hill Education MIME Format to enable attachment of multiple types of files txt (text file) doc (MSOFFICE Word document file) gif (graphic image format file) jpg (jpg format image file) wav format voice or music file Chapter-5 L13: "Embedded Systems - Architecture, Programming and Design", 2015 4 Raj Kamal, Publs.: McGraw-Hill Education A system at one IP address Communication with other system at another IP address using the physical connections on the Internet and routers Since Internet is global network, the system connects to remotely as well as short range located system. Chapter-5 L13: "Embedded Systems - Architecture, Programming and Design", 2015 5 Raj Kamal, Publs.: McGraw-Hill Education
  • 951 John Gilmore (Sun Microsystems) September 1985

    951 John Gilmore (Sun Microsystems) September 1985

    Network Working Group Bill Croft (Stanford University) Request for Comments: 951 John Gilmore (Sun Microsystems) September 1985 BOOTSTRAP PROTOCOL (BOOTP) 1. Status of this Memo This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. 2. Overview This RFC describes an IP/UDP bootstrap protocol (BOOTP) which allows a diskless client machine to discover its own IP address, the address of a server host, and the name of a file to be loaded into memory and executed. The bootstrap operation can be thought of as consisting of TWO PHASES. This RFC describes the first phase, which could be labeled 'address determination and bootfile selection'. After this address and filename information is obtained, control passes to the second phase of the bootstrap where a file transfer occurs. The file transfer will typically use the TFTP protocol [9], since it is intended that both phases reside in PROM on the client. However BOOTP could also work with other protocols such as SFTP [3] or FTP [6]. We suggest that the client's PROM software provide a way to do a complete bootstrap without 'user' interaction. This is the type of boot that would occur during an unattended power-up. A mechanism should be provided for the user to manually supply the necessary address and filename information to bypass the BOOTP protocol and enter the file transfer phase directly. If non-volatile storage is available, we suggest keeping default settings there and bypassing the BOOTP protocol unless these settings cause the file transfer phase to fail.
  • Optional Interniche Protocol Modules for Nichelite For

    Optional Interniche Protocol Modules for Nichelite For

    fåíÉêkáÅÜÉ=qÉÅÜåçäçÖáÉëI=fåÅK bãÄÉÇÇÉÇ=mêçíçÅçä=péÉÅá~äáëíë ïïïKáåáÅÜÉKÅçã Available from NXP : Optional InterNiche Protocol Modules for InterNiche Technologies and NXP have collaborated to NicheLite for LPC provide an OEM version of InterNiche’s NicheLite™ InterNiche’s optional protocol modules have been optimized for the LPC developed from the ground up to address the needs of low architecture. NicheLite for LPC provides the functionality of cost embedded systems. The result is a modular solution NicheLite and is RFC compliant. that is functionally comprehensive, requiring minimal system and memory requirements, and is tuned for both Key Features portability and performance. • Transmission Control Protocol (TCP) supporting InterNiche's lightweight API, and a Zero-Copy option NicheStack™ SNMP(v1, v2c or v3) are fully compliant agent • Internet Protocol (IPv4), without implementations enabling industry standard device fragmentation and reassembly monitoring with SNMP management workstations. The • User Datagram Protocol (UDP) • Address Resolution Protocol (ARP) complete SDK includes a MIB Compiler tool. • Internet Control Message Protocol (ICMP) NicheStack HTTPServer™ is an innovative robust embedded • Dynamic Host Configuration Protocol (DHCP) Client web server that has been designed specifically to optimize • Name Service (DNS) Client size, performance and support for dynamic data displays • Bootstrap Protocol (BOOTP) • Trivial File Transfer Protocol (TFTP), and important security features. client and server • Ping Protocol Options: A variety of optional protocols support • NicheTool ™ solutions for specific applications including Point to Point • NicheFile ™ VFS • Single Ethernet interface Protocol (PPP), PPPoE, Telnet, FTP, SMTP and POP3. • No "GPL Contamination" Includes two operating systems Options • SuperLoop : a very fast, do-forever loop running various tasks and Email applications in a run-to-completion FTP model.
  • IP Host Configuration IK2218/EP2120

    IP Host Configuration IK2218/EP2120

    IP Host Configuration IK2218/EP2120 Markus Hidell, [email protected] KTH School of ICT Acknowledgements • The presentation builds upon material from - Previous slides by Markus Hidell, Björn Knutsson and Peter Sjödin - Computer Networking: A Top Down Approach, 5th ed. Jim Kurose, Keith Ross. Addison-Wesley. - TCP/IP Protocol Suite, 4th ed, Behrouz Foruzan. McGraw-Hill. 2 Outline • Introduction • Automating IP Configuration • Stateful configuration - DHCP • Stateless configuration – SLAAC • Further reading 3 Basic Question • IP (Internet Protocol): - what packets look like and how to interpret IP addresses • Routing protocols: - calculate paths through the network • DNS (Domain Name System): - how to translate between names and IP addresses But how do we get an IP address for a network interface? 4 Manual IP Address Configuration • System administrator: - Manually select an IP address from currently unassigned addresses in the subnet - Assign to host machine - Manually edit configuration file on host machine • Statically assigned address - require work to change address • What if... - Sysadmin forgets to mark address as assigned? - Subnet changes address? Manual IP address configuration is not a practical solution 5 IP Configuration Information • Just IP address is not enough information for hosts - Need to know subnet mask for local traffic • CIDR notation: 10.1.1.0/24 - Need to know IP address of gateway for non-local traffic • Gateway: the router that connects our subnet to the Internet (default gateway) • What else might we want to tell
  • Bootstrap Protocol, BOOTP, Is the Recommended Way to Establish Communications from the Host to the Printer in an Internet Protocol Environment

    Bootstrap Protocol, BOOTP, Is the Recommended Way to Establish Communications from the Host to the Printer in an Internet Protocol Environment

    BOOTP Bootstrap protocol, BOOTP, is the recommended way to establish communications from the host to the printer in an internet protocol environment. BOOTP obtains booting data from the bootptab file. With the proper information stored in the bootptab file, the printer can find its own name and IP address and boot from the network without any intervention, even for a first time boot. 1. Verify that the bootpd and bootptab files are in the correct directories: UNIX: /etc or /usr/etc directory OS/2: \TCPIP\ETC (for bootptab) and \TCPIP\BIN (for bootpd) LAN Server: MPTN\ETC (for bootptab) and \MPTN\BIN (for bootpd) Type: ls bootp* 2. Edit the hosts file to add the printer internet addresses and names: 128.07.60.30 P340-mktg 128.07.60.31 P340-sales For OS/2, use the TCP/IP Configuration Notebook under the Services tab to add the printer internet addresses and names. 3. Some UNIX hosts may require an explicit update to the arp table to add the new entries. This command is host-specific; check your host documentation for details. arp -s ether P340-mktg 08:00:11:01:00:45 arp -s ether P340-sales 08:00:11:01:00:46 The ether switch indicates that you are providing an Ethernet address. 4. Set up the bootptab file. 5. Start or restart the inetd or bootpd daemon. For OS/2 Warp, LAN Server 4.0, and UNIX, use the bootpd daemon. Here is a sample bootptab file; check your host system documentation to see which fields your implementation of BOOTP supports.
  • Kenneth Brennan ISC330 Lab 1 How Many Packets (Frames)

    Kenneth Brennan ISC330 Lab 1 How Many Packets (Frames)

    Kenneth Brennan ISC330 Lab 1 How many packets (frames) are there in this capture? 499 Choose the first frame in the top pane. Expand the Internet Protocol triangle of this frame in the middle pane. What are the source and destination addresses of this packet? 10.1.6.18 10.1.3.143 To what entities do these numbers refer? IP addresses Expand the Transmission Control Protocol triangle of the packet. What are the source and destination ports of this packet? i. 1720 ii. 32803 To what entities do these numbers refer? iii. Port numbers Note that wireshark is smart enough to "know" which ports are typically used by internet applications. what service is the host at IP 10.1.3.143 trying to access on the host with IP 10.1.6.18? [hint] ​ ​ Telephone call Read this discussion excerpted from here and answer the questions that follow ​ ​ as best you can. H.323 uses a single fixed TCP port (1720) to start a call using the H.225 protocol (defined by H.323 suite) for call control. Once that protocol is complete, it then uses a dynamic TCP port for the H.245 protocol (also defined by the H.323 suite) for capabilities exchange (caps exchange) and channel control. Finally, it opens up two dynamic UDP ports for each type of media that was negotiated for the call (audio, video, far-end camera control, etc.). This first port carries the RTP protocol data (defined by the H.225 specification) and the second one carries the RTCP data (defined by the H.225 specification).
  • Network Protocols and Service

    Network Protocols and Service

    UNIT 2 NETWORK PROTOCOLS AND SERVICE 1 SYLLABUS 2.1 Dynamic Host Control Protocol(DHCP): DHCP Origins :ARP,RARP,BOOTP DHCP Objectives, IP Address assignments, DHCP Architecture. 2.2 Introduction to Domain Name Systems (DNS) DNS Objectives Domain Naming, Top Lavel Domains, Second Level Domains, Sub- domains DNS Functions, Resource Records, DNS Name Resolution, Resolves, DNS Requests, Root Name Servers, Resolving a Domain Name, DNS Name Registration 2.3 Network Printing Concepts Locally Connected Print Devices, Setting up local Print Devices, Shared Print Devices, Sharing Locally Attached Print Devices, 2 Describe Windows Network Printing and Add print Wizard. 2.1 DHCP ORIGINS: ADDRESS RESOLUTION PROTOCOL(ARP) . Address Resolution Protocol (ARP) is a protocol for mapping an Internet Protocol address (IP address) to a physical machine address that is recognized in the local network. ARP stands for Address Resolution Protocol. When you try to ping an IP address on your local network, say 192.168.1.1, your system has to turn the IP address 192.168.1.1 into a MAC address. This involves using ARP to resolve the address, hence its name. Systems keep an ARP look-up table where they store information about what IP addresses are associated with what MAC addresses. 3 ARP CONT… . When trying to send a packet to an IP address, the system will first consult this table to see if it already knows the MAC address. If there is a value cached, ARP is not used. If the IP address is not found in the ARP table, the system will then send a broadcast packet to the network using the ARP protocol to ask "who has 192.168.1.1".
  • Supporting Protocols and Framing

    Supporting Protocols and Framing

    Internet Protocols Supporting Protocols and Framing Updated: 9/30/14 Supporting Protocols p ARP / RARP p BOOTP p ICMP p DHCP p NAT IP Supporting Protocols p IP protocol only deals with the data transfer (best-effort) n Possible Errors that can happen and not detected by IP: Data lost, duplication, out-of- order n However there are some error checking mechanisms: p CRC, TTL IP Supporting Protocols We focus on the following Protocols: ICMP, ARP, RARP, BOOTP, DHCP Whose IP It is mine: ARP is this? MAC/IP (Address Resolution Protocol) p Used to resolve network layer addresses into link layer addresses p Exploits broadcast property of a LAN p Each host on LAN maintains a table of IP subnetwork addresses p If the address can not be found ARP broadcasts a request n Shouting: Who knows about this IP address? p Other hosts listen and reply n The reply includes IP address and MAC (unicast) n Any interested host can learn about the new information ARP Example 1 2 p Assume 1 is sending a message to 2 (192.31.65.5) n What is the MAC address for 192.31.65.5? Use ARP broadcast! p Host 2 responds to Host 1: it is E2 n Host 1 maps IP and MAC; p Encapsulate the IP message in the Ethernet frame and sends it n Cashing can enhance ARP operation (Node 1 can cash the result) ARP Example 1 4 p Assume 1 is sending a message to 4 ([email protected]) n ee.sonoma.edu is the destination n Host 1 sends a message to Domain Name System (DNS): what is the IP address for ee.sonoma.edu? à 192.31.63.8 n What is the MAC address for 192.31.63.8? ARP cannot pass through the router! p Two choices: 1.
  • Bootp and DHCP

    Bootp and DHCP

    BootP and DHCP Flexible and Scalable Host Configuration (C) Herbert Haas 2005/03/11 1 Shortcomings of RARP Reverse Address Resolution Protocol Only IP Address distribution No subnet mask Using hardware address for identification New methods needed: BOOTP, DHCP (C) Herbert Haas 2005/03/11 2 RARP was one of the first protocols which offers automatically an IP Address to a new connected client. But RARP is an old protocol with many disadvantages. It can only distribute an IP Address without a subnet mask. RARP uses the hardware address for identification. This make it impossible to connect new clients to the network without some administrative work. 2 Bootstrap Protocol (BOOTP) A static solution with many parameters 3 Goal Clients request IP address and other parameters from server Subnet mask, configuration filename, ... IP addresses are predefined in a list Fixed mapping MAC address IP address Defined in RFC 951 and RFC 1048 (C) Herbert Haas 2005/03/11 4 The Bootstrap Protocol can offer many important parameters to the client. The most important parameters are the subnet mask and the configuration filename. With the configuration filename it is possible to connect a no-disk client. Also BOOTP uses a fixed mapping via hardware address (Ethernet Mac Address). 4 Bootstrap Eth2 DA = FFFF.FFFF.FFFF DA = 255.255.255.255 IP SA = 0.0.0.0 DPort = 67 UDP SPort = 68 Request-ID = 77 B Client IP = 0.0.0.0 O MAC = A O Your IP = ? T BOOTP Server IP = ? P Server Image File = ? Here is MAC A, I need an IP address, and something to boot! TFTP BOOTP Client Server (C) Herbert Haas 2005/03/11 5 In the picture above you see the classic bootstrap principle.
  • Network Protocols Handbook

    Network Protocols Handbook

    Third Edition Network Protocols TCP/IP Ethernet ATM Handbook Frame Relay WAN LAN MAN WLAN SS7/C7 VOIP Security VPN SAN VLAN IEEE IETF ISO Javvin Technologies,ITU-T Inc. ANSI Cisco IBM Apple Microsoft Novell I Table of Contents Table of Contents Network Communication Architecture and Protocols•••••••••••••••••••••••••••••••••••••••••••••1 OSI Network Architecture 7 Layers Model•••••••••••••••••••••••••••••••••••••••••••••••••••••••••2 TCP/IP Four Layers Archiitecture Model••••••••••••••••••••••••••••••••••••••••••••••••••••••••••5 Other Network Architecture Models: IBM SNA•••••••••••••••••••••••••••••••••••••••••••••••••7 Network Protocols: Definition and Overview•••••••••••••••••••••••••••••••••••••••••••••••••••••9 Protocols Guide••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••11 TCP/IP Protocols••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••11 Application Layer Protocols••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••13 BOOTP: Bootstrap Protocol•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••13 DCAP: Data Link Switching Client Access Protocol••••••••••••••••••••••••••••••••••••••••••••••••••••••14 DHCP: Dynamic Host Configuration Protocol•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••15 DNS: Domain Name System (Service) Protocol•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••16 FTP: File Transfer Protocol••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••17