Lightboard Lessons: BIG-IP Life of a Packet
In this episode of Lightboard Lessons, Jason updates an earlier Whiteboard Wednesday with a slight change in flow introduced in TMOS version 12.1. Some of the features in this flow are only applicabl...
Published Feb 01, 2017
Version 1.0JRahm
Admin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.JRahm
Admin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.Richard_Shuford
Sep 30, 2021Ret. Employee
[responding to "epaalx"] As Jason wrote in an earlier comment, the term "HUD" was inspired by the motion picture "The Hudsucker Proxy". The "HUD chain" is essentially a logical stack of filter layers stacked up on either side of the dual-proxy processing paradigm used by the TMM (the Traffic Management Microkernel process). An input packet comes in and goes up the HUD chain on one side (potentially undergoing processing at each layer of the stack), and then from the pinnacle goes down the chain on the other side and then (typically) out to something outside BIG-IP.