Abstract: A flow routing system includes a source device and a destination device that are coupled together via a network that includes a Software Defined Networking (SDN) device. The source device generates a packet that includes a packet header, provides a connection identifier in the packet header, and transmits the packet through the network. The SDN device receives the packet through the network from the source device, matches the connection identifier that is included in the packet header to a single tuple in a flow entry of a flow table and, in response, uses the flow entry to route the packet through the network to the destination device. The connection identifier may be provided by hashing a source IP address, a destination IP address, a VLAN identity, a source MAC address, a source port identifier, a destination port identifier; and a creation time for the flow including the packet.

Abstract: An information handling system includes a memory to store a set of instructions, and a processor. The processor receives a maximum transmission unit (MTU) packet from a second information handling system via a first portion of a communication path, and in response to the information handling system not being a final destination information handling system compares a current MTU size of the communication path with a next MTU size of the communication path. In response to the next MTU size being smaller than the initial MTU size, the processor replaces the current MTU size with the next MTU size as the current MTU size, otherwise maintains the current MTU size as the current MTU size. The processor also provides the MTU packet to a next information handling system via the next portion of the communication path.

Abstract: A network device may be configured to cause one or more network address allocation communications broadcast in a network to be communicated as directed unicast communications. More particularly, in a Local Area Network, a routing device such as a switch may be modified to receive broadcast communications for network address allocation, and instead of propagating the broadcast communications as broadcast communications, the routing device may route the network address allocation communications as directed unicast communications in the Local Area Network.

Abstract: A pre-boot file transfer system includes at least one server device that creates a plurality of packets for a file and provides a respective file offset value for each of the plurality of packets in a header of that packet. The at least one server device transmits each of the plurality of packets over a network to a client device that is in a pre-boot environment. The client device receives each of the plurality of packets and stores the plurality of packets in a receive buffer in the order that the plurality of packets were received. The client device then writes the plurality of packets that were stored in the receive buffer into an application buffer in an order that is defined by the respective file offset values for the plurality of packets.

Abstract: A flow routing system includes a source device and a destination device that are coupled together via a network that includes a Software Defined Networking (SDN) device. The source device generates a packet that includes a packet header, provides a connection identifier in the packet header, and transmits the packet through the network. The SDN device receives the packet through the network from the source device, matches the connection identifier that is included in the packet header to a single tuple in a flow entry of a flow table and, in response, uses the flow entry to route the packet through the network to the destination device. The connection identifier may be provided by hashing a source IP address, a destination IP address, a VLAN identity, a source MAC address, a source port identifier, a destination port identifier; and a creation time for the flow including the packet.

Abstract: Methods and systems for intelligent network checksum processing are disclosed. A method for intelligent network checksum processing may include receiving a data unit at a receiver network element sent from a sender network element, determining a success count of the sender network element, determining whether to perform a checksum validation at the receiver network element, wherein the determining may include skipping the checksum validation if the success count of the sender network element is greater than the predefined threshold success count, and performing the checksum validation if the success count of the sender network element is not greater than a predefined threshold success count, incrementing the success count of the sender network element if the checksum validation is performed and the checksum validation is successful, and resetting the success count of the sender network element if the checksum validation is performed and the checksum validation is unsuccessful.

Abstract: An information handling system includes a memory to store a set of instructions, and a processor. The processor receives a maximum transmission unit (MTU) packet from a second information handling system via a first portion of a communication path, and in response to the information handling system not being a final destination information handling system compares a current MTU size of the communication path with a next MTU size of the communication path. In response to the next MTU size being smaller than the initial MTU size, the processor replaces the current MTU size with the next MTU size as the current MTU size, otherwise maintains the current MTU size as the current MTU size. The processor also provides the MTU packet to a next information handling system via the next portion of the communication path.

Abstract: Methods and systems for intelligent network checksum processing are disclosed. A method for intelligent network checksum processing may include receiving a data unit at a receiver network element sent from a sender network element, determining a success count of the sender network element, determining whether to perform a checksum validation at the receiver network element, wherein the determining may include skipping the checksum validation if the success count of the sender network element is greater than the predefined threshold success count, and performing the checksum validation if the success count of the sender network element is not greater than a predefined threshold success count, incrementing the success count of the sender network element if the checksum validation is performed and the checksum validation is successful, and resetting the success count of the sender network element if the checksum validation is performed and the checksum validation is unsuccessful.

Abstract: A network device may be configured to cause one or more network address allocation communications broadcast in a network to be communicated as directed unicast communications. More particularly, in a Local Area Network, a routing device such as a switch may be modified to receive broadcast communications for network address allocation, and instead of propagating the broadcast communications as broadcast communications, the routing device may route the network address allocation communications as directed unicast communications in the Local Area Network.

Abstract: A pre-boot file transfer system includes at least one server device that creates a plurality of packets for a file and provides a respective file offset value for each of the plurality of packets in a header of that packet. The at least one server device transmits each of the plurality of packets over a network to a client device that is in a pre-boot environment. The client device receives each of the plurality of packets and stores the plurality of packets in a receive buffer in the order that the plurality of packets were received. The client device then writes the plurality of packets that were stored in the receive buffer into an application buffer in an order that is defined by the respective file offset values for the plurality of packets.