A network packet is a piece of data that traverses the network between devices. It contains information packaged within each request and response, which helps applications and other services communicate effectively. 

One network packet doesn't have to constitute the entire data payload. Instead, that payload is broken into individual units and reassembled once they reach their destination. The network therefore doesn't have to wait for the entire transfer, which can cause congestion. This concept, called packet switching, enables multiple devices to communicate over the same network without causing delays.

How do network packets work?

A network packet includes both a header and a payload. The header contains packet metadata (like source and destination IP addresses), packet size, and other essential request/response information. The payload describes the actual data in transit. This could include a portion of an email or another type of message. 

Ideally, a packet will choose the most efficient pathway across the network to boost efficiency. Routers and switches inspect the network packet to determine its intended destination before sending it onward. Finally, devices on the receiving end assess the header information before carefully reconstructing the full data payload.

How does HAProxy handle network packets?

HAProxy is a load balancer, which entails handling requests and responses between clients and servers. We can do this while preserving critical information contained within headers and other portions of a given message. Additionally, HAProxy supports traffic capturing to uncover key packet information such as IP addresses. 

Next, our PacketShield security feature uses stateful packet analysis to help mitigate DDoS attacks and block unwanted traffic, while letting legitimate traffic through. Overall, HAProxy works to preserve and pass along the important data contained within network packets while ensuring each payload is valid. 

To learn more about packet handling, read our introductory PacketShield blog and our write-up on the PROXY protocol.