WO2002011402A1 - Serveur dhcp dote de fonctions de prise en charge de demande rarp - Google Patents

Serveur dhcp dote de fonctions de prise en charge de demande rarp Download PDF

Info

Publication number
WO2002011402A1
WO2002011402A1 PCT/US2001/023883 US0123883W WO0211402A1 WO 2002011402 A1 WO2002011402 A1 WO 2002011402A1 US 0123883 W US0123883 W US 0123883W WO 0211402 A1 WO0211402 A1 WO 0211402A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
address
protocol
based network
broadcast
Prior art date
Application number
PCT/US2001/023883
Other languages
English (en)
Inventor
Joshau T. Levasseur
Original Assignee
Loudcloud, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Loudcloud, Inc. filed Critical Loudcloud, Inc.
Priority to AU2001278082A priority Critical patent/AU2001278082A1/en
Publication of WO2002011402A1 publication Critical patent/WO2002011402A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses

Definitions

  • the present invention relates generally to network communication protocols, interfaces between different protocols, and the configuration of network information on a server. Specifically, the present invention relates to adding new clients to a network and providing them with network addresses.
  • Computer networks have become an integral part of everyday life. By way of various computer networks, activities such as data sharing, electronic commerce, multi-media broadcasting and other useful exchanges of data have been enabled. Some of these networks include, for example, local area networks (LAN), wide area networks (WAN), the Internet, and other similar networks that utilize data packets for transferring data from one computer location to another. In transferring data from one location on a network to another, a network data transfer protocol, or communications protocol, and an addressing scheme are necessary.
  • LAN local area networks
  • WAN wide area networks
  • the Internet In transferring data from one location on a network to another, a network data transfer protocol, or communications protocol, and an addressing scheme are necessary.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • Addresses are also a necessary element of communications on a network.
  • IP Internet protocol
  • An IP address has two portions: a network address portion, and a host address portion.
  • the network address portion identifies a network, within which the device being addressed resides, and the host address portion uniquely identifies the device being addressed within that network.
  • the combination of network address and host address is unique, such that no two devices have the same IP address.
  • These addresses are 32 bits long and are usually written in a decimal notation, such as: A. B.C. D, where the variables A, B, C, and D are each an octet having a numerical value between 0 and 255.
  • IP addresses expressed in this form are used in the source address and destination address fields contained within IP packets, and allow for unique addressing of each data packet to a specific device connected to the Internet. Within the IP packets, the IP addresses are expressed in network-byte communication order. Thus, since the address of a particular device on a network is crucial for correctly transmitting data packets to that device, obtaining a unique address identifier, such as an IP address, is important and must be correctly carried out so that the device on the network can communicate with other devices on the network. Accordingly, various protocols have been devised to assign unique logical network addresses, such as IP addresses for the Internet, to devices contained within a local network. Typically, a computer does not know its network address when booted, and only has information regarding its hardware interface address, such as an Ethernet address. To use a protocol such as the Internet Protocol (IP), the computer must be assigned a unique IP address.
  • IP Internet Protocol
  • Various address assignment protocols have been devised to assign a logical network address, such as an IP address, based on a particular device's hardware interface address, such as an Ethernet address.
  • Two types of protocols that are commonly used for network address assignment are broadcast-based protocols and address-based protocols.
  • broadcast-based protocols broadcast a request for network address assignment and then do not further utilize the network address that is assigned for communication with the server.
  • Address-based protocols broadcast a request for network address assignment and then can continue to use the assigned network address to communicate with the server for transmitting configuration information and other data.
  • One specific type of broadcast-based protocol that is discussed in connection with embodiments of the present invention is the reverse address resolution protocol (RARP).
  • RARP reverse address resolution protocol
  • Two specific types of address-based protocols discussed in connection with the present invention are the bootstrap protocol (BOOTP) and the dynamic host configuration protocol (DHCP), which is an evolution of BOOTP.
  • BOOTP bootstrap protocol
  • DHCP dynamic host configuration protocol
  • the reverse address resolution protocol is a common address resolution protocol used by some computer systems, such as the Ultrasparc servers of Sun Microsystems, Inc.
  • RARP is a broadcast-based protocol that is used to announce a client to the network and request a network address, and has the advantage of being light-weight, or simple.
  • RARP does not have as many features as other protocols, such as DHCP.
  • DHCP dynamic host configuration protocol
  • DHCP clients may communicate with a DHCP server on a different network.
  • DHCP allows for use of a network gateway or helper, such as a router, for example, and RARP does not.
  • addressed-based protocols such as BOOTP and DHCP
  • BOOTP and DHCP allow for dynamic configuration of IP addresses, thereby allowing IP addresses to be allocated on a temporary or permanent basis to the requesting client, as deemed necessary. Allocation of IP addresses on a temporary basis allows the entire network to more efficiently manage available IP addresses.
  • An additional advantage of DHCP is that it provides a mechanism for a requesting client to obtain all of the configuration information required for the client to operate on the network.
  • a system and method that is capable of operating with both types of protocols, address-based network protocols, such as BOOTP and DHCP, and broadcast- based network protocols, such as RARP on the same network, and thereby utilize the advantages of both types of protocols and allow communication between devices using both types of protocols.
  • address-based network protocols such as BOOTP and DHCP
  • broadcast- based network protocols such as RARP on the same network
  • mapping file When a request is issued from a network client using a broadcast-based network protocol to a network server using an address- based network protocol, a mapping file is examined and an unused network address is selected, and the mapping file is updated to indicate that the network address has been assigned. Normal server processing is restarted, and a response to the network client is generated using the broadcast-based protocol to provide the network address.
  • a system for handling requests from devices using multiple network protocols has a network server that uses an address-based network protocol, at least one network client connected to the network using a broadcast-based network protocol, and a series of instructions for interpreting the requests made by a network client using a broadcast-based network protocol, and assigning a network address by using the mapping file of the server which uses an address-based network protocol.
  • FIG 1 is a block diagram of a typical network using a reverse address resolution protocol (RARP) .
  • RARP reverse address resolution protocol
  • FIG. 2 is a flow diagram of the steps associated with the reverse address resolution protocol (RARP).
  • RARP reverse address resolution protocol
  • FIG 3 is a block diagram of a typical network using a dynamic host configuration protocol (DHCP).
  • Figure 4 is a flow diagram illustrating various steps of dynamic host configuration protocol (DHCP) address resolution.
  • DHCP dynamic host configuration protocol
  • Figure 5 is a block diagram of one embodiment of the present invention.
  • Figure 6 is a block diagram of another embodiment of the present invention.
  • Figure 7 is a flow diagram illustrating the various steps performed by the system and method of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • a local network such as an Ethernet network
  • a DHCP server assigns IP addresses to BOOTP, DHCP, and RARP clients on the local network for communication with an external network, such as the Internet.
  • an external network such as the Internet
  • FIG. 1 A typical network, which employs the RARP protocol to assign network addresses, is illustrated in Figure 1.
  • an RARP server 102 is connected, via a local network 104, to various clients 106, 108, 110.
  • the local network 104 may comprise any of a variety of different types of physical networks.
  • the network 104 may be an Ethernet network or other suitable broadcast-based networks, wherein devices request network address assignment using a broadcast-based network protocol.
  • the network 104 may be connected to an external network 112 as illustrated by the broken line 114.
  • This external network may be a variety of networks external to the local network 104.
  • the external network 112 may comprise the Internet or portions thereof.
  • FIG. 2 A flow diagram illustrating the manner in which the RARP network performs address assignment is shown in Figure 2.
  • a network client broadcasts a message over the local network containing its physical device address, such as its Ethernet address, which is contained on its network interface card (NIC). Additionally, other identifiers suitable for use by devices to identify themselves on a broadcast-based network may be used as physical device addresses.
  • the message broadcast by the network client may be carried out as part of the client's normal boot process.
  • an RARP server looks up the device identifier provided in the broadcast message from the network client in a mapping file. This file may be locally stored on the RARP server, such as the server 102 shown in Figure 1, for example, or in a central server.
  • the Ethernet address may be located in a file named "/etc/ethers.” This file provides a mapping between each Ethernet address and an available IP address.
  • the RARP server finds the network address corresponding to the device identifier of the network client broadcasting the message in step 202. This network address may be an IP address used in communication via the Internet, for example.
  • the RARP server responds to the requesting client of step 202, transmitting the logical network address corresponding to its physical device identification.
  • the network client upon receiving the network address from the RARP server, stores it for future reference, so that it may communicate via the external network 112 using the network address provided.
  • the local network discussed in connection with Figures 1 and 2 may comprise an Ethernet network, or other similar, broadcast-based network.
  • the device identifier associated with a network client comprises an Ethernet address.
  • the external network discussed in connection with Figures 1 and 2 may advantageously comprise the Internet, or other similar network.
  • the network address discussed in connection with Figure 2 may comprise an IP address, for example.
  • FIG. 3 is a block diagram of a network that operates in accordance with
  • the DHCP network of Figure 3 comprises a server 302 connected by way of a network 304 to various clients 306, 308, 310.
  • the server 302 is a DHCP server using the DHCP protocol.
  • the network 304 may comprise any suitable network such as those discussed in connection with the network 104 shown in Figure 1.
  • the network 304 may optionally be connected to an external network 312, as shown by the broken line 314.
  • This external network 312 may comprise the Internet, or other similar network.
  • a flow diagram illustrating the basic steps of address assignment in a DHCP network are shown.
  • a client broadcasts a message over the network requesting a network address.
  • This request includes a device identifier for the client, and a session identifier for the client.
  • a decision is made, as illustrated by decision box 404, whether more than one DHCP server is present on the network. If there is more than one DHCP server on the network, as indicated by step 406, a specific DHCP server is chosen to provide a network address to the requesting client. For instance, each server may generate an initial response to the request from the DHCP client. Upon receiving multiple responses, the client can select one of the servers to continue further processing of the request and issue an IP address.
  • FIG. 5 is a block diagram illustrating one embodiment of a network in which the present invention can be employed.
  • at least one RARP client 504 is connected to a network 508 in which logical addresses are assigned by DHCP server 502.
  • a DHCP proxy 506 may also be connected by way of the network 508.
  • an application residing on the network server acts upon the original RARP request, and is transparent to both the RARP client and the DHCP server upon which it resides.
  • the application may be a variety of application types, such as script applications, batch (.BAT) files, UNIX scripts, or other similar applications for executing a series of steps on a computer.
  • any network address assignment such as IP address assignment, for example, is carried out by way of requests from the RARP client 504 to the DHCP server 502 being acted upon and responded to by an application, such as a scripting application.
  • any transmissions of such address information from the DHCP server 502 is communicated to the RARP client 504 by way of an application residing on the DHCP server 502, such as a scripting application.
  • the network 508 may be a sub-network connected to other networks as sub-networks by way of a router, or other connection means.
  • a second embodiment of a network which employs the present invention is shown, wherein a DHCP server 602 is located on one network 604, and the RARP client 606 is comprises one node on another network 608.
  • a network router 610 is used to transmit data between the DHCP server 602 and the RARP client 606.
  • An agent 612 is used to package RARP requests from the RARP client 606 in a network addressable message format to be transferred via network router 610 to the DHCP server.
  • a routine 614 is disposed on the DHCP server for handling RARP requests transmitted from the RARP client 606 and packaged by the agent 612.
  • the network 604 and network 608 may be individual local area networks, or subnetworks in a larger network, e.g. , a WAN.
  • the network 604 may comprise any of a variety of different types of networks, such as Ethernet networks, FDDI networks, token ring networks, asynchronous transfer mode networks (ATM), frame relay networks, cable networks and the like. Additionally, other types of networks are intended to be encompassed inasmuch as they are capable of transmitting broadcast network protocol requests.
  • the term client may include any computer on a network that relies on the DHCP server 502, 602 to provide a network address.
  • the RARP client 504, 604 could be a file server, such as the Ultrasparc server of Sun
  • Microsystems or other similar server. Additionally, it will be understood by those skilled in the art that protocols other than RARP and DHCP may be used in the embodiment shown in Figure 6. For example, another address-based network protocol, such as BOOTP may be used instead of DHCP and another broadcast- based network protocol may be used instead of RARP.
  • RARP Address-based Network Protocol
  • BOOTP address-based network protocol
  • RARP broadcast- based network protocol
  • the network server 502, 602 may be contained within the same machine as the RARP client 504, 606.
  • the client portion of such a machine would operate in the same manner as described above in connection with Figures 5 and 6 for the purposes of network address resolution.
  • the client portion of such a machine would have no knowledge of the server portion of the same machine, and would, therefore, utilize a proxy or routine to assist in handling network address assignment requests.
  • FIG. 7 is a flow diagram of the method performed by the various embodiments of the present invention, such as those shown in Figures 5 and 6, for example.
  • an RARP client generates a request for a network address using a broadcast-based network protocol. This request includes a local network address, or device identification.
  • the DHCP server at Step 704 receives the request, and makes a decision at step 705 as to whether or not the request is an RARP request. If the request is determined not to be an RARP request, then normal DHCP processing is executed on the request, as shown at step 706. However, upon detecting that the request is an RARP request at decision step 705, the routine stops normal DHCP server processing at step 707.
  • the DHCP mapping file is examined at step 708, and state and configuration files are parsed.
  • an unused network address is selected by the routine, which corresponds to the requesting device's device identification, and the DHCP mapping file is updated at step 712.
  • the unused network address selected in step 710 may be a new or previously used network address.
  • the RARP response is sent to the client after normal DHCP server processing is restarted.
  • this order of operation need not be the case in all embodiments of the present invention.
  • the RARP response may be sent before such a re-boot.
  • the RARP request handling routine may place the response to be sent to the client in some cue with a flag indicating that after the re-boot is complete that response is to be sent.
  • the RARP response could be sent before normal DHCP processing is restarted, or anytime after the unused network address has been selected.
  • the RARP response could be sent to the client before the DHCP mapping file has been updated.
  • the present invention provides a system and method for communication between two different computer network address assignment protocols.
  • the present invention provides communication between devices using a broadcast-based network protocol, such as RARP, and a server using an address-based network protocol, such as BOOTP and DHCP network address assignment protocols.
  • the present invention provides a method of assigning a logical network address to a client on a network, wherein the network uses a plurality of protocols for address assignment by way of a series of instructions located on a network server.
  • the present invention provides a system for handling requests from devices using multiple network protocols, wherein the system comprises a network, a network server using an address-based network protocol, and a network client using a broadcast-based network protocol by way of a series of instructions located on the network server.
  • the present invention can be embodied in other specific forms without departing from the spirit or essential characteristics thereof.
  • the invention has been described in the context of network communications protocols used in a local network, such as an Ethernet network, and another network, such as the Internet.
  • the particular type of network, either local or otherwise in which the present invention is used need not be limited to the examples given herein, but rather can include any networks suitable for operation with various computer devices connected via networks.
  • specific protocols have been described in connection with embodiments of the present invention; namely, BOOTP, RARP, and DHCP.
  • the present invention need not be limited to these protocols, but rather may be implemented for use with various protocols suitable for the data communications of the present invention of which these examples are a subset.
  • the present invention also need not be limited to handling requests using one protocol by a server using a second protocol, but rather could be used to facilitate communication between clients and a server on a network using multiple protocols.
  • the present invention in such multi-protocol systems would operate in the same manner described herein, by extracting device information from a client's address request, handling the request by an application residing on the server and generating a response in a protocol understood by the requesting client.
  • request handling in such a multi-protocol network can be performed between many protocols and not just two in the same manner described herein, using an application for handling requests in multiple protocols, which resides on the server.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)

Abstract

L'invention concerne un système et un procédé d'assignation d'une adresse de réseau à un client sur un réseau radiodiffusion. Une demande d'adresse dans un protocole de réseau radiodiffusion est interprété par un programme résidant sur un serveur de réseau qui utilise un protocole de réseau adresse et transmet une adresse au client du réseau en utilisant un protocole de réseau radiodiffusion. Le système et le procédé permettent d'obtenir, selon une forme d'exécution, une série d'instructions sur un serveur utilisant un protocole de réseau adresse, tel que RARP, pour l'interprétation d'instructions utilisant un protocole de réseau radiodiffusion, tel que DHCP et BOOTP, en vue de fournir une adresse IP à un client sur un réseau radiodiffusion, tel que, par exemple, un réseau Ethernet. L'invention concerne en outre un système de prise en charge de demandes provenant de dispositifs utilisant de multiples protocoles de réseaux.
PCT/US2001/023883 2000-07-31 2001-07-31 Serveur dhcp dote de fonctions de prise en charge de demande rarp WO2002011402A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001278082A AU2001278082A1 (en) 2000-07-31 2001-07-31 Dhcp server with rarp request handling capabilities

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US62982700A 2000-07-31 2000-07-31
US09/629,827 2000-07-31

Publications (1)

Publication Number Publication Date
WO2002011402A1 true WO2002011402A1 (fr) 2002-02-07

Family

ID=24524660

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/023883 WO2002011402A1 (fr) 2000-07-31 2001-07-31 Serveur dhcp dote de fonctions de prise en charge de demande rarp

Country Status (2)

Country Link
AU (1) AU2001278082A1 (fr)
WO (1) WO2002011402A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1365609A1 (fr) * 2002-05-22 2003-11-26 Huawei Technologies Co., Ltd. Procédé pour établir automatiquement un canal d'opération et de maintenance pour une station de base dans des résaux mobiles de télécommunication internationaux
WO2008017666A1 (fr) 2006-08-09 2008-02-14 Siemens Aktiengesellschaft Procédé de localisation d'un abonné de communication, utilisation d'un tel procédé et boîtier de commande avec une implémentation du procédé
CN111886845A (zh) * 2018-03-23 2020-11-03 昕诺飞控股有限公司 在通信互连装置网络中执行空中下载（ota）升级的方法和装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0883266A2 (fr) * 1997-05-12 1998-12-09 Kabushiki Kaisha Toshiba Dispositif de routage, procédé de transfert de datagrammes et système de communication réalisant le contrÔle de changement de cellules pour des terminaux mobiles
EP0946027A2 (fr) * 1998-03-26 1999-09-29 Hewlett-Packard Company Appareil et procédé pour configurer un noeud de réseau pour être sa prope passerelle

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0883266A2 (fr) * 1997-05-12 1998-12-09 Kabushiki Kaisha Toshiba Dispositif de routage, procédé de transfert de datagrammes et système de communication réalisant le contrÔle de changement de cellules pour des terminaux mobiles
EP0946027A2 (fr) * 1998-03-26 1999-09-29 Hewlett-Packard Company Appareil et procédé pour configurer un noeud de réseau pour être sa prope passerelle

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1365609A1 (fr) * 2002-05-22 2003-11-26 Huawei Technologies Co., Ltd. Procédé pour établir automatiquement un canal d'opération et de maintenance pour une station de base dans des résaux mobiles de télécommunication internationaux
WO2008017666A1 (fr) 2006-08-09 2008-02-14 Siemens Aktiengesellschaft Procédé de localisation d'un abonné de communication, utilisation d'un tel procédé et boîtier de commande avec une implémentation du procédé
CN101502081B (zh) * 2006-08-09 2012-10-03 西门子公司 定位通信用户的方法、这种方法的应用和实施这种方法的操作设备
CN111886845A (zh) * 2018-03-23 2020-11-03 昕诺飞控股有限公司 在通信互连装置网络中执行空中下载（ota）升级的方法和装置

Also Published As

Publication number Publication date
AU2001278082A1 (en) 2002-02-13

Similar Documents

Publication Publication Date Title
US7046666B1 (en) Method and apparatus for communicating between divergent networks using media access control communications
Alexander et al. DHCP options and BOOTP vendor extensions
Cheshire et al. Multicast dns
Droms Dynamic host configuration protocol
US7412515B2 (en) Method and apparatus for dynamic assignment of network protocol addresses
JP4043052B2 (ja) Ｄｈｃｐを用いてネットワークにおける学習されたｉｐアドレスをオーバライドする方法
Droms RFC2131: Dynamic Host Configuration Protocol
US6061739A (en) Network address assignment using physical address resolution protocols
US7339895B2 (en) Gateway device and control method for communication with IP and IPV6 protocols
US6353614B1 (en) Method and protocol for distributed network address translation
KR100560737B1 (ko) 듀얼스택을 이용한 아이피브이4 - 아이피브이6 전환 장치및 그 방법
US8028035B2 (en) Shared resource support for internet protocols
US20040107287A1 (en) Method and apparatus for communicating on a communication network
CN105577852B (zh) 用于生成功能地址的系统和方法
Cheshire et al. Rfc 6762: Multicast dns
US9819641B2 (en) Method of and a processing device handling a protocol address in a network
US20120198091A1 (en) Network system, control apparatus and network apparatus
JPH11252172A (ja) パケット生成方法およびその機能を有する情報処理装置並びにパケット生成プログラムを記録した記録媒体
JPH1117726A (ja) Ｄｎｓ機能を内蔵したｉｐネットワークの結合制御装置
US6823386B1 (en) Correlating data streams of different protocols
US7085836B1 (en) System and method for automatic private IP address selection
Alexander et al. RFC2132: DHCP Options and BOOTP Vendor Extensions
WO2002011402A1 (fr) Serveur dhcp dote de fonctions de prise en charge de demande rarp
Cisco DHCP Options
WO2002011393A2 (fr) Passerelle independante d'un serveur de protocole rarp entre un protocole de configuration hote dynamique (dhcp) et le protocole rarp

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP