An eBPF loophole: Using XDP for egress traffic
loopholelabs.io
An eBPF loophole: Using XDP for egress traffic
1–10 of 81 posts
Re: An eBPF loophole: Using XDP for egress traffic
#2This post not only expands on the overall implementation but also outlines how existing container and VM workloads can immediately take advantage with minimal effort and zero infrastructure changes.
Re: An eBPF loophole: Using XDP for egress traffic
#3Re: An eBPF loophole: Using XDP for egress traffic
#4Re: An eBPF loophole: Using XDP for egress traffic
#5You can also use XDP for outgoing packets for tap interfaces.
Re: An eBPF loophole: Using XDP for egress traffic
#6In some scenarios veth is being replaced with netkit for a similar reason. Does this impact how you're going to manage this?
Re: An eBPF loophole: Using XDP for egress traffic
#7XDP (eXpress Data Path) is the fastest packet processing framework in linux - but it only works for incoming (ingress) traffic. We discovered how to use it for outgoing (egress) traffic by exploiting a loophole in how the linux kernel determines packet direction. Our technique delivers 10x better performance than current solutions, works with existing Docker/Kubernetes containers, and requires zero kernel modificatio…