H04L2012/5617

Using standard fields to carry meta-information
09729431 · 2017-08-08 · ·

A method of processing one or more packets includes receiving, at a first processing unit, a first packet including first information bits. The first information bits indicate a first control parameter. The method also includes determining whether the first control parameter will be utilized to process the first packet in at least a second processing unit and, at least partially in response to determining that the first control parameter will not be utilized to process the first packet in at least the second processing unit, replacing one or more bits of the first information bits in the first packet with second information bits. The second information bits indicate a second control parameter. The method also includes providing the first packet including the second information bits to the second processing unit.

Offload controller control of programmable switch
10880124 · 2020-12-29 · ·

A method and system that include techniques for an offload controller that controls functionality of a programmable switch. The offload controller may handle hash management and/or hash collision resolution for the programmable switch. The offload controller may additionally or alternatively configure the programmable switch to forward packets directly to a virtual private cloud (VPC) and/or virtual machine (VM), bypassing a gateway in some instances.

Method and system for allowing a client to re-initiate DHCP request after undergoing VLAN change
10868698 · 2020-12-15 · ·

A method and system are devised of moving at a NAS (1) a client (12, 13) with a MAC address, from a first VLAN to a second VLAN. A leaf is comprised of at least one intermediate L2 bridge/switch (5, 9) being connected to the NAS (1). The client (12, 13) is being connected to one (9) of the at least one intermediate L2 bridge/switches (5, 9) in the leaf. The method and system involve sending at the NAS (1) a first message downlink (31, 36) to intermediate L2 bridge/switches (5) in the leaf directly connected to the NAS. They further involve at each intermediate L2 bridge/switch (5, 9) in the leaf: upon receiving the first message from uplink from the NAS (1) or an intermediate L2 bridge/switch (5, 9) in the leaf, determining whether the client (12, 13) is directly or indirectly connected to one of its ports; and if it is directly connected, bouncing the port to which the client (12, 13) is connected, and sending a second message uplink to the NAS (1) or an intermediate L2 bridge/switch (5, 9) in the leaf; if it is indirectly connected, sending the first message downlink on the port to which the client (12, 13) is indirectly connected to an intermediate L2 bridge/switches (5, 9) in the leaf; and if it is not connected, sending a third message uplink to the NAS (1) or an intermediate L2 bridge/switch (5, 9) in the leaf. They further involve at each intermediate L2 bridge/switch (5, 9) in the leaf: upon receiving the second or third message from downlink from an intermediate L2 bridge/switch (5, 9) in the leaf, forwarding it uplink to the NAS (1) or an intermediate L2 bridge/switch (5, 9) in the leaf. Finally the client (12, 13) may initiate a DHCP request in the second VLAN.

METHOD AND SYSTEM FOR ALLOWING A CLIENT TO RE-INITIATE DHCP REQUEST AFTER UNDERGOING VLAN CHANGE
20200382343 · 2020-12-03 ·

A method and system are devised of moving at a NAS (1) a client (12, 13) with a MAC address, from a first VLAN to a second VLAN. A leaf is comprised of at least one intermediate L2 bridge/switch (5, 9) being connected to the NAS (1). The client (12, 13) is being connected to one (9) of the at least one intermediate L2 bridge/switches (5, 9) in the leaf. The method and system involve sending at the NAS (1) a first message downlink (31, 36) to intermediate L2 bridge/switches (5) in the leaf directly connected to the NAS. They further involve at each intermediate L2 bridge/switch (5, 9) in the leaf: upon receiving the first message from uplink from the NAS (1) or an intermediate L2 bridge/switch (5, 9) in the leaf, determining whether the client (12, 13) is directly or indirectly connected to one of its ports; and if it is directly connected, bouncing the port to which the client (12, 13) is connected, and sending a second message uplink to the NAS (1) or an intermediate L2 bridge/switch (5, 9) in the leaf; if it is indirectly connected, sending the first message downlink on the port to which the client (12, 13) is indirectly connected to an intermediate L2 bridge/switches (5, 9) in the leaf; and if it is not connected, sending a third message uplink to the NAS (1) or an intermediate L2 bridge/switch (5, 9) in the leaf. They further involve at each intermediate L2 bridge/switch (5, 9) in the leaf: upon receiving the second or third message from downlink from an intermediate L2 bridge/switch (5, 9) in the leaf, forwarding it uplink to the NAS (1) or an intermediate L2 bridge/switch (5, 9) in the leaf. Finally the client (12, 13) may initiate a DHCP request in the second VLAN.

OFFLOAD CONTROLLER CONTROL OF PROGRAMMABLE SWITCH
20200213156 · 2020-07-02 ·

A method and system that include techniques for an offload controller that controls functionality of a programmable switch. The offload controller may handle hash management and/or hash collision resolution for the programmable switch. The offload controller may additionally or alternatively configure the programmable switch to forward packets directly to a virtual private cloud (VPC) and/or virtual machine (VM), bypassing a gateway in some instances.