In the Cache-Based Packet Forwarding blog post I described what happens when someone tries to bypass the complexities of IP routing table lookup with a forwarding cache.
Now imagine you want to implement full-featured fast packet forwarding including ingress- and egress ACL, NAT, QoS… but find the required hardware (TCAM) too expensive. Wouldn’t it be nice if we could send the first packet of every flow to a CPU to figure out what to do with it, and download the results into a high-speed flow cache where they could be used to switch the subsequent packets of the same flow. Welcome to flow-based packet forwarding.
Print
Share
Comment
Cite
Upload
Translate
APA
() » Flow-Based Packet Forwarding. Retrieved from https://www.truth.cx/2022/03/08/flow-based-packet-forwarding/.
MLA" » Flow-Based Packet Forwarding." - , https://www.truth.cx/2022/03/08/flow-based-packet-forwarding/
HARVARD » Flow-Based Packet Forwarding., viewed ,
VANCOUVER - » Flow-Based Packet Forwarding. [Internet]. [Accessed ]. Available from: https://www.truth.cx/2022/03/08/flow-based-packet-forwarding/
CHICAGO" » Flow-Based Packet Forwarding." - Accessed . https://www.truth.cx/2022/03/08/flow-based-packet-forwarding/
IEEE" » Flow-Based Packet Forwarding." [Online]. Available: https://www.truth.cx/2022/03/08/flow-based-packet-forwarding/. [Accessed: ]