A system may comprise a group of processor cores configured to generate kernel-space threads in a kernel space and user-space threads in a user space of a Linux operating system. Each kernel-space thread may be executable by one of the processor cores to perform operations. For example, a kernel-space thread may receive a data packet transmitted from a client device via a network. The kernel-space thread may determine a particular communication channel assigned to a processor core that is executing the kernel-space thread. The kernel-space thread may determine if the data packet satisfies a condition based on information extracted from the data packet. In response to determining that the data packet does not satisfy the condition, the kernel-space thread may transmit data from the data packet via the particular communication channel to a user-space thread. The user-space thread may be configured to receive and process the data.

Various example embodiments for supporting an in-band control plane are presented. Various example embodiments for supporting an in-band control plane may be configured to support an in-band control plane in a Multiprotocol Label Switching (MPLS) network. Various example embodiments for supporting an in-band control plane in an MPLS network may be configured to support an in-band control plane in an MPLS network by supporting exchange of control protocol packets of control protocols as MPLS packets, such that the control protocol messaging is in-band along the MPLS data plane itself. Various example embodiments for supporting an in-band control plane in an MPLS network may be configured to support an in-band control plane in an MPLS network by supporting communication of MPLS packets that encapsulate control protocol messages of control protocols with an MPLS label which indicates that the payloads of the MPLS packets carry the control protocol messages of the control protocols.

A method is implemented by a switch in a software defined networking (SDN) network managed by a controller to achieve hitless resynchronization during a controller upgrade. The method includes installing an upgraded set of flow entries so that a packet processing pipeline of the switch includes both a non-upgraded set of flow entries and the upgraded set of flow entries, processing non-tunneled packets using the non-upgraded set of flow entries, processing tunneled packets that have a tunnel upgrade status indicator set in a tunnel header using the non-upgraded set of flow entries, while processing tunneled packets that do not have a tunnel upgrade status indicator set in a tunnel header using the upgraded set of flow entries, and processing non-tunneled packets using the upgraded set of flow entries after all switches managed by the controller have installed upgraded flow entries.

Systems and methods are provided for management of network segments that cross geographic regions and/or other types of network divisions in a cloud-based network environment. Gateway may manage traffic across regions using routing metadata that includes a segment identifier. The gateways may also signal their routes across regions based on segment data, and implement the signaled routes using segment-based routing policies. Route selection may be performed using optimization data.

Systems and methods for source address verification and/or retention for access devices.

Systems and methods for source address verification and/or retention for access devices.

Disclosed are a packet sending method, a packet receiving method, an electronic device, a packet sending and receiving system, and a storage medium. The packet sending method may include: acquiring a current sequence number of a current link-state packet; generating a link-state packet with a transition sequence number according to the current sequence number, the link-state packet with the transition sequence number is newer than a link-state packet with a maximum sequence number and older than a link-state packet with an initial sequence number; and sending the link-state packet with the transition sequence number.

Techniques for operating a networking switch in two broadcast networks are provided. In some embodiments, the switch may instantiate a first controller client and a second controller client in a control plane of the switch; register the first controller client with a first broadcast controller associated with a first broadcast network; and register the second controller client with a second broadcast controller associated with a second broadcast network. The switch may further receive a first multicast route through the first controller client; receive a second multicast route through the second controller client; and program at least one of the first multicast route and the second multicast route into a multicast routing information base.

Techniques for operating a networking switch in two broadcast networks are provided. In some embodiments, the switch may instantiate a first controller client and a second controller client in a control plane of the switch; register the first controller client with a first broadcast controller associated with a first broadcast network; and register the second controller client with a second broadcast controller associated with a second broadcast network. The switch may further receive a first multicast route through the first controller client; receive a second multicast route through the second controller client; and program at least one of the first multicast route and the second multicast route into a multicast routing information base.

In some examples, a provider edge device provides L2 virtual bridge connectivity for at least one customer network using an EVPN instance and L3 routing using an IRB interface that is a L3 routing interface assigned to the EVPN instance; the provider edge device obtains an indication of a new binding for an endpoint device of the at least one customer network, the new binding comprising a first L2 address and a L3 address that are assigned to the endpoint device; and the provider edge device outputs, in response to determining the provider edge device stores a prior binding for the endpoint device of a second L2 address and the L3 address that are assigned to the endpoint device, an EVPN route comprising an indication of the new binding and an indication the new binding is an updated binding of the prior binding for the endpoint device.