From: Mathieu Xhonneux <[email protected]> Date: Tue, 24 Apr 2018 18:44:15 +0100
> This patch adds the End.BPF action to the LWT seg6local infrastructure. > This action works like any other seg6local End action, meaning that an IPv6 > header with SRH is needed, whose DA has to be equal to the SID of the > action. It will also advance the SRH to the next segment, the BPF program > does not have to take care of this. I'd like to see some BPF developers review this change. But on my side I wonder if, instead of validating the whole thing afterwards, we should make the helpers accessible by the eBPF program validate the changes as they are made.
