Systems and techniques are provided for synchronizing DHCP snoop information. In some examples, a method can include, performing, by a first PE device from a plurality of PE devices, DHCP snooping of a first plurality of DHCP messages between a DHCP client and a DHCP server, wherein the plurality of PE devices is part of an ethernet segment for multihoming the DHCP client. In some aspects, the method includes determining, based on snooping the first plurality of DHCP messages, an association between an IP address corresponding to the DHCP client and a MAC address corresponding to the DHCP client. In some examples, the method includes sending, by the first PE device to at least one other PE device from the plurality of PE devices, a first route advertisement that includes the association between the IP address corresponding to the DHCP client and the MAC address corresponding to the DHCP client.

Systems and techniques are provided for synchronizing DHCP snoop information. In some examples, a method can include, performing, by a first PE device from a plurality of PE devices, DHCP snooping of a first plurality of DHCP messages between a DHCP client and a DHCP server, wherein the plurality of PE devices is part of an ethernet segment for multihoming the DHCP client. In some aspects, the method includes determining, based on snooping the first plurality of DHCP messages, an association between an IP address corresponding to the DHCP client and a MAC address corresponding to the DHCP client. In some examples, the method includes sending, by the first PE device to at least one other PE device from the plurality of PE devices, a first route advertisement that includes the association between the IP address corresponding to the DHCP client and the MAC address corresponding to the DHCP client.

Systems, methods, and devices for performing targeted filtering of network traffic generated by user equipment (UE) devices connected to a customer premise equipment (CPE) device in a communication system that includes a distributed residential gateway. A network server may determine that the communication system includes a UE device that is compromised, misconfigured, or operating outside normal communication parameters, identify the UE device, determine an Internet protocol (IP) address or a media access control (MAC) address of the identified UE device, generate a quarantine request message that includes the IP address or the MAC address of the identified UE device in response to determining that the preconfigured virtual local area network access control list (VACL) on the CPE lists source IP addresses from which the CPE will filter outbound traffic, and send the generated quarantine request message to a bridged residential gateway (BRG) associated with the CPE device.

A wireless communication coverage extension system comprises a backhaul subnetwork that includes a set of interconnected nodes. A plurality of nodes of the backhaul subnetwork implementing a functionality of access point of a same wireless communication network. To avoid conflicts of IP addresses, a monitoring of the presence of the main DHCP server is implemented, by a said node, to which the main DHCP server is connected. In the case where the first monitoring shows a disconnection of the main DHCP server, a backup DHCP server is activated in a node of the backhaul subnetwork. Then a general disconnection of the nodes of the backhaul subnetwork and of any device connected to the wireless communication coverage extension system is implemented. The IP address leases are then renewed by the backup DHCP server, following the general disconnection.

A wireless communication coverage extension system comprises a backhaul subnetwork that includes a set of interconnected nodes. A plurality of nodes of the backhaul subnetwork implementing a functionality of access point of a same wireless communication network. To avoid conflicts of IP addresses, a monitoring of the presence of the main DHCP server is implemented, by a said node, to which the main DHCP server is connected. In the case where the first monitoring shows a disconnection of the main DHCP server, a backup DHCP server is activated in a node of the backhaul subnetwork. Then a general disconnection of the nodes of the backhaul subnetwork and of any device connected to the wireless communication coverage extension system is implemented. The IP address leases are then renewed by the backup DHCP server, following the general disconnection.

A method comprising: at a multi-link device (MLD) configured for multi-link operation: establishing a first Internet Protocol (IP) stack of a first IP type and configured with a first IP address of the first IP type, wherein the first IP stack is associated to a first MLD media access control (MAC) address of a first station of the MLD; establishing a second IP stack of a second IP type and configured with a second IP address of the second IP type, wherein the second IP stack exists concurrently with the first IP stack and is associated to a second MLD MAC address of a second station of the MLD; and exchanging, with a peer MLD, IP traffic using one or more of (i) the first IP stack and the first MLD MAC address, and (ii) the second IP stack and the second MLD MAC address.

Techniques for implementing a last known good (LKG) client-side cache for DNS resiliency are disclosed. A first DNS request is submitted to a DNS server. A first DNS resolution that resolves an IP address for a domain name is received. A service stores the first DNS resolution in an LKG cache residing on the local host. A second DNS request is sent, where the second DNS request again requests to resolve the same domain name. In response to determining that a second DNS resolution for the second DNS request has not been received, the service obtains the IP address for the domain name from the LKG cache.

Techniques for implementing a last known good (LKG) client-side cache for DNS resiliency are disclosed. A first DNS request is submitted to a DNS server. A first DNS resolution that resolves an IP address for a domain name is received. A service stores the first DNS resolution in an LKG cache residing on the local host. A second DNS request is sent, where the second DNS request again requests to resolve the same domain name. In response to determining that a second DNS resolution for the second DNS request has not been received, the service obtains the IP address for the domain name from the LKG cache.

Systems and methods for the dynamic selection of IP address in email platforms, and the synchronization of hostnames and IP addresses in such platforms, are disclosed.

Systems and methods for the dynamic selection of IP address in email platforms, and the synchronization of hostnames and IP addresses in such platforms, are disclosed.