+

WO2002011393A2 - Passerelle independante d'un serveur de protocole rarp entre un protocole de configuration hote dynamique (dhcp) et le protocole rarp - Google Patents

Passerelle independante d'un serveur de protocole rarp entre un protocole de configuration hote dynamique (dhcp) et le protocole rarp Download PDF

Info

Publication number
WO2002011393A2
WO2002011393A2 PCT/US2001/023898 US0123898W WO0211393A2 WO 2002011393 A2 WO2002011393 A2 WO 2002011393A2 US 0123898 W US0123898 W US 0123898W WO 0211393 A2 WO0211393 A2 WO 0211393A2
Authority
WO
WIPO (PCT)
Prior art keywords
network
address
protocol
client
server
Prior art date
Application number
PCT/US2001/023898
Other languages
English (en)
Other versions
WO2002011393A3 (fr
Inventor
Jacob M. Mcguire
Jay Soffian
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 AU2001279091A priority Critical patent/AU2001279091A1/en
Publication of WO2002011393A2 publication Critical patent/WO2002011393A2/fr
Publication of WO2002011393A3 publication Critical patent/WO2002011393A3/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/5038—Address allocation for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]

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.
  • address-based network protocols such as 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.
  • a system and method of assigning a network address to a client on a network that uses a plurality of protocols is provided.
  • a request is issued from a network client using a broadcast-based network protocol
  • a hardware or device address is extracted from the request, and a request is generated using an address-based network protocol incorporating the hardware address previously extracted.
  • 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 gateway connected to the network for translating between the network client and network server.
  • the gateway translates requests from the network client using the broadcast-based network protocol into requests using the address-based network protocol for handling by the network server.
  • the gateway also translates responses from the network server into responses using the broadcast-based network protocol for the network client.
  • network clients using multiple protocols may operate on the same network. Additionally, there is no need for an address assignment server on the network of each requesting client.
  • 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).
  • DHCP dynamic host configuration protocol
  • Figure 4 is a flow diagram illustrating various steps of dynamic host configuration protocol (DHCP) address resolution.
  • 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.
  • DHCP dynamic host configuration protocol
  • Figure 7 is a flow diagram illustrating the various steps performed by the system and method of the present invention.
  • 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.
  • 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, or its Ethernet address, which is contained on its network interface card (NIC).
  • NIC network interface card
  • other identifiers suitable for use by devices on a broadcast-based network using a broadcast-based network protocol 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 name "/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 addresses 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 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.
  • the present invention need not be limited to any of the specific embodiments described wherein the local network is an Ethernet network and the external network is the Internet.
  • the networks of the present invention may comprise any suitable broadcast-based network and address-based network.
  • Figure 3 is a block diagram of a network that operates in accordance with the DHCP or BOOTP protocols. For the sake of simplicity, only DHCP will be referenced in the following discussion. However, it will be recognized that the illustrative example is equally applicable to BOOTP.
  • 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 local 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 network addresses are assigned by a DHCP server 502.
  • a DHCP proxy 506 operates as a gateway between the RARP client 504 and the DHCP server 502, acting as a translator between the two protocols used by these two respective devices.
  • any network address assignment such as IP address assignment, for example, is carried out by the DHCP server 502 in response to requests broadcast from the RARP client 504 that are relayed via the DHCP proxy 506.
  • any transmissions of such address information from the DHCP server 502 is communicated to the RARP client 504 by way of a DHCP proxy 506.
  • the DHCP server and the DHCP proxy are depicted as separate logical devices on the network. It will be appreciated, however, that they can be embodied in the same physical device.
  • the proxy 506 may use address-based protocols other than DHCP, such as BOOTP, and the like.
  • 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 an RARP client 606 and an RARP-to-DHCP proxy 607 are contained on another network 608.
  • a DHCP helper 610 is used for mediating requests and data transmissions between the DHCP server 602 and the RARP client 606, as relayed by the RARP-to-DHCP proxy 607.
  • This DHCP helper 610 may be, for example, a network router that interconnects the two local networks.
  • the proxy 607 is used to assist the DHCP helper 610 in converting RARP requests to DHCP requests.
  • the DHCP helper 610 may be a router, which has no method of internally storing data, such as a hard drive or the like.
  • the proxy 607 may be used to provide such functionality.
  • the present invention may employ an alternative embodiment in which the functionality of the RARP-to-DHCP proxy 607 is actually contained within the DHCP helper 610.
  • 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.
  • the term client as used in connection with the present invention, 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.
  • 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 using a broadcast-based network protocol, such as an RARP request, in the normal manner.
  • a DHCP gateway e.g.
  • the DHCP client of Figure 5 or the DHCP helper, or network router, asserted by the RARP-to-DHCP proxy of Figure 6, receives that RARP request from the client and, in step 706, extracts the device identifier from the RARP request.
  • the device identifier Once the device identifier has been extracted from the RARP request by the RARP-to-DHCP proxy, it generates and transmits a conventional address-based network protocol, such as a DHCP request or BOOTP request using the device identifier that has been extracted, as shown in step 708.
  • the DHCP server then carries out normal processing to select an unused logical network address for the requesting client, using the extracted identifier of the client device, as shown in step 710.
  • the DHCP server might perform the steps of parsing state and configuration files, and selecting an unused network address.
  • the DHCP server transmits the network address to the DHCP gateway, which is received by such in step 714.
  • the DHCP gateway generates a standard RARP response to communicate the network address received from the DHCP server.
  • the RARP client receives the network address communicated by the DHCP server, and is able to communicate via the network using this network address.
  • the present invention provides a system and method for communication between two different computer network communications protocols by way of a server-independent gateway.
  • the present invention provides communication between devices using RARP and DHCP 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.
  • 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, a network client using a broadcast-based network protocol, and a gateway, which is generally assisted by a proxy, for translating between the network server and network client.
  • 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 an external network, such as the Internet.
  • the particular type of network, either local or external, 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, RARP, BOOTP, 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 translation between two protocols, 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, translating the request into a protocol understood by the server, and translating the server's response into a protocol understood by the requesting client.
  • the translations in such a multi-protocol network can be performed between any number of protocols.
  • the present invention may make use of multiple clients on a network and not solely one.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

La présente invention porte sur un système et un procédé d'attribution d'une adresse de réseau à un client d'un réseau au moyen d'une pluralité de protocoles. Une demande d'adresse est traduite à partir d'un protocole de réseau sur la base d'une diffusion à un protocole de réseau à base d'adresse, et une attribution d'adresse est traduite d'un protocole de réseau à base d'adresse à un protocole de réseau à base de diffusion entre un client et un serveur du réseau. Ce système et ce procédé, selon une réalisation, assurent une passerelle indépendante d'un serveur entre des protocoles spécifiques, BOOTP, DHCP et RARP, de façon à envoyer une adresse IP à un dispositif sur un réseau local tel qu'un réseau Ethernet. Cette invention porte également sur un système de gestion de requêtes à partir de dispositifs utilisant plusieurs protocoles de réseau, ce système comprenant un serveur connecté à un réseau, un client connecté au réseau et une passerelle connectée au serveur et au client du réseau pour traduire des communications entre le serveur et le client du réseau.
PCT/US2001/023898 2000-07-31 2001-07-31 Passerelle independante d'un serveur de protocole rarp entre un protocole de configuration hote dynamique (dhcp) et le protocole rarp WO2002011393A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001279091A AU2001279091A1 (en) 2000-07-31 2001-07-31 Rarp server-independent gateway

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US62982900A 2000-07-31 2000-07-31
US09/629,829 2000-07-31

Publications (2)

Publication Number Publication Date
WO2002011393A2 true WO2002011393A2 (fr) 2002-02-07
WO2002011393A3 WO2002011393A3 (fr) 2003-02-13

Family

ID=24524665

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/023898 WO2002011393A2 (fr) 2000-07-31 2001-07-31 Passerelle independante d'un serveur de protocole rarp entre un protocole de configuration hote dynamique (dhcp) et le protocole rarp

Country Status (2)

Country Link
AU (1) AU2001279091A1 (fr)
WO (1) WO2002011393A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021244456A1 (fr) * 2020-05-30 2021-12-09 华为技术有限公司 Procédé de résolution d'adresse inverse et dispositifs électroniques

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3529621B2 (ja) * 1997-05-12 2004-05-24 株式会社東芝 ルータ装置、データグラム転送方法及び通信システム
US6070187A (en) * 1998-03-26 2000-05-30 Hewlett-Packard Company Method and apparatus for configuring a network node to be its own gateway

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021244456A1 (fr) * 2020-05-30 2021-12-09 华为技术有限公司 Procédé de résolution d'adresse inverse et dispositifs électroniques

Also Published As

Publication number Publication date
AU2001279091A1 (en) 2002-02-13
WO2002011393A3 (fr) 2003-02-13

Similar Documents

Publication Publication Date Title
US7046666B1 (en) Method and apparatus for communicating between divergent networks using media access control communications
KR100485801B1 (ko) 서로 다른 사설망에 존재하는 네트워크장치들 간의직접접속을 제공하는 망접속장치 및 방법
US6580717B1 (en) Packet communication method and apparatus and a recording medium storing a packet communication program
US8307048B2 (en) Network system with initiator subnetwork communication to target subnetwork communication including fibre channel over ethernet to fibre channel over internet protocol conversion
US7701952B2 (en) Packet communication method and apparatus and a recording medium storing a packet communication program
JP3903014B2 (ja) インターネットプロトコルアドレス変換装置及びこれを用いたホームネットワークシステム並びにその通信方法
US7231452B2 (en) Method and apparatus for communicating on a communication network
KR100560737B1 (ko) 듀얼스택을 이용한 아이피브이4 - 아이피브이6 전환 장치및 그 방법
JP4130962B2 (ja) ネットワーク上のデスティネーションへ送信されたデータの経路決めをするドメイン名を使用するためのシステムおよび方法
EP1754351B1 (fr) Procédé et appareil de gestion de demandes ipv4 dns ptr à travers des réseaux ipv4 et ipv6
JP3735348B2 (ja) インターネットプロトコルアドレス変換装置、これを用いた通信ネットワークシステム及び通信方法
US8028035B2 (en) Shared resource support for internet protocols
KR100587560B1 (ko) 링크 로컬 주소를 가지는 시스템에서 외부 시스템과통신하는 방법 및 장치
JP3915230B2 (ja) パケット生成方法およびその機能を有する情報処理装置並びにパケット生成プログラムを記録した記録媒体
JPH1117726A (ja) Ｄｎｓ機能を内蔵したｉｐネットワークの結合制御装置
US7085836B1 (en) System and method for automatic private IP address selection
US20060067350A1 (en) Method of assigning network identifiers by means of interface identifiers
WO2002011393A2 (fr) Passerelle independante d'un serveur de protocole rarp entre un protocole de configuration hote dynamique (dhcp) et le protocole rarp
JP4349413B2 (ja) パケット生成方法およびその機能を有する情報処理装置並びにパケット生成プログラムを記録した記録媒体
WO2002011402A1 (fr) Serveur dhcp dote de fonctions de prise en charge de demande rarp
KR101052913B1 (ko) ＩＰｖ６ 주소를 할당하는 네트워크 시스템 및 그 방법
KR20030075237A (ko) 서로 다른 인터넷 프로토콜을 사용하는 애플리케이션을구비한 호스트가 목적지 플랫폼과 통신하기 위한 방법 및시스템
Elahi et al. Internet Protocols Part I
Davies TCP/IP Fundamentals for Microsoft Windows
Pittet ARP and IP broadcast over HIPPI-800

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

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: A2

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

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载