-
Notifications
You must be signed in to change notification settings - Fork 483
Description
Describe the bug
I'm using the latest version and noticed that logging isn't working properly. I don't always have it enabled, and I remember it working with previous versions.
If I use the LOG target, only one rule is created within the afwall-reject chain, while all other chains remain the same (only 1 reject).
Thus, the dmesg --follow process receives nothing, and AFWall doesn't receive anything either.
Using the NFLOG target, multiple nflog-prefix "{AFL}" nflog-group 40 rules with NFLOG are created within the various *-reject chains, but then no one manages the received logs.
I don't know what the dev.ukanth.ufirewall/app_bin/nflog 40 process does but it doesn't seem to communicate properly with the app
With the command tcpdump -i nflog:40 -n, I can see them, but AFWall doesn't receive anything.
Firewall Logs
Attached log.zip
Smartphone (please complete the following information):
- Device: Samsung A72
- Android OS: 14 original ROM
Additional context