Load Balancing and Client IP Addressing

You've probably configured a load balancer or web server to use the "X-Forwarded-For" header, or maybe you've followed a tutorial to ensure that a client's real IP address is passed to a backend web service. But why is all this necessary, and what factors do you have to consider when using different load balancing strategies? In this video, we take a packet-level deep dive into the impact that different load balancing strategies have on preserving a client's real IP address.

Configuration examples: https://github.com/acritelli/beyond-t...

VIDEO CHAPTERS
00:00 - Intro
00:13 - Video Overview
00:52 - Background
02:35 - Environment Setup

03:21 - HTTP(S) Reverse Proxy with HAProxy and NGINX
04:00 - HAProxy and NGINX Without X-Fowarded-For
05:52 - Reverse Proxy Packet Capture Without X-Forwarded-For
07:28 - Reverse Proxy Traffic Flow
07:54 - HAProxy and NGINX X-Forwarded-For Configuration
10:02 - Reverse Proxy Packet Capture With X-Forwarded-For
11:19 - Reverse Proxy Considerations

12:15 - TCP Reverse Proxy with HAProxy and NGINX
13:44 - PROXY Protocol Overview
14:06 - PROXY Protocol Configuration
14:34 - PROXY Protocol Packet Capture
17:05 - PROXY Protocol Traffic Flow
17:33 - TCP Reverse Proxy Considerations

18:09 - Transparent Load Balancing with IPVS and NGINX
18:40 - IPVS Configuration
21:13 - Transparent Load Balancing Packet Capture
22:46 - Transparent Load Balancing Traffic Flow
24:15 - Transparent Load Balancing Considerations

24:36 - Video Conclusion
25:17 - Outro