Bug#1037006: opensnitch: Upstream change enables ebpf compilation

2023-06-10 Thread Petter Reinholdtsen
In experimental there now is a new version of opensnitch buiding a ebpf module. -- Happy hacking Petter Reinholdtsen

Bug#1037006: opensnitch: Upstream change enables ebpf compilation

2023-06-02 Thread Pijgn
Control: retitle -1 opensnitch: Explicitly use 'proc' fallback by default Control: severity -1 minor Control: summary -1 0 Control: tags -1 - upstream + patch Debian 12 does not ship the eBPF module required for the upstream default process monitor method. The 'proc' method is used as an implicit

Bug#1037006: opensnitch: Upstream change enables ebpf compilation

2023-06-01 Thread Pijgn
On Thursday, June 1, 2023 6:22:14 PM EDT Gustavo Iñiguez Goya wrote: > Petter is correct: we fall back to proc when ebpf can't be used. > There's no difference in setting it to proc or let it fail. > The error is "open /etc/opensnitchd/opensnitch.o: no such file or > directory" This causes the

Bug#1037006: opensnitch: Upstream change enables ebpf compilation

2023-06-01 Thread Gustavo Iñiguez Goya
Hi all, On Thu, 1 Jun 2023 at 18:25, Pijgn wrote: > > [Petter Reinholdtsen] > > I believe this is a misunderstanding. Even if the default setting is > > ebpf, it will fall back to using proc when it fail to find the ebpf > > module. > > My testing suggests this is not reliable with the default

Bug#1037006: opensnitch: Upstream change enables ebpf compilation

2023-06-01 Thread Pijgn
[Petter Reinholdtsen] > I believe this is a misunderstanding. Even if the default setting is > ebpf, it will fall back to using proc when it fail to find the ebpf > module. My testing suggests this is not reliable with the default eBPF setting. Applying the 'Debug invalid connections' setting

Bug#1037006: opensnitch: Upstream change enables ebpf compilation

2023-06-01 Thread Petter Reinholdtsen
[Pijgn] > With the default setting to use eBPF monitoring, the option to 'Debug > invalid connections' has no effect unless > /etc/opensnitchd/opensnitch.o exists. I believe this is a misunderstanding. Even if the default setting is ebpf, it will fall back to using proc when it fail to find the

Bug#1037006: opensnitch: Upstream change enables ebpf compilation

2023-06-01 Thread Pijgn
[Petter Reinholdtsen] > I use opensnitch with NFS on Debian Bookworm, and have not noticed it > is making NFS unusable. How did you end up with this conclusion? I may be in error here. Having personally confirmed that wireguard was broken by the default opensnitch configuration in Debian, I

Bug#1037006: opensnitch: Upstream change enables ebpf compilation

2023-05-31 Thread Petter Reinholdtsen
[Pijgn] > OpenSnitch in Debian is currently incompatible with (some?) kernel space > network tools such as wireguard and NFS. These are entirely unusable so > long as the opensnitchd service is running. I use opensnitch with NFS on Debian Bookworm, and have not noticed it is making NFS

Bug#1037006: opensnitch: Upstream change enables ebpf compilation

2023-05-31 Thread Pijgn
Package: opensnitch Version: 1.5.8.1-1+b2 Severity: wishlist Tags: upstream Dear Maintainer, OpenSnitch in Debian is currently incompatible with (some?) kernel space network tools such as wireguard and NFS. These are entirely unusable so long as the opensnitchd service is running. An eBPF