You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bpf:hubble: support policy verdict from L3 devices
When `bpf_host` is attached to a L3 device and there are policies
(e.g., when HostFw is enabled), verdict notification are emitted, but
monitor/Hubble incorrectly decodes the packet, starting from a non-existent
L2 header. Let's fix this by adding a flag, similarly to what we did for
drop/trace notifications.
From v1.18 onwards, `bpf_wireguard` has its own program rather than attaching
`bpf_host` to the `cilium_wg0@ingress`. Though, it still can happen that
`bpf_host` is attached to some L3 device (TUN).
Example of PolicyVerdict incorrectly decoded:
```
Policy verdict log: flow 0x0 local EP ID 285, remote ID remote-node, proto 1, ingress, action allow, auth: disabled, match L4-Only, 40:00:40:01:90:a3 -> 45:c0:00:34:51:3b UnknownEthernetType
```
Example of PolicyVerdict correctly decoded after PR:
```
Policy verdict log: flow 0x0 local EP ID 285, remote ID remote-node, proto 1, ingress, action allow, auth: disabled, match L4-Only, 172.18.0.3 -> 172.18.0.4 EchoRequest
```
Signed-off-by: Simone Magnani <simone.magnani@isovalent.com>
0 commit comments