evilsocket / evilsocket/opensnitch

netdiscover's network access not detected or blocked

Open
#1,182 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
14.1k
Forks
665
PR merge metrics
No merged PRs in 30d

Description

Please, check the FAQ and Known Problems pages before creating the bug report:

https://github.com/evilsocket/opensnitch/wiki/FAQs

GUI related issues:
https://github.com/evilsocket/opensnitch/wiki/GUI-known-problems

Daemon related issues:
- Run `opensnitchd -check-requirements` to see if your kernel is compatible.: All green
- https://github.com/evilsocket/opensnitch/wiki/daemon-known-problems

**Describe the bug**
It seems `netdiscover` passes under the radar of opensnitch. I'm not actually sure what type of sockets netdiscover uses, so I don't know if this is expected.

Include the following information:
- OpenSnitch version. 1.6.5.1-1 (installed from distro + ebpf from AUR)
- OS: Arch Linux
- Version: rolling release
- Window Manager: KDE Plasma 6.1.4
- Kernel version: `Linux athena 6.10.8-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Wed, 04 Sep 2024 15:18:31 +0000 x86_64 GNU/Linux`

**To Reproduce**
Steps to reproduce the behavior:
1. Install netdiscover: `pacman -S netdiscover`
2. Enable opensnitch and verify it works with "normal" programs (getting popups etc)
3. Run netdiscover.
4. OpenSnitch doesn't detect or block netdiscover's network access. And netdiscover works as if opensnitch wasn't there.

**Post error logs:**
I don't see any relevant error logs in this case.

**Expected behavior (optional)**
Netdiscover shouldn't be able to bypass opensnitch.

**Screenshots**
If applicable, add screenshots or videos to help explain your problem. It may help to understand the issue much better.

**Additional context**
Add any other context about the problem here.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.