Description
I’m trying to run networking software inside an exe.dev VM that needs to:
- create a dummy network interface
- attach TC/eBPF programs to interface ingress/egress hooks
The VM has general eBPF support enabled, but appears to be missing a few networking-specific kernel options.
Environment
Commands used to check
uname -r
zgrep -E 'CONFIG_BPF|CONFIG_BPF_JIT|CONFIG_KPROBES|CONFIG_UPROBES|CONFIG_TRACEPOINTS|CONFIG_FTRACE|CONFIG_NET_CLS_BPF|CONFIG_NET_ACT_BPF|CONFIG_DUMMY' /proc/config.gz
Current kernel config
General eBPF features appear to be enabled:
CONFIG_BPF=y
CONFIG_BPF_SYSCALL=y
CONFIG_BPF_JIT=y
CONFIG_BPF_JIT_DEFAULT_ON=y
CONFIG_TRACEPOINTS=y
CONFIG_KPROBES=y
CONFIG_KPROBES_ON_FTRACE=y
CONFIG_UPROBES=y
CONFIG_FTRACE=y
CONFIG_BPF_EVENTS=y
But these required networking features are missing:
# CONFIG_NET_CLS_BPF is not set
# CONFIG_NET_ACT_BPF is not set
# CONFIG_DUMMY is not set
Reproduction
Creating a dummy interface fails:
sudo ip link add testdummy0 type dummy
Result:
Error: Unknown device type.
Trying to load the dummy module also fails:
Result:
modprobe: FATAL: Module dummy not found in directory /lib/modules/6.12.93
A veth interface can be created, but TC/eBPF attachment is still blocked because CONFIG_NET_CLS_BPF / CONFIG_NET_ACT_BPF are not enabled.
Request
Could exe.dev enable these kernel options, either built-in or as modules?
CONFIG_DUMMY=y or m
CONFIG_NET_CLS_BPF=y or m
CONFIG_NET_ACT_BPF=y or m
This would allow workloads to create dummy network devices and attach TC/eBPF programs to network interfaces.
Related issues
This is related to, but more specific than:
Issue #127 enabled broader eBPF support, and that does appear to be working. This request is specifically for TC networking BPF support and dummy netdev support.
Description
I’m trying to run networking software inside an exe.dev VM that needs to:
The VM has general eBPF support enabled, but appears to be missing a few networking-specific kernel options.
Environment
Commands used to check
uname -r zgrep -E 'CONFIG_BPF|CONFIG_BPF_JIT|CONFIG_KPROBES|CONFIG_UPROBES|CONFIG_TRACEPOINTS|CONFIG_FTRACE|CONFIG_NET_CLS_BPF|CONFIG_NET_ACT_BPF|CONFIG_DUMMY' /proc/config.gzCurrent kernel config
General eBPF features appear to be enabled:
But these required networking features are missing:
Reproduction
Creating a dummy interface fails:
sudo ip link add testdummy0 type dummyResult:
Trying to load the dummy module also fails:
Result:
A
vethinterface can be created, but TC/eBPF attachment is still blocked becauseCONFIG_NET_CLS_BPF/CONFIG_NET_ACT_BPFare not enabled.Request
Could exe.dev enable these kernel options, either built-in or as modules?
This would allow workloads to create dummy network devices and attach TC/eBPF programs to network interfaces.
Related issues
This is related to, but more specific than:
Issue #127 enabled broader eBPF support, and that does appear to be working. This request is specifically for TC networking BPF support and dummy netdev support.