-
-
Notifications
You must be signed in to change notification settings - Fork 520
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opensnitch log has failed netlink entries every 15 seconds (like #688) #781
Comments
Hi @cthulhubuddha , I've only reproduced this issue on Ubuntu 16. Could you post the output of Do you have other firewall configured? firewalld or ufw? |
Ah, yep, UFW is running. happy to securely send my ruleset somewhere, would prefer not to disclose on a forum. Is opensnitch using ufw and if so if i manually disable the instance i enabled prior to installing opensnitch will that break opensnitch? |
you can email me the rules + the log opensnitchd.log: gusi.xx [a] protonmail.com For now, set Firewall option to "iptables" in
No, we don't use ufw. if Firewall option is "iptables" we use iptables binary to add the rules, and if it's "nftables" we add the rules directly to the kernel. |
A couple of updates in testing back and forth between iptables and nftables. When nftables is used the issues does not occur when the gui is first opened. however, if you disable opensnitch in the gui and then re-enable it, the errors start appearing (again, every 15 seconds). when using iptables the errors do not occur as expected above. happy to help you troubleshoot it, but it looks like it is not related to the actual problem i am troubleshooting related to the list of domains not working, i'll open a separate issue for that. |
Thank you @cthulhubuddha !
I'll try to reproduce it this way 👍 Yes please, open a new issue. Things to look for in the logs regarding the domains list: If a domain is blocked by a list, it'll be appear in the logs as such:
A basic test would be to add www.example.org to a new list: Create a new rule with name: 000-domain-list-test , check [x] Priority rule and [x] Reject, (*) Always Verify tthat the list has been loaded:
And see if it's blocked from the command line:
opensnitchd.log:
(use ping, curl or wget to test it. firefox, chrome and other apps works in a different way) Also try stopping systemd-resolved and change /etc/resolv.conf nameservers to point to 9.9.9.9, 1.1.1.1, etc. We had problems with systemd-resolved in the past, but as far as I can tell, it seems to work fine now. |
Reproduced. I'll try to fix it. |
ok, I think this issue is fixed. I need to test it on more systems (ubuntu 16), but at least it solves the problem on PopOS! 22 and works as expected on Debian Sid. Thank you for reporting this problem @cthulhubuddha ! |
On some kernels (4.19), adding the interception rule to the inet-mangle-output chain failed. According to the nftables wiki, the mangle-output chain have (must?) to be of type Route: "route type: ... mangle table ... for the output hook (for other hooks use type filter instead)." https://wiki.nftables.org/wiki-nftables/index.php/Configuring_chains#Base_chain_types So if we fail adding the interception rule, we retry it with type Filter instead of Route. Related: #781 , ced9a24
New version released with this fix: https://github.com/evilsocket/opensnitch/releases/tag/v1.6.0-rc.4 |
PopOS 22.04, Opensnitch 1.6.0-rc.3-1
I am troubleshooting why regex domain lists are not working and have found these log entries appearing every 15 seconds, thinking it may be related. Using GUI for configuring. Issue #688 exists but was never resolved, here's a debug log sample:
The text was updated successfully, but these errors were encountered: