US11729140B2 - Method and system for managing DHCP servers - Google Patents

Method and system for managing DHCP servers Download PDF

Info

Publication number
US11729140B2
US11729140B2 US17/416,000 US201917416000A US11729140B2 US 11729140 B2 US11729140 B2 US 11729140B2 US 201917416000 A US201917416000 A US 201917416000A US 11729140 B2 US11729140 B2 US 11729140B2
Authority
US
United States
Prior art keywords
dhcp server
node
wireless communication
new device
backup
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.)
Active
Application number
US17/416,000
Other languages
English (en)
Other versions
US20220078160A1 (en
Inventor
Mathieu COLLIAUX
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sagemcom Broadband SAS
Original Assignee
Sagemcom Broadband SAS
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 Sagemcom Broadband SAS filed Critical Sagemcom Broadband SAS
Assigned to SAGEMCOM BROADBAND SAS reassignment SAGEMCOM BROADBAND SAS ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: COLLIAUX, Mathieu
Publication of US20220078160A1 publication Critical patent/US20220078160A1/en
Application granted granted Critical
Publication of US11729140B2 publication Critical patent/US11729140B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/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/5053—Lease time; Renewal aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • the present invention relates to a DHCP (“Dynamic Host Configuration Protocol” as defined by the normative document RFC 1531, amended and supplemented by the normative documents RFC 1534, RFC 2131 and RFC 2132) management method and system intended for avoiding conflicts in IP (Internet Protocol as defined by the normative document RFC 791) addresses.
  • DHCP Dynamic Host Configuration Protocol
  • a local area network LAN based on a dynamic distribution of IP addresses must include a unique DHCP server.
  • This unique DHCP server may in this case be a DHCP relay agent that serves as a proxy for another DHCP server that is located on another network connected to said local area network LAN by means of a router.
  • the DHCP server provides leases to each requesting device of the local area network LAN, each lease indicating at least an IP address that must be used by the requesting equipment for communicating, as well as a duration of validity of the lease.
  • the DHCP server may also supply router IP address information and/or information on an IP address of at least one DNS (Domain Name System as defined in the normative document RFC 6895) server.
  • DNS Domain Name System as defined in the normative document RFC 6895
  • the DHCP server forms part of a set of functionalities integrated in the gateways GW for access to the internet, and is therefore visible to any device connected to the local area network LAN.
  • systems for extending wireless communication coverage may be used in order to increase the range of these local area networks LAN by coordinating a plurality of distributed access points AP.
  • These various access points AP are integrated in interconnected nodes by means of a backhaul subnetwork and all make available a same wireless local area network WLAN.
  • all these access points AP thus use the same SSID (Service Set IDentifier) and the same password (also referred to as a security key).
  • SSID Service Set IDentifier
  • password also referred to as a security key
  • the wireless communication coverage extension system is thus typically connected to the internet through the gateway GW, for example by means of an Ethernet cord providing the connection of a main node of the wireless communication coverage extension system to the gateway.
  • the wireless communication coverage extension system then serves as a relay between the gateway and each device connected by a cable or wireless link to the local area network LAN, and also serves as a relay between these various devices connected to the local area network LAN to enable them to communicate with each other.
  • the nodes of the backhaul subnetwork are connected to each other, a node then being able to serve as a relay between two other nodes of the backhaul subnetwork.
  • the nodes are thus interconnected by means of cable connections, for example of the Ethernet type, or wireless connections, for example a Wi-Fi (registered trade mark) connection using an SSID identifier different from said local area network WLAN itself.
  • the nodes of the backhaul subnetwork thus communicate with each other by means of logic links, for example IP communications or encrypted tunnels or communications in accordance with a proprietary communication protocol. These logic links are typically established by means of probe and discovery messages.
  • the nodes of the backhaul subnetwork are typically coordinated in a centralised manner, by a master node among said nodes of the backhaul subnetwork.
  • the master node may be designated by fixed configuration or dynamically by election.
  • the master node may be the node of the backhaul subnetwork that is directly connected to the internet access gateway GW. All the nodes of the backhaul subnetwork thus have knowledge of the master node and are capable of identifying it by means of its MAC (Medium Access Control) address.
  • MAC Medium Access Control
  • Any communication within a network being regulated through IP addresses attributed to the devices connected to the local area network LAN it is desirable to provide a solution that makes it possible to maintain the DHCP server function within the local area network LAN while avoiding addressing conflicts. It is in particular desirable to avoid these addressing conflicts when the link with the DHCP server is restored. These addressing conflicts are also to be avoided when this DHCP server is connected elsewhere in the local area network LAN. These addressing conflicts are also to be avoided when this DHCP server is replaced by another DHCP server. It is also desirable to avoid these addressing conflicts when a plurality of DHCP servers are connected to the wireless communication coverage extension system. It is also desirable to provide a solution that is simple, effective and low cost.
  • the patent document US 2014/0325040 A1 is also known, which discloses a solution for duplicating the information from a main DHCP server to a backup DHCP server.
  • the backup DHCP server can thus take over in the event of disconnection of the main DHCP by using information thus duplicated.
  • One object of the present invention is to propose a method for managing IP address leases in a wireless communication coverage extension system comprising a backhaul subnetwork comprising a set of interconnected nodes, a plurality of nodes of the backhaul subnetwork implementing an access point functionality of a same wireless communication network.
  • the wireless communication coverage extension system being adapted for making it possible to connect devices to said nodes by means of the wireless communication network or by cable.
  • the method comprises the following steps:
  • the method comprises the following steps, by each said node: cancelling its own IP address lease; restarting any communication interface of said node that is not used for creating the backhaul subnetwork.
  • the method comprises the following steps:
  • connection node in the case where the second monitoring shows a connection of a new device to a said node, referred to as connection node:
  • the logic barrier there is no conflict of IP addresses at the connection of the main DHCP server.
  • the general disconnection that follows the return of the main DHCP server the addressing implemented by the main DHCP server in replacement for the backup DHCP server is coherent from the point of view of any said node or of any device connected to the wireless communication coverage extension system.
  • the method comprises the following steps: notifying said nodes that the wireless communication coverage extension system is in normal operational mode when the main DHCP server is active; and notifying said nodes that the wireless communication coverage extension system is in backup operational mode when the backup DHCP server is active.
  • each said node can have a distinct second monitoring behaviour according to the operational mode in which the wireless communication coverage extension system is situated.
  • the method comprises the following steps:
  • connection node in the case where the second monitoring shows a connection of a new device to a said node, referred to as connection node:
  • the logic barrier there is no conflict of IP addresses at the connection of the main DHCP server.
  • the general disconnection that follows the return of the main DHCP server the addressing implemented by the main DHCP server in replacement for the backup DHCP server is coherent from the point of view of any said node or of any device connected to the wireless communication coverage extension system.
  • the supplementary logic barrier the potential conflicts of IP addresses that would be caused by the entry of another DHCP server that would come to interfere with the main DHCP server are avoided.
  • the new device is probed by sending a DHCP Discover request and the new device includes a DHCP server when a DHCP Offer response is received in response to the DHCP Discover request.
  • the logic barrier is implemented by a firewall of the connection node configured for dropping any DHCP Offer response coming from the backhaul subnetwork and intended for the reconnection node.
  • the backup DHCP server is activated in the node to which the main DHCP server was connected before disconnection.
  • the invention also relates to a computer program that can be stored on a medium and/or downloaded from a communication network, in order to be read by a processor.
  • This computer program comprises instructions for implementing one or other of the methods mentioned above in any one of the embodiments thereof, when said program is executed by the processor.
  • the invention also relates to an information storage medium storing such a computer program.
  • the invention also relates to a wireless communication coverage extension system comprising a backhaul subnetwork comprising a set of interconnected nodes, a plurality of nodes of the backhaul subnetwork implementing an access point functionality of the same wireless communication network.
  • the wireless communication coverage extension system being adapted for making it possible to connect devices to said nodes by means of the wireless communication network or by cable.
  • the wireless communication coverage extension system comprises:
  • the invention also relates to a node, called the master node, intended to be used in a wireless communication coverage extension system comprising a backhaul subnetwork comprising a set of interconnected nodes including the master node, a plurality of nodes of the backhaul subnetwork implementing an access point functionality of a same wireless communication network, the wireless communication coverage extension system being adapted for making it possible to connect devices to said nodes by means of the wireless communication network or by cable.
  • the master node comprises:
  • FIG. 1 illustrates schematically a communication system wherein the present invention can be implemented
  • FIG. 2 illustrates schematically a master node in a backhaul subnetwork of the communication system in FIG. 1 ;
  • FIG. 3 illustrates schematically an example of hardware arrangement of nodes of the backhaul subnetwork
  • FIG. 4 illustrates schematically an algorithm for activating a backup DHCP server in the master node
  • FIG. 5 illustrates schematically the communication system at the time of a reconnection of a main DHCP server
  • FIG. 6 illustrates schematically a configuration of a node of the backhaul subnetwork when the backup DHCP server is activated
  • FIG. 7 illustrates schematically an algorithm for deactivating the backup DHCP server in a particular embodiment
  • FIG. 8 illustrates schematically the communication system when a conflicting DHCP server is connected
  • FIG. 9 illustrates schematically an algorithm for deactivating the backup DHCP server in another particular embodiment.
  • FIG. 1 illustrates schematically a communication system wherein the present invention can be implemented.
  • the communication system comprises a wireless communication coverage extension system constructed around a backhaul subnetwork comprising a set of interconnected nodes N 1 121 , N 2 122 , N 3 123 , N 4 124 .
  • Each node in a plurality of nodes in the backhaul subnetwork typically all the nodes in the backhaul subnetwork, implements an access point AP functionality of a wireless local area network WLAN.
  • the nodes in said plurality of nodes all make available the same wireless local area network WLAN (same name, etc.).
  • Wi-Fi registered trade mark
  • all these access points AP thus use the same SSID identifier and the same password.
  • the coverage area of the wireless local area network WLAN and therefore in general terms of the local area network LAN thus formed around the wireless communication coverage extension system, is then extended in a way that is transparent for each terminal, or station, that connects thereto.
  • the nodes N 1 121 , N 2 122 , N 3 123 , N 4 124 of the backhaul subnetwork are connected to each other (e.g. by means of a structure in tree form or a mesh structure), a node then being able to serve as a relay between two other nodes of the backhaul subnetwork.
  • the nodes N 1 121 , N 2 122 , N 3 123 , N 4 124 are thus interconnected by means of cable connections, for example of the Ethernet type, or wireless connections, for example a Wi-Fi (registered trade mark) connection using an SSID identifier different from said local area network WLAN itself.
  • the nodes N 1 121 , N 2 122 , N 3 123 , N 4 124 of the backhaul subnetwork thus communicate with each other by means of logic links, for example IP communications or encrypted tunnels or communications in accordance with a proprietary communication protocol.
  • FIG. 1 shows that the node N 1 121 is connected to the node N 2 122 and to the node N 3 123 by means of a wireless connection, and the node N 4 124 is connected to the node N 3 123 by means of a cable connection.
  • the wireless communication coverage extension system thus makes it possible to interconnect a gateway GW 110 for access to the internet, a terminal T 1 141 , a terminal T 2 142 , a terminal T 3 143 and a terminal T 4 144 .
  • the gateway GW 110 implements a DHCP server functionality 111 , here referred to as the main DHCP server.
  • the terminal T 1 141 is for example a smartphone connected by a wireless connection to the node N 2 122 , that is to say the terminal T 1 141 is thus connected via the wireless local area network WLAN by means of the node N 2 122 acting as an access point AP.
  • the terminal T 2 142 is for example a television set connected by a cable connection to the node N 2 122 .
  • the terminal T 3 143 is for example a tablet connected by a wireless connection to the node N 4 124 , that is to say the terminal T 3 143 is thus connected via the wireless local area network WLAN by means of the node N 4 124 acting as an access point AP.
  • the terminal T 4 144 is for example a network-attached storage unit NAS connected by a wireless connection to the node N 3 123 , that is to say the terminal T 4 144 is thus connected via the wireless local area network WLAN by means of the node N 3 123 acting as an access point AP.
  • the nodes of the backhaul subnetwork are coordinated in a centralised manner, by a master node among said nodes of the backhaul subnetwork.
  • the master node can be designated by fixed configuration or dynamically by election.
  • the master node is for example the node of the backhaul subnetwork that is directly connected to the gateway GW for access to the internet, namely the node N 1 121 in the context of FIG. 1 . All the nodes of the backhaul subnetwork thus have knowledge of the master node, and are capable of identifying it by means of its MAC address.
  • the master node N 1 121 implements a disengageable functionality of the backup DHCP server 200 in order to manage the IP address leases in the event of disconnection of the main DHCP server.
  • the backup DHCP server is thus selectively activated when the main DHCP server is disconnected from the wireless communication coverage extension system.
  • FIG. 3 illustrates schematically an example of hardware architecture of any node 300 of the backhaul subnetwork.
  • the example of hardware architecture presented comprises, connected by a communication bus 310 : a processor CPU (central processing unit) 301 ; a random access memory RAM 302 , a read only memory ROM 303 or a flash memory; a storage unit or a storage medium reader, such as an SD (Secure Digital) card reader 304 or a hard disk HDD (hard disk drive); and at least one set of communication interfaces COM 305 .
  • the set of communication interfaces COM 305 makes it possible to implement the access point functionality AP for extending the coverage of the wireless local area network WLAN, to connect terminals or the gateway GW 110 by cable and to establish the backhaul subnetwork.
  • the processor CPU 301 is capable of executing instructions loaded in the RAM memory 302 from the ROM memory 303 , from an external memory (such as an SD card), from a storage medium (such as the hard disk HDD), or from a communication network. On powering up, the processor CPU 301 is capable of reading instructions from the RAM memory 302 and executing them. These instructions form a computer program causing the implementation, by the processor CPU 301 , of all or some of the algorithms and steps described hereinafter.
  • nodes N 1 121 , N 2 122 , N 3 123 , N 4 124 comprise electronic circuitry adapted and configured for implementing the algorithms and steps described hereinafter.
  • FIG. 4 illustrates schematically an algorithm for activating the backup DHCP server 200 in the master node.
  • the node to which the main DHCP server 111 is connected i.e. the node N 1 121 in FIG. 1 , monitors whether the main DHCP server 111 is or is not still connected to the wireless communication coverage extension system.
  • the main DHCP server 111 may be present in a device connected by cable, or by wireless via the wireless local area network WLAN, to the wireless communication coverage extension system.
  • the node N 1 121 can simply monitor whether or not the gateway GW 110 is still connected to the wireless communication coverage extension system.
  • NETLINK events can be used to implement this monitoring, in particular the event RTMGRP_LINK that takes the state UP or DOWN according to the physical state of the connection in question.
  • Each of the changes in state of the physical connection instantaneously generates a corresponding NETLINK event, which enables the node N 1 121 to detect that the gateway GW 110 has been disconnected.
  • a step 402 the node N 1 121 checks whether the main DHCP server 111 is still connected to the wireless communication coverage extension system. If such is the case, the step 401 is repeated; otherwise a step 403 is performed.
  • the node N 1 121 activates the backup DHCP server 200 .
  • this other node informs the master node that the main DHCP server 111 has been disconnected so that the master node can activate the backup DHCP server 200 in response to the disconnection of the main DHCP server 111 .
  • the master node i.e. the one that implements the backup DHCP server 200
  • the master node is preferentially the node of the wireless communication coverage extension system that is connected to the main DHCP server 111 , but may also in a variant be another node of the wireless communication coverage extension system.
  • the master node notifies the other nodes of the wireless communication coverage extension system that the backup DHCP server 200 has been activated. All the nodes then note that the backup DHCP server 200 has been activated (entry to backup operational mode).
  • a step 405 the master node instructs the other nodes of the wireless communication coverage extension system to implement a general disconnection of the local area network LAN. It should be noted that the steps 404 and 405 can be performed in a single step wherein the master node sends a message requesting general disconnection of the local area network LAN that includes supplementary information indicating that the backup DHCP server 200 has been activated (entry to backup operational mode).
  • each of the nodes of the wireless communication coverage extension system :
  • Restarting these interfaces forces the devices that were connected thereto to reconnect and to request a lease renewal in order to obtain an IP address in conformity with the policy for attributing IP addresses by the DHCP server in place (in this case, at this moment, the backup DHCP server 200 ).
  • the master node or more particularly the backup DHCP server 200 , renews the leases for all the devices connected to the LAN network (including the nodes of the wireless communication coverage extension system).
  • the backup DHCP server 200 processes the DHCP requests that come from the various devices of the local area network LAN, including those coming from the nodes of the wireless communication coverage extension system.
  • a complete renewal of the IP addresses of the local area network LAN is therefore implemented, which avoids any conflict of IP address with the IP address attribution policy previously established by the main DHCP server 111 .
  • FIG. 5 illustrates schematically the communication system when a main DHCP server 111 is reconnected.
  • the gateway GW 110 that includes the main DHCP server 111 is reconnected to the node N 1 121 .
  • the gateway GW 110 may in a variant be reconnected to another node of the wireless communication coverage extension system.
  • a device other than the gateway GW 110 is connected to the wireless communication coverage extension system, this other device including a DHCP server that is also not disengageable (as is the case with the DHCP server 111 of the gateway GW 110 ).
  • each node implements a monitoring mechanism MON 610 and a firewall FW 600 , as illustrated in FIG. 6 .
  • the monitoring mechanism MON 610 monitors, on any communication interface that is not being used for creating the backhaul subnetwork, any appearance of a new device.
  • protective measures are taken by means of a particular configuration of the firewall 600 , in order to create a logic barrier avoiding IP address conflicts. This aspect is detailed hereinafter.
  • FIG. 7 illustrates schematically an algorithm for deactivating the backup DHCP server 200 , in a particular embodiment.
  • each node of the wireless communication coverage extension system monitors whether a new device is connected thereto, whether by means of a wireless connection or by means of a cable connection. For example, as already indicated, when the nodes are based on a Linux operating system, NETLINK events can be used for implementing this monitoring.
  • each node checks whether a new device is connected thereto. If such is the case, a step 703 is performed; otherwise the step 701 is repeated.
  • the node that detected the connection of a new device to one of its interfaces that is not being used for creating the backhaul subnetwork activates a logic barrier vis-à-vis the backup DHCP server 200 .
  • the logic barrier isolates the monitoring mechanism MON 610 of the node in question vis-à-vis the backup server DHCP 200 to make it possible to probe a possible presence of a DHCP server in the newly connected device without the monitoring mechanism MON 610 suffering any interference on the part of the backup DHCP server 200 .
  • the logic barrier rejects any “DHCP Offer” response transmitted via the UDP (User Datagram Protocol as defined in the normative document RFC 768), coming from the backhaul subnetwork and intended for the node that activated said logic barrier. Consequently the monitoring mechanism MON 610 does not suffer any interference on the part of the backup DHCP server 200 .
  • the firewall FW 600 is configured to implement a dropping of any “DHCP Offer” response coming from the backhaul subnetwork and intended for the node that activated said logic barrier (INPUT clause of the firewall FR 600 ).
  • the logic barrier furthermore isolates the newly connected device with respect to the backup DHCP server 200 , to enable the monitoring mechanism MON 610 to probe the possible presence of a DHCP server in the newly connected device without the newly connected device suffering any interference on the part of the backup DHCP server 200 .
  • the logic barrier rejects any “DHCP Offer” response coming from the backhaul subnetwork and passing through the node that activated said logic barrier.
  • the firewall FW 600 is considered to implement a dropping of any “DHCP Offer” response coming from the backhaul subnetwork and passing through the node that activated said logic barrier (THROUGH clause of the firewall).
  • the monitoring mechanism MON 610 of the node that detected the connection of the new device performs a DHCP test with said new device.
  • the monitoring mechanism MON 610 probes the new device to determine whether said new device includes a DHCP server.
  • the monitoring mechanism MON 610 broadcasts a DHCP Discover request. This request is thus received by all the devices connected to the local network LAN, including the master node and therefore the backup DHCP server 200 .
  • Each DHCP server present in the local area network LAN then transmits, in unicast mode, to the node that detected the connection of the new device, a DHCP Offer response in return.
  • the response of the backup DHCP server 200 is then blocked by the logic barrier activated at the step 703 . If the newly connected device includes a DHCP server, the monitoring mechanism MON 610 then receives the “DHCP Offer” response coming from this incorporated DHCP server. Otherwise, without any response after the expiry of a time delay of predefined duration, the monitoring mechanism MON 610 considers that the newly connected device does not include a DHCP server.
  • a step 705 the monitoring mechanism MON 610 checks whether the test performed at the step 704 concludes that the newly connected device includes a DHCP server. If such is the case, the backup DHCP server 200 must give way to the DHCP server thus introduced (or reintroduced) in the local area network LAN, and a step 708 is performed; otherwise a step 706 is performed.
  • the node that detected the connection of the new device at one of the interfaces thereof that is not being used for creating the backhaul subnetwork deactivates the logic barrier that had been established at the step 703 .
  • a step 707 the node accepts the new device in the local area network LAN, and the algorithm in FIG. 7 is ended.
  • the master node deactivates the backup DHCP server 200 . Otherwise the node in question informs the master node that a DHCP server, to be considered henceforth as the main DHCP server, has been connected; then the master deactivates the backup DHCP server 200 .
  • a step 709 the node that detected the connection of the new device to one of the interfaces thereof that is not being used for creating the backhaul subnetwork deactivates the logic barrier that had been established at the step 703 .
  • the node in question accepts the new device in the local area network LAN.
  • the master node notifies the other nodes of the wireless communication coverage extension system that the backup DHCP server 200 has been deactivated. All the nodes then note that the backup DHCP server 200 has been deactivated (return to normal operational mode). The fact that each node knows in which operational mode the wireless communication coverage extension system is situated makes it possible to activate the monitoring mechanism MON 610 solely in backup operational mode.
  • a step 712 the master node instructs the other nodes of the wireless communication coverage extension system to perform a general disconnection of the local area network LAN.
  • the steps 711 and 712 may be performed in a single step wherein the master node sends a message requesting general disconnection of the local area network LAN that includes supplementary information indicating that the backup DHCP server 200 has been deactivated (return to normal operational mode).
  • each of the nodes of the wireless communication coverage extension system proceeds as already described in relation to FIG. 4 .
  • the main DHCP server implements lease renewals for all the devices connected to the LAN network (including the nodes of the wireless communication coverage extension system).
  • the main DHCP server processes the DHCP requests that come from the various devices of the local area network LAN, including those coming from the nodes of the wireless communication coverage extension system.
  • a complete renewal of the IP addresses of the local area network LAN is therefore implemented, which avoids any IP address conflict with the IP address attribution policy previously established by the backup DHCP server 200 .
  • the wireless communication coverage extension system is able to manage conflicts of any non-disengageable DHCP servers that are connected thereto.
  • FIG. 8 illustrates schematically the communication system when a conflicting DHCP server is connected while the main DHCP server 111 is already active.
  • the conflicting DHCP server 810 is included in a device DEV 800 that is connected to the node N 4 124 .
  • the device DEV 800 may be connected by cable connection or wireless connection.
  • FIG. 9 illustrates schematically an algorithm for deactivating the backup DHCP server 200 in a particular embodiment relating to FIG. 8 . It should be noted that, in this context, when there is any activation of the backup DHCP server 200 , the step 404 is not optional. Each node of the wireless communication coverage extension system must know which operational mode is current.
  • each node of the wireless communication coverage extension system monitors whether a new device is connected to it, whether by means of a wireless connection or by means of a cable connection. For example, as already indicated, when the nodes are based on a Linux operating system, NETLINK events may be used for implementing this monitoring.
  • each node checks whether a new device is connected thereto. If such is the case, a step 903 is performed; otherwise the step 901 is repeated.
  • the node that detected the connection of a new device to one of the interfaces thereof that is not being used for creating the backhaul subnetwork activates a logic barrier with respect to the active DHCP server, whether this be the backup DHCP server 200 or the main DHCP server 111 .
  • the logic barrier in question corresponds to that of the step 703 already described.
  • the node in question determines whether the active DHCP server is the main DHCP server 111 or the backup DHCP server 200 . In other words, the node in question determines whether the wireless communication coverage extension system is in normal operational mode or in backup operational mode. In normal operational mode, a step 905 is performed; in backup operational mode, a step 906 is performed.
  • the node in question activates a supplementary logic barrier for preventing any DHCP message that could be sent by the newly connected device to use the backhaul subnetwork.
  • the supplementary logic barrier isolates the backhaul subnetwork with respect to the newly connected device, so that only the monitoring mechanism MON 610 can receive any DHCP messages coming from said newly connected device.
  • the firewall FW 600 is configured to implement a dropping of any DHCP message coming from the newly connected device and intended to be propagated via the backhaul subnetwork (THROUGH clause of the firewall FW 600 ). Then the step 906 is performed.
  • a step 906 the monitoring mechanism MON 610 of the node that has detected the connection of the new device performs a DHCP test with said new device.
  • the monitoring mechanism MON 610 probes the new device to determine whether said new device includes a DHCP server, as already described in relation to the step 704 .
  • a step 907 the monitoring mechanism MON 610 checks whether the test performed at the step 906 concludes that the newly connected device includes a DHCP server. If such is the case, a step 910 is performed; otherwise a step 908 is performed.
  • the node in question deactivates the logic barrier that was established at the step 903 , as well as the supplementary logic barrier that was optionally established at the step 905 .
  • a step 909 the node in question accepts the new device in the local area network LAN, and the algorithm of FIG. 9 is ended.
  • the node in question determines whether the active DHCP server is the main DHCP server 111 or the backup DHCP server 200 , as at the step 904 .
  • a step 911 is performed; in backup operational mode, a step 912 is performed.
  • the node in question maintains the isolation of the DHCP server of the newly connected device to prevent any IP address conflicts with the main DHCP server 111 , and this until the newly connected device is disconnected.
  • the node in question deactivates the logic barrier that was established at the step 903 , as well as the supplementary logic barrier that was established at the step 905 ; then the algorithm in FIG. 9 is ended.
  • the backup DHCP server 200 must give way to the DHCP server thus introduced (or reintroduced) in the local area network LAN, which then becomes the main DHCP server. Consequently, if the node that detected the connection of the new device to one of the interfaces thereof that is not being used for creating the backhaul subnetwork is the master node, the master node deactivates the backup DHCP server 200 . Otherwise the node in question informs the master node that a DHCP server, to be considered henceforth as the main DHCP server, has been connected; then the master node deactivates the backup DHCP server 200 .
  • a step 913 the node that detected the connection of the new device at one of the interfaces thereof that is not being used for creating the backhaul subnetwork deactivates the logic barrier that had been established at the step 903 .
  • the node in question accepts the new device in the local area network LAN.
  • the master node notifies the other nodes of the wireless communication coverage extension system that the backup DHCP server 200 has been deactivated. All the nodes then note that the backup DHCP server 200 has been deactivated (return to normal operational mode).
  • the fact that each node knows in which operational mode the wireless communication coverage extension system is situated makes it possible to determine whether or not it is necessary to activate the supplementary logic barrier and, in the case of the introduction of a new device including a DHCP server, to determine whether the latter must be maintained in isolation or adopt the role of main DHCP server. It should be noted that, in the embodiment in FIGS. 8 and 9 , the monitoring mechanism MON 610 is permanently activated.
  • a step 916 the master node instructs the other nodes of the wireless communication coverage extension system to implement a general disconnection of the local area network LAN.
  • the steps 915 and 916 may be performed in a single step wherein the master node sends a message requesting general disconnection of the local area network LAN that includes supplementary information indicating that the backup DHCP server 200 has been deactivated (return to normal operational mode).
  • each of the nodes of the wireless communication coverage extension system proceeds as already described in relation to FIG. 4 .
  • the main DHCP server implements lease renewals for all the devices connected to the LAN network (including the nodes of the wireless communication coverage extension system).
  • the main DHCP server processes the DHCP requests that come from the various devices of the local area network LAN, including those coming from the nodes of the wireless communication coverage extension system.
  • a complete renewal of the IP addresses of the local area network LAN is then implemented, which avoids any IP address conflict with the IP address attribution policy previously established by the backup DHCP server 200 .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
US17/416,000 2018-12-20 2019-12-19 Method and system for managing DHCP servers Active US11729140B2 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
FR1873530 2018-12-20
FR1873530A FR3091128B1 (fr) 2018-12-20 2018-12-20 Procédé et système de gestion de serveurs dhcp
PCT/EP2019/086231 WO2020127680A1 (fr) 2018-12-20 2019-12-19 Procede et systeme de gestion de serveurs dhcp

Publications (2)

Publication Number Publication Date
US20220078160A1 US20220078160A1 (en) 2022-03-10
US11729140B2 true US11729140B2 (en) 2023-08-15

Family

ID=66776473

Family Applications (1)

Application Number Title Priority Date Filing Date
US17/416,000 Active US11729140B2 (en) 2018-12-20 2019-12-19 Method and system for managing DHCP servers

Country Status (4)

Country Link
US (1) US11729140B2 (de)
EP (1) EP3881523B1 (de)
FR (1) FR3091128B1 (de)
WO (1) WO2020127680A1 (de)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210400015A1 (en) * 2019-01-17 2021-12-23 Hewlett Packard Enterprise Development Lp Short-term lease allocation for network address conflict reduction in dhcp failover deployments

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060155833A1 (en) * 1998-11-12 2006-07-13 Toru Matsuda Method and apparatus for automatic network configuration
US20060218252A1 (en) * 2005-03-22 2006-09-28 Cisco Technology, Inc., A Corporation Of California Remote survivable DHCP for a DHCP relay agent
US20070140239A1 (en) * 2005-12-21 2007-06-21 Packethop, Inc. Distributed services for mesh networks
US20080267259A1 (en) * 2007-04-30 2008-10-30 Honeywell International Inc. Apparatus and method for intelligent frequency-hopping discovery and synchronization
US20130166706A1 (en) * 2011-12-22 2013-06-27 International Business Machines Corporation Extending a dhcp relay to backup a dhcp server
US20140173124A1 (en) * 2012-12-19 2014-06-19 Krishnapillai Velayudhapillai Method and System for Causing a Client Device to Renew a Dynamic IP Address
US20160112370A1 (en) * 2014-10-17 2016-04-21 Aruba Networks, Inc. Method and system for causing client to renew dynamic host configuration protocol internet protocol address based on link local addresses
US20160219502A1 (en) 2015-01-28 2016-07-28 Distech Controls Inc Environment control device (ecd) and method for configuring the ecd to operate a wi-fi communication interface
US20160261457A1 (en) * 2015-03-03 2016-09-08 Qualcomm Incorporated Recovering from connectivity failure at a bridging device
US20170163597A1 (en) * 2015-12-05 2017-06-08 Aruba Networks, Inc. Ip address of wireless client device
US20200412690A1 (en) * 2018-02-26 2020-12-31 Nippon Telegraph And Telephone Corporation Communication device, communication method and program

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9300627B2 (en) 2013-03-14 2016-03-29 Time Warner Cable Enterprises Llc System and method for automatic routing of dynamic host configuration protocol (DHCP) traffic
US9413610B2 (en) 2013-04-24 2016-08-09 Ciena Corporation Network-based DHCP server recovery

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060155833A1 (en) * 1998-11-12 2006-07-13 Toru Matsuda Method and apparatus for automatic network configuration
US20060218252A1 (en) * 2005-03-22 2006-09-28 Cisco Technology, Inc., A Corporation Of California Remote survivable DHCP for a DHCP relay agent
US20070140239A1 (en) * 2005-12-21 2007-06-21 Packethop, Inc. Distributed services for mesh networks
US20080267259A1 (en) * 2007-04-30 2008-10-30 Honeywell International Inc. Apparatus and method for intelligent frequency-hopping discovery and synchronization
US20130166706A1 (en) * 2011-12-22 2013-06-27 International Business Machines Corporation Extending a dhcp relay to backup a dhcp server
US20140173124A1 (en) * 2012-12-19 2014-06-19 Krishnapillai Velayudhapillai Method and System for Causing a Client Device to Renew a Dynamic IP Address
US20160112370A1 (en) * 2014-10-17 2016-04-21 Aruba Networks, Inc. Method and system for causing client to renew dynamic host configuration protocol internet protocol address based on link local addresses
US20160219502A1 (en) 2015-01-28 2016-07-28 Distech Controls Inc Environment control device (ecd) and method for configuring the ecd to operate a wi-fi communication interface
US20160261457A1 (en) * 2015-03-03 2016-09-08 Qualcomm Incorporated Recovering from connectivity failure at a bridging device
US20170163597A1 (en) * 2015-12-05 2017-06-08 Aruba Networks, Inc. Ip address of wireless client device
US20200412690A1 (en) * 2018-02-26 2020-12-31 Nippon Telegraph And Telephone Corporation Communication device, communication method and program

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
Bernard; "The Mini-DHCP Derver: draft-aboba-dhc-mini-04.txt" Interent Engineering Task Force IEIF; Standard Working Draft, Internet Society; No. 4; pp. 1 (line 1); pp. 6 (last line); Sep. 29, 2001.
Droms et al; "DHCP Failover Protocal" pp. 1-133; Mar. 1, 2003.
Feb. 20, 2020 International Search Report issued in International Patent Application No. PCT/EP2019/086231.
Lin, Changsheng, Tian Su, and Zhiqian Wang. "Summary of high-availability DHCP service solutions." 2011 4th IEEE International Conference on Broadband Network and Multimedia Technology. IEEE, 2011. (Year: 2011). *
Saleem, Sara, Thienne Johnson, and Srinivasan Ramasubramanian. "Design of a self-forming, self-healing small-medium infrastructure wireless mesh network." 2013 IEEE International Conference on Sensing, Communications and Networking (SECON). IEEE, 2013. (Year: 2013). *
Tjoens et al; "DHCP reconfigure extension;" Bernard; Internet Engineering Task Force Ietf Standard, Internet Society; pp. 2 (line 1); pp. 4 (last line); Dec. 1, 2001.

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210400015A1 (en) * 2019-01-17 2021-12-23 Hewlett Packard Enterprise Development Lp Short-term lease allocation for network address conflict reduction in dhcp failover deployments

Also Published As

Publication number Publication date
FR3091128A1 (fr) 2020-06-26
EP3881523B1 (de) 2023-09-27
WO2020127680A1 (fr) 2020-06-25
US20220078160A1 (en) 2022-03-10
EP3881523A1 (de) 2021-09-22
FR3091128B1 (fr) 2021-01-15

Similar Documents

Publication Publication Date Title
CN1985470B (zh) 用于动态主机配置协议框架的配置管理的系统和网络实体
JP5364671B2 (ja) ネットワーク認証における端末接続状態管理
JP4727537B2 (ja) リレーエージェント装置及び代行アドレス貸与装置
US8543669B2 (en) Network switch and method of preventing IP address collision
US10560550B1 (en) Automatic configuration of a replacement network device in a high-availability cluster
JP6389956B2 (ja) ネットワークトラフィックを管理する方法およびシステム
CN112654049B (zh) 用于配置无线通信覆盖扩展系统的方法、系统、节点和介质
WO2017177798A1 (zh) 一种接入点发现云接入控制器的方法和系统
US20160119186A1 (en) Zero-configuration networking protocol
US10841154B1 (en) Systems and methods for network discovery for zero configuration based-clustered systems
US10708223B2 (en) Dynamically defining encryption spaces across multiple data centers
CN110932876B (zh) 一种通信系统、方法及装置
US11729140B2 (en) Method and system for managing DHCP servers
JP6445408B2 (ja) 通信システムおよび設定方法
US20150229520A1 (en) Network monitoring system, communication device, network management method
CN112910704B (zh) 一种支持动态自适应网络配置的局域网系统、方法和装置
US9256416B1 (en) Methods and apparatus for automatic session validation for distributed access points
US20230146880A1 (en) Management system and management method
JP5370493B2 (ja) 通信システム、通信装置、通信制御方法及び通信制御プログラム
JP6360012B2 (ja) ネットワーク統合システムおよびネットワーク統合方法
Syafei et al. Centralized Dynamic Host Configuration Protocol and Relay Agent for Smart Wireless Router
US11683225B2 (en) Relay device and non-transitory computer readable medium
US11283755B2 (en) Method for identifying a communication node
US20230171226A1 (en) Method for configuring a communication network and node implementing said configuration method
EP4184822A1 (de) Verfahren und vorrichtung zur lebendhaltung eines benutzerendgeräts

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: SAGEMCOM BROADBAND SAS, FRANCE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:COLLIAUX, MATHIEU;REEL/FRAME:056758/0211

Effective date: 20210625

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE