US20090092063A1 - METHOD AND APPARATUS FOR PROVIDING LINK-LOCAL IPv4 ADDRESSING ACROSS MULTIPLE INTERFACES OF A NETWORK NODE - Google Patents
METHOD AND APPARATUS FOR PROVIDING LINK-LOCAL IPv4 ADDRESSING ACROSS MULTIPLE INTERFACES OF A NETWORK NODE Download PDFInfo
- Publication number
- US20090092063A1 US20090092063A1 US12/257,266 US25726608A US2009092063A1 US 20090092063 A1 US20090092063 A1 US 20090092063A1 US 25726608 A US25726608 A US 25726608A US 2009092063 A1 US2009092063 A1 US 2009092063A1
- Authority
- US
- United States
- Prior art keywords
- interface
- interfaces
- node
- address
- network node
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
Images
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/5038—Address allocation for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
-
- 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/5046—Resolving address allocation conflicts; Testing of addresses
-
- 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/5092—Address allocation by self-assignment, e.g. picking addresses at random and testing if they are already in use
Definitions
- the present invention relates to the process of configuring Internet Protocol version 4 (IPv4) addresses on a network node. More specifically, the present invention relates to a method and an apparatus for providing link-local IPv4 addressing across multiple interfaces of a network node.
- IPv4 Internet Protocol version 4
- IPv4 Internet Protocol version 4
- USB IPv4-over-Universal Serial Bus
- IPv4-over-Firewire IPv4-over-Firewire
- IPv4 In order to participate in an IPv4 network, a network node, such as a computer or a printer, needs to be configured with IPv4 addresses for one or more of its interfaces. Additionally, in order to enable communication, the network node needs the ability to translate an IPv4 address into the corresponding hardware address.
- the Address Resolution Protocol is a link-level protocol that solves the translation problem by providing an address-resolution mechanism that can be used to find the hardware address for a given IPv4 address, thereby enabling a network node to participate in an IPv4 network.
- IPv4 addresses can be configured either manually by the user, or automatically by the help of another network node, such as a DHCP server. Unfortunately, a DHCP server may not always be available. Moreover, it is cumbersome to have the user configure an IPv4 address. Therefore, there is a strong need for a mechanism by which a network node can automatically configure an IPv4 address on its own.
- Link-local IPv4 addressing provides such a mechanism.
- a network node picks a random IPv4 address in a specified link-local address range and checks for its uniqueness within the scope of the link. If the address is already in use by another network node, then it picks another address and tries again. Once it finds a unique link-local IPv4 address, it uses it to communicate with other nodes in the network.
- a source network-node typically configures only one interface out of all of its interfaces for link-local addressing, because otherwise, two target network-nodes that are connected on different interfaces of the source network-node may choose the same IPv4 address, thereby creating an address ambiguity.
- This is a severe limitation in today's networks, because while the number of interfaces in a network node continues to increase, the user is being forced to use link-local addressing on only one of the interfaces, thereby preventing the user from leveraging link-local IPv4 addressing to simplify network-node configuration.
- One embodiment of the present invention provides a system for providing link-local IPv4 addressing across multiple interfaces of a source network-node.
- the source network-node broadcasts an Address Resolution Protocol (ARP) request packet on multiple interfaces, wherein the ARP-request packet asks for the hardware address of a network node whose link-local IPv4 address is Y.
- ARP Address Resolution Protocol
- the source network-node receives an ARP-reply packet on interface Z 1 from a target network-node whose link-local IPv4 address is Y and whose hardware address is X.
- the source network-node If Y is not present in the ARP cache of the source network-node, an entry is added to the ARP cache, which specifies that IP address Y is at the hardware address X on interface Z 1 .
- the source network-node chooses a winner interface out of Z 1 and Z 2 . If interface Z 1 is chosen as the winner, the source network-node updates the ARP cache so that it specifies that IP address Y is at the hardware address X on interface Z 1 . Finally, the source network-node sends one or more contention-resolution packets on the loser interface to cause the loser network-node to choose another link-local IPv4 address for itself.
- the interface can be an Ethernet interface, a USB interface, a Firewire interface, or an AirPort interface.
- the address prefix for link-local IPv4 addresses can be 169.254/16.
- the contention-resolution packets can be ARP packets.
- the winner interface is chosen based on the speed of the interface.
- sending one or more contention-resolution packets on the loser interface involves sending the packets directly to the loser network-node.
- sending one or more contention-resolution packets on the loser interface involves broadcasting the packets on the loser interface.
- the winner network-node and the loser network-node can be the same entity.
- FIG. 1 illustrates a network node, such as a computer, with multiple interfaces, in accordance with an embodiment of the present invention.
- FIG. 2 illustrates how a network node, such as a computer, can use two of its interfaces to communicate with other network nodes, in accordance with an embodiment of the present invention.
- FIG. 3 illustrates an ARP packet that contains a number of pieces of information that can be used by a source network-node, such as a computer, to resolve the IPv4 address of a target network-node, such as an AirPort device, in accordance with an embodiment of the present invention.
- a source network-node such as a computer
- a target network-node such as an AirPort device
- FIG. 4 presents a flow chart illustrating the process of providing link-local IPv4 addressing across multiple interfaces of a computer, in accordance with an embodiment of the present invention.
- a computer readable storage medium which may be any device or medium that can store code and/or data for use by a computer system. This includes, but is not limited to, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs) and DVDs (digital versatile discs or digital video discs).
- FIG. 1 illustrates a network node, such as a computer 102 , with multiple interfaces 104 , 106 , 108 , and 110 , in accordance with an embodiment of the present invention.
- a network node can generally include any type of communication device capable of communicating with other network nodes via a communication network. This includes, but is not limited to, a computer system based on a microprocessor, a mainframe computer, a printer, a video camera, an external disk drive, a router, a switch, a personal organizer, and a mobile phone.
- the computer 102 illustrated in FIG. 1 has four interfaces, namely, Ethernet interface 104 , Airport interface 106 , USB interface 108 , and Firewire interface 110 .
- An interface can generally include any type of communication component that enables a network node to communicate with another network node over a wire or wireless communication channel.
- Any of the four interfaces 104 , 106 , 108 , and 110 can enable the computer 102 to participate in an IPv4 network.
- the computer 102 can use its Ethernet interface 104 to participate in an IPv4-over-Ethernet local-area network.
- FIG. 2 illustrates how a network node, such as a computer 102 , can use two of its interfaces, Ethernet interface 104 and AirPort interface 106 , to communicate with other network nodes, in accordance with an embodiment of the present invention.
- the Ethernet interface 104 is connected to a router 204 , which enables the computer 102 to communicate with the Ethernet device 206 .
- the AirPort interface 106 enables the computer 102 to communicate with an AirPort device 208 .
- FIG. 2 although we omitted the USB interface 108 and the Firewire interface 110 , which were illustrated in FIG. 1 , it will be readily apparent to one skilled in the art that they could also be used for communicating with other network nodes.
- a computer 102 can be connected to multiple network nodes via its interfaces 104 and 106 . There is consequently a strong need to provide link-local IPv4 addressing across multiple interfaces 104 and 106 of the computer 102 to allow the interfaces 104 and 106 to be automatically configured by the computer 102 .
- FIG. 3 illustrates an ARP packet 300 that contains a number of pieces of information that can be used by a source network-node, such as a computer 102 , to resolve the IPv4 address of a target network-node, such as an AirPort device 208 , in accordance with an embodiment of the present invention.
- a source network-node such as a computer 102
- a target network-node such as an AirPort device 208
- ARP packet 300 contains a hardware family field 310 and the protocol family field 312 that specify the type of hardware and the type of protocol, respectively.
- ARP packet 300 also includes a hardware length field 314 and a protocol length field 316 that specify the sizes (in bytes) of the hardware addresses and the protocol addresses, respectively.
- ARP packet 300 contains an operation code 318 , which specifies whether the packet is an ARP-request packet or an ARP-reply packet.
- ARP packet 300 also contains four addresses, namely, the sender hardware address 320 , the sender protocol address 322 , the target hardware address 324 , and the target protocol address 326 , which are used for translating the IPv4 address of a target network-node into the corresponding hardware address.
- FIG. 4 presents a flow chart illustrating the process of providing link-local IPv4 addressing across multiple interfaces 104 , 106 , 108 , and 110 of a network node, such as a computer 102 , in accordance with an embodiment of the present invention.
- the computer 102 broadcasts an ARP-request packet on the multiple interfaces (step 402 ), such as Ethernet interface 104 and AirPort interface 106 , which asks for the hardware address of a target network-node whose link-local IPv4 address is Y. Note that, since the computer 102 broadcasts the ARP-request on multiple interfaces, the user is no longer constrained to use link-local addressing on only one of the interfaces.
- the computer 102 receives an ARP-reply packet (step 404 ) on Ethernet interface 104 from an Ethernet device 206 , whose link-local IPv4 address is Y, and whose hardware address is X.
- the computer 102 checks whether the IPv4 address Y is already in the ARP cache and associated with a different interface (step 406 ). If Y is not present in the ARP cache of the computer 102 , an entry is added to the ARP cache (step 410 ), which specifies that IP address Y is at the hardware address X on the Ethernet interface 104 .
- the computer 102 resolves the contention by choosing a winner interface (step 408 ) out of the two interfaces, Ethernet interface 104 and AirPort interface 106 .
- the computer 102 then checks whether the winner interface, Ethernet interface 104 , is different from the interface that is already in the ARP cache (step 412 ). If the winner interface, Ethernet interface 104 , is different from the interface that is already in the cache, AirPort interface 106 , then the computer updates the ARP cache (step 414 ) to specify that IP address Y is at the hardware address X on the winner interface, Ethernet interface 104 .
- the computer 102 sends one or more contention-resolution packets to the loser network-node (step 416 ), AirPort device 208 , which causes the loser network-node, AirPort device 208 , to choose another link-local IPv4 address for itself, thereby preventing address ambiguity.
- the contention-resolution packet can be an ARP-reply packet 300 , wherein the sender protocol-address 322 is equal to Y, and the sender hardware-address 320 is equal to X.
- the above-described embodiment of the present invention avoids address ambiguity.
- the above described embodiment can provide link-local IPv4 addressing across multiple interfaces. This allows the network nodes to automatically configure IPv4 addresses for their interfaces, thereby simplifying network-node configuration.
Abstract
Description
- 1. Field of the Invention
- The present invention relates to the process of configuring Internet Protocol version 4 (IPv4) addresses on a network node. More specifically, the present invention relates to a method and an apparatus for providing link-local IPv4 addressing across multiple interfaces of a network node.
- 2. Related Art
- The ever-increasing popularity of mobile computing and the proliferation of intelligent devices are necessitating network nodes, such as computers and printers, to support a plethora of interfaces. Moreover, network nodes are being enabled to support Internet Protocol version 4 (IPv4) over these various interfaces. For example, computers have recently started supporting IPv4-over-Universal Serial Bus (USB) and IPv4-over-Firewire. These and other developments have created a strong demand for mechanisms to facilitate automatic configuration of network nodes in an IPv4 network, thereby drastically simplifying the process of configuring network nodes.
- In order to participate in an IPv4 network, a network node, such as a computer or a printer, needs to be configured with IPv4 addresses for one or more of its interfaces. Additionally, in order to enable communication, the network node needs the ability to translate an IPv4 address into the corresponding hardware address. The Address Resolution Protocol (ARP) is a link-level protocol that solves the translation problem by providing an address-resolution mechanism that can be used to find the hardware address for a given IPv4 address, thereby enabling a network node to participate in an IPv4 network. IPv4 addresses can be configured either manually by the user, or automatically by the help of another network node, such as a DHCP server. Unfortunately, a DHCP server may not always be available. Moreover, it is cumbersome to have the user configure an IPv4 address. Therefore, there is a strong need for a mechanism by which a network node can automatically configure an IPv4 address on its own.
- Link-local IPv4 addressing provides such a mechanism. In link-local IPv4 addressing, a network node picks a random IPv4 address in a specified link-local address range and checks for its uniqueness within the scope of the link. If the address is already in use by another network node, then it picks another address and tries again. Once it finds a unique link-local IPv4 address, it uses it to communicate with other nodes in the network.
- Unfortunately, since link-local addresses are only guaranteed to be unique within the scope of a link, a source network-node typically configures only one interface out of all of its interfaces for link-local addressing, because otherwise, two target network-nodes that are connected on different interfaces of the source network-node may choose the same IPv4 address, thereby creating an address ambiguity. This is a severe limitation in today's networks, because while the number of interfaces in a network node continues to increase, the user is being forced to use link-local addressing on only one of the interfaces, thereby preventing the user from leveraging link-local IPv4 addressing to simplify network-node configuration.
- Hence, what is needed is a method and an apparatus that can provide link-local IPv4 addressing across multiple interfaces of a network node.
- One embodiment of the present invention provides a system for providing link-local IPv4 addressing across multiple interfaces of a source network-node. During system operation, the source network-node broadcasts an Address Resolution Protocol (ARP) request packet on multiple interfaces, wherein the ARP-request packet asks for the hardware address of a network node whose link-local IPv4 address is Y. Next, the source network-node receives an ARP-reply packet on interface Z1 from a target network-node whose link-local IPv4 address is Y and whose hardware address is X. If Y is not present in the ARP cache of the source network-node, an entry is added to the ARP cache, which specifies that IP address Y is at the hardware address X on interface Z1. Alternatively, if Y is already present in the ARP cache of the source network-node and is associated with a different interface Z2, the source network-node chooses a winner interface out of Z1 and Z2. If interface Z1 is chosen as the winner, the source network-node updates the ARP cache so that it specifies that IP address Y is at the hardware address X on interface Z1. Finally, the source network-node sends one or more contention-resolution packets on the loser interface to cause the loser network-node to choose another link-local IPv4 address for itself.
- In a variation on this embodiment, the interface can be an Ethernet interface, a USB interface, a Firewire interface, or an AirPort interface.
- In a variation on this embodiment, the address prefix for link-local IPv4 addresses can be 169.254/16.
- In a variation on this embodiment, the contention-resolution packets can be ARP packets.
- In a variation on this embodiment, the winner interface is chosen based on the speed of the interface.
- In a variation on this embodiment, sending one or more contention-resolution packets on the loser interface involves sending the packets directly to the loser network-node.
- In a variation on this embodiment, sending one or more contention-resolution packets on the loser interface involves broadcasting the packets on the loser interface.
- In a variation on this embodiment, the winner network-node and the loser network-node can be the same entity.
-
FIG. 1 illustrates a network node, such as a computer, with multiple interfaces, in accordance with an embodiment of the present invention. -
FIG. 2 illustrates how a network node, such as a computer, can use two of its interfaces to communicate with other network nodes, in accordance with an embodiment of the present invention. -
FIG. 3 illustrates an ARP packet that contains a number of pieces of information that can be used by a source network-node, such as a computer, to resolve the IPv4 address of a target network-node, such as an AirPort device, in accordance with an embodiment of the present invention. -
FIG. 4 presents a flow chart illustrating the process of providing link-local IPv4 addressing across multiple interfaces of a computer, in accordance with an embodiment of the present invention. - The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
- The data structures and code described in this detailed description are typically stored on a computer readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. This includes, but is not limited to, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs) and DVDs (digital versatile discs or digital video discs).
-
FIG. 1 illustrates a network node, such as acomputer 102, withmultiple interfaces - The
computer 102 illustrated inFIG. 1 has four interfaces, namely, Ethernetinterface 104, Airportinterface 106, USB interface 108, and Firewireinterface 110. An interface can generally include any type of communication component that enables a network node to communicate with another network node over a wire or wireless communication channel. Any of the fourinterfaces computer 102 to participate in an IPv4 network. For example, thecomputer 102 can use its Ethernetinterface 104 to participate in an IPv4-over-Ethernet local-area network. -
FIG. 2 illustrates how a network node, such as acomputer 102, can use two of its interfaces, Ethernetinterface 104 and AirPortinterface 106, to communicate with other network nodes, in accordance with an embodiment of the present invention. The Ethernetinterface 104 is connected to arouter 204, which enables thecomputer 102 to communicate with the Ethernetdevice 206. Similarly, the AirPortinterface 106 enables thecomputer 102 to communicate with an AirPortdevice 208. InFIG. 2 , although we omitted the USB interface 108 and the Firewireinterface 110, which were illustrated inFIG. 1 , it will be readily apparent to one skilled in the art that they could also be used for communicating with other network nodes. - It is evident from
FIG. 2 that acomputer 102 can be connected to multiple network nodes via itsinterfaces multiple interfaces computer 102 to allow theinterfaces computer 102. -
FIG. 3 illustrates anARP packet 300 that contains a number of pieces of information that can be used by a source network-node, such as acomputer 102, to resolve the IPv4 address of a target network-node, such as anAirPort device 208, in accordance with an embodiment of the present invention. - Specifically,
ARP packet 300 contains ahardware family field 310 and theprotocol family field 312 that specify the type of hardware and the type of protocol, respectively.ARP packet 300 also includes ahardware length field 314 and aprotocol length field 316 that specify the sizes (in bytes) of the hardware addresses and the protocol addresses, respectively. Additionally,ARP packet 300 contains anoperation code 318, which specifies whether the packet is an ARP-request packet or an ARP-reply packet. Furthermore,ARP packet 300 also contains four addresses, namely, thesender hardware address 320, thesender protocol address 322, thetarget hardware address 324, and thetarget protocol address 326, which are used for translating the IPv4 address of a target network-node into the corresponding hardware address. -
FIG. 4 presents a flow chart illustrating the process of providing link-local IPv4 addressing acrossmultiple interfaces computer 102, in accordance with an embodiment of the present invention. First, thecomputer 102 broadcasts an ARP-request packet on the multiple interfaces (step 402), such asEthernet interface 104 andAirPort interface 106, which asks for the hardware address of a target network-node whose link-local IPv4 address is Y. Note that, since thecomputer 102 broadcasts the ARP-request on multiple interfaces, the user is no longer constrained to use link-local addressing on only one of the interfaces. - Next, the
computer 102 receives an ARP-reply packet (step 404) onEthernet interface 104 from anEthernet device 206, whose link-local IPv4 address is Y, and whose hardware address is X. Next, thecomputer 102 checks whether the IPv4 address Y is already in the ARP cache and associated with a different interface (step 406). If Y is not present in the ARP cache of thecomputer 102, an entry is added to the ARP cache (step 410), which specifies that IP address Y is at the hardware address X on theEthernet interface 104. - On the other hand, if Y is already present in the ARP cache of the
computer 102, and is associated with a different interface, such asAirPort interface 106, thecomputer 102 resolves the contention by choosing a winner interface (step 408) out of the two interfaces,Ethernet interface 104 andAirPort interface 106. - Assuming that the
Ethernet interface 104 is chosen as the winner, thecomputer 102 then checks whether the winner interface,Ethernet interface 104, is different from the interface that is already in the ARP cache (step 412). If the winner interface,Ethernet interface 104, is different from the interface that is already in the cache,AirPort interface 106, then the computer updates the ARP cache (step 414) to specify that IP address Y is at the hardware address X on the winner interface,Ethernet interface 104. - Finally, the
computer 102 sends one or more contention-resolution packets to the loser network-node (step 416),AirPort device 208, which causes the loser network-node,AirPort device 208, to choose another link-local IPv4 address for itself, thereby preventing address ambiguity. Note that the contention-resolution packet can be an ARP-reply packet 300, wherein the sender protocol-address 322 is equal to Y, and the sender hardware-address 320 is equal to X. - Hence, by broadcasting the ARP-request packet on multiple interfaces,
Ethernet interface 104 andAirPort interface 106, and by sending one or more contention-resolution packets on the loser interface,AirPort interface 106, the above-described embodiment of the present invention avoids address ambiguity. In this way, the above described embodiment can provide link-local IPv4 addressing across multiple interfaces. This allows the network nodes to automatically configure IPv4 addresses for their interfaces, thereby simplifying network-node configuration. - The foregoing descriptions of embodiments of the present invention have been presented for purposes of illustration and description only. They are not intended to be exhaustive or to limit the present invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims.
Claims (33)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/257,266 US7974222B2 (en) | 2004-06-25 | 2008-10-23 | Method and apparatus for providing link-local IPv4 addressing across multiple interfaces of a network node |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/877,533 US7457255B2 (en) | 2004-06-25 | 2004-06-25 | Method and apparatus for providing link-local IPv4 addressing across multiple interfaces of a network node |
US12/257,266 US7974222B2 (en) | 2004-06-25 | 2008-10-23 | Method and apparatus for providing link-local IPv4 addressing across multiple interfaces of a network node |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/877,533 Continuation US7457255B2 (en) | 2004-06-25 | 2004-06-25 | Method and apparatus for providing link-local IPv4 addressing across multiple interfaces of a network node |
Publications (2)
Publication Number | Publication Date |
---|---|
US20090092063A1 true US20090092063A1 (en) | 2009-04-09 |
US7974222B2 US7974222B2 (en) | 2011-07-05 |
Family
ID=34960908
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/877,533 Active 2026-12-24 US7457255B2 (en) | 2004-06-25 | 2004-06-25 | Method and apparatus for providing link-local IPv4 addressing across multiple interfaces of a network node |
US12/257,266 Expired - Fee Related US7974222B2 (en) | 2004-06-25 | 2008-10-23 | Method and apparatus for providing link-local IPv4 addressing across multiple interfaces of a network node |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/877,533 Active 2026-12-24 US7457255B2 (en) | 2004-06-25 | 2004-06-25 | Method and apparatus for providing link-local IPv4 addressing across multiple interfaces of a network node |
Country Status (9)
Country | Link |
---|---|
US (2) | US7457255B2 (en) |
EP (1) | EP1766938B1 (en) |
JP (1) | JP4490479B2 (en) |
AT (1) | ATE417452T1 (en) |
AU (1) | AU2005267598B2 (en) |
CA (1) | CA2562984C (en) |
DE (1) | DE602005011622D1 (en) |
HK (1) | HK1102950A1 (en) |
WO (1) | WO2006011910A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110280175A1 (en) * | 2010-05-14 | 2011-11-17 | Buffalo Inc. | Wireless relay device |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7796614B1 (en) * | 2004-11-30 | 2010-09-14 | Symantec Corporation | Systems and methods for message proxying |
DE102006026482A1 (en) * | 2006-06-07 | 2007-12-13 | Siemens Ag | Method for communicating a non-network-capable device in a communication network |
US20080204789A1 (en) * | 2007-02-26 | 2008-08-28 | Hewlett-Packard Development Company, L.P. | Systems and Methods for Identifying Physically Proximate Printers |
US20130003600A1 (en) * | 2011-06-29 | 2013-01-03 | International Business Machines Corporation | Configuration of Interfaces Communicatively Coupled to Link-Local Zones in a Network |
US9430622B2 (en) * | 2011-07-13 | 2016-08-30 | Dell Products L.P. | Mini appliance |
US20130332586A1 (en) * | 2012-06-08 | 2013-12-12 | Apple Inc. | Providing ipv6 connectivity through shared external interfaces on electronic devices |
US8995443B2 (en) * | 2012-07-31 | 2015-03-31 | Qualcomm Incorporated | Address resolution mechanism for hybrid communication networks |
CN108259271A (en) * | 2018-02-01 | 2018-07-06 | 天津天地伟业信息系统集成有限公司 | A kind of method for detecting link state after more network card bindings by ARP |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4461902A (en) * | 1982-01-07 | 1984-07-24 | Takeda Chemical Industries, Ltd. | Thiazolidine derivatives and production thereof |
US5758282A (en) * | 1995-06-19 | 1998-05-26 | Sharp Kabushiki Kaisha | Radio terminal using allocated addresses |
US6334153B2 (en) * | 1997-10-14 | 2001-12-25 | Alacritech, Inc. | Passing a communication control block from host to a local device such that a message is processed on the device |
US20040083306A1 (en) * | 2002-10-24 | 2004-04-29 | International Business Machines Corporation | Method and apparatus for maintaining internet domain name data |
US6732165B1 (en) * | 2000-08-31 | 2004-05-04 | International Business Machines Corporation | Simultaneous network configuration of multiple headless machines |
US20040109460A1 (en) * | 1998-10-27 | 2004-06-10 | Hewlett-Packard Company | Method and apparatus for bridging between networks |
US20040213234A1 (en) * | 2002-05-09 | 2004-10-28 | Koch Christopher D. | Network address assignment in a passive optical network |
US6826611B1 (en) * | 2000-09-30 | 2004-11-30 | Fluke Corporation | Apparatus and method for automatically obtaining a valid IP configuration in a local area network |
US20040258074A1 (en) * | 2003-06-20 | 2004-12-23 | Williams Aidan Michael | Method and apparatus for allocating addresses in integrated zero-configured and manually configured networks |
US20040264503A1 (en) * | 2003-06-30 | 2004-12-30 | Microsoft Corporation | Method and system for providing a virtual protocol interlayer |
US20060114929A1 (en) * | 2002-12-19 | 2006-06-01 | Edwin Rijpkema | Contention resolution covering all ports of a data switch |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4661902A (en) | 1985-03-21 | 1987-04-28 | Apple Computer, Inc. | Local area network with carrier sense collision avoidance |
JPH06268650A (en) * | 1993-03-11 | 1994-09-22 | Toshiba Corp | Network repeater |
JPH11242642A (en) * | 1998-02-25 | 1999-09-07 | Matsushita Electric Ind Co Ltd | Device discovery processing method |
JP3534305B2 (en) * | 2000-02-29 | 2004-06-07 | 日本電気株式会社 | IP address duplication detection method using address resolution protocol |
US20030026230A1 (en) * | 2001-08-02 | 2003-02-06 | Juan-Antonio Ibanez | Proxy duplicate address detection for dynamic address allocation |
US7370093B2 (en) * | 2002-03-07 | 2008-05-06 | Brother Kogyo Kabushiki Kaisha | Electronic apparatus and system capable of assigning appropriate address |
US7532862B2 (en) * | 2002-03-19 | 2009-05-12 | Apple Inc. | Method and apparatus for configuring a wireless device through reverse advertising |
-
2004
- 2004-06-25 US US10/877,533 patent/US7457255B2/en active Active
-
2005
- 2005-02-10 CA CA2562984A patent/CA2562984C/en not_active Expired - Fee Related
- 2005-02-10 WO PCT/US2005/004306 patent/WO2006011910A1/en not_active Application Discontinuation
- 2005-02-10 JP JP2007508334A patent/JP4490479B2/en active Active
- 2005-02-10 AU AU2005267598A patent/AU2005267598B2/en not_active Ceased
- 2005-02-10 AT AT05713327T patent/ATE417452T1/en not_active IP Right Cessation
- 2005-02-10 EP EP05713327A patent/EP1766938B1/en active Active
- 2005-02-10 DE DE602005011622T patent/DE602005011622D1/en active Active
-
2007
- 2007-07-09 HK HK07107335.2A patent/HK1102950A1/en not_active IP Right Cessation
-
2008
- 2008-10-23 US US12/257,266 patent/US7974222B2/en not_active Expired - Fee Related
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4461902A (en) * | 1982-01-07 | 1984-07-24 | Takeda Chemical Industries, Ltd. | Thiazolidine derivatives and production thereof |
US5758282A (en) * | 1995-06-19 | 1998-05-26 | Sharp Kabushiki Kaisha | Radio terminal using allocated addresses |
US6334153B2 (en) * | 1997-10-14 | 2001-12-25 | Alacritech, Inc. | Passing a communication control block from host to a local device such that a message is processed on the device |
US20040109460A1 (en) * | 1998-10-27 | 2004-06-10 | Hewlett-Packard Company | Method and apparatus for bridging between networks |
US6732165B1 (en) * | 2000-08-31 | 2004-05-04 | International Business Machines Corporation | Simultaneous network configuration of multiple headless machines |
US6826611B1 (en) * | 2000-09-30 | 2004-11-30 | Fluke Corporation | Apparatus and method for automatically obtaining a valid IP configuration in a local area network |
US20040213234A1 (en) * | 2002-05-09 | 2004-10-28 | Koch Christopher D. | Network address assignment in a passive optical network |
US20040083306A1 (en) * | 2002-10-24 | 2004-04-29 | International Business Machines Corporation | Method and apparatus for maintaining internet domain name data |
US20060114929A1 (en) * | 2002-12-19 | 2006-06-01 | Edwin Rijpkema | Contention resolution covering all ports of a data switch |
US20040258074A1 (en) * | 2003-06-20 | 2004-12-23 | Williams Aidan Michael | Method and apparatus for allocating addresses in integrated zero-configured and manually configured networks |
US20040264503A1 (en) * | 2003-06-30 | 2004-12-30 | Microsoft Corporation | Method and system for providing a virtual protocol interlayer |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110280175A1 (en) * | 2010-05-14 | 2011-11-17 | Buffalo Inc. | Wireless relay device |
Also Published As
Publication number | Publication date |
---|---|
CA2562984C (en) | 2011-07-26 |
ATE417452T1 (en) | 2008-12-15 |
JP4490479B2 (en) | 2010-06-23 |
US20050286515A1 (en) | 2005-12-29 |
DE602005011622D1 (en) | 2009-01-22 |
EP1766938B1 (en) | 2008-12-10 |
AU2005267598A1 (en) | 2006-02-02 |
US7457255B2 (en) | 2008-11-25 |
CA2562984A1 (en) | 2006-02-02 |
HK1102950A1 (en) | 2007-12-07 |
WO2006011910A1 (en) | 2006-02-02 |
JP2007533259A (en) | 2007-11-15 |
EP1766938A1 (en) | 2007-03-28 |
US7974222B2 (en) | 2011-07-05 |
AU2005267598B2 (en) | 2008-10-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7974222B2 (en) | Method and apparatus for providing link-local IPv4 addressing across multiple interfaces of a network node | |
Cheshire et al. | Dynamic configuration of IPv4 link-local addresses | |
US7729292B2 (en) | Method and apparatus for detecting a router that improperly responds to ARP requests | |
Cheshire et al. | Multicast dns | |
CA2562889C (en) | Method and apparatus for looking up configuration information for a network node | |
KR100544395B1 (en) | Apparatus connected to network, storage medium and address determination method | |
US6061739A (en) | Network address assignment using physical address resolution protocols | |
KR100628493B1 (en) | Communication device | |
EP2267984B1 (en) | Address configuring method, apparatus and system | |
US20090052461A1 (en) | Method and Apparatus for Fibre Channel Over Ethernet Data Packet Translation Via Look up Table Conversion Bridge in a Network System | |
US20070047549A1 (en) | Dual-stack network apparatus and broadcasting method thereof | |
WO2000018049A1 (en) | System and method for providing a proxy farp for legacy storage devices | |
RU2540820C2 (en) | Packet forwarding method and switch | |
Cheshire et al. | Rfc 6762: Multicast dns | |
WO2007143833A1 (en) | System and method for handling address resolution protocol requests | |
Cheshire et al. | RFC 3927: Dynamic configuration of IPv4 link-local addresses | |
JP2005210265A (en) | Network system, terminal-setting method, address solution server, and client | |
US8516141B2 (en) | Method and system for modifying and/or changing a MAC ID utilizing an IPv6 network connection | |
CN107547286B (en) | Method and device for generating Address Resolution Protocol (ARP) table | |
US20070283332A1 (en) | Address allocation system and method | |
US11888648B1 (en) | Software-enabled access point (SoftAP) based bridging of devices in two wireless networks | |
US20090213851A1 (en) | Multiport device | |
US10742445B2 (en) | System for detecting loops in a pseudo-bridge | |
Guttman | Dynamic Configuration of IPv4 Link-Local Addresses Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the" Internet |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20230705 |