Commit graph

9 commits

Author SHA1 Message Date
Gustavo Iñiguez Goia
f79bde1226
updated ebpf workflow 2026-04-14 01:42:40 +02:00
Gustavo Iñiguez Goia
94e533077e
updated workflows
- fixed watch path
- updated ebpf modules build matrix.
2026-04-14 01:26:49 +02:00
Gustavo Iñiguez Goia
7ea473f823 actions/upload-artifact bumped to v4
Some checks failed
CI - build eBPF modules / build (6.0, 1.5.0) (push) Has been cancelled
CI - build eBPF modules / build (6.0, master) (push) Has been cancelled
Test resources validation / Install tools (push) Has been cancelled
Build status / Build (push) Has been cancelled
2025-02-25 16:23:50 +01:00
Gustavo Iñiguez Goia
6b297a93b1
ci: removed compiling for 5.8 kernel 2023-05-17 17:28:55 +02:00
Gustavo Iñiguez Goia
0bb46197cc
ci fixes 2023-05-17 12:54:36 +02:00
Gustavo Iñiguez Goia
f97e7392a3
ci fixes 2023-05-17 12:26:49 +02:00
Gustavo Iñiguez Goia
ba64379348
ebpf: new way of compiling the modules
- Don't rename libbpf's bpf_map_def struct, and distribute the needed bpf
  headers.
  The bpf_map_def struct has been deprecated for quite some time now,
  and it was been removed on >= 6.2 anyway.
  We still need it, because we use gobpf.
- Improved compilation behaviour:
  - We don't require the kernel sources anymore. We can just use the
    kernel headers from the distribution.
  - There's no need to copy the sources to the kernel tree, the modules
    can be compiled from the ebpf_prog/ dir.
- Compiling against kernels 6.x seems to solve the problem we had with
  VPNs, where connections were not intercepted with modules compiled
  against 5.8, on kernels >= 5.19.

The modules has been tested on kernels 4.17, 5.4, 5.10, 5.15, 6.1 and
6.2 (kernel connections included).

Closes: #939
2023-05-17 01:20:53 +02:00
Spencer Comfort
a5a24403eb
Bump workflow actions (#828)
* Update build_ebpf_modules.yml

* Update go.yml
2023-02-01 17:31:13 +01:00
Gustavo Iñiguez Goia
09182fad2e
ebpf,action: compile modules when a change is pushed
Build eBPF modules whenever a change to the modules is pushed.
It'll fail if there're some warnings.

The action compiles *and publishes* the modules for several branches and
kernels.

Hopefully this will help to automate this process and be more transparent.
It'll also help on issues like this one: #454
2022-10-05 16:38:58 +02:00