Skip to content
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

[ISSUE] OUTPUT Chain (IPv4) automatically changes back after "Apply" #1386

Open
WalkerSky001 opened this issue Jun 4, 2024 · 0 comments
Open
Labels

Comments

@WalkerSky001
Copy link

WalkerSky001 commented Jun 4, 2024

I am finding that when
Preferences -> Rules/Connectivity -> "OUTPUT Chain (IPv4)" is turned off / set to "Currently BLOCKED outgoing connections",
then "Apply" is selected, only about 114 rules are applied (which is less than when i first started using this app), and when i go back into Preferences -> Rules/Connectivity ->"OUTPUT Chain (IPv4)" the setting has been set back to "Currently ALLOWED outgoing connections".

All other changes which are made stick, its only this which does not. For example, if "INPUT Chain (IPv4)" is set and applied, it sticks, where as "OUTPUT Chain (IPv4)" always gets reverted back after apply is selected. Its as if there is another program in the background reverting this for some reason. It is also unclear what rule is linked to this option, or which logs are linked to this optioning and being written, as i am unable to track down what could be causing this issue using logs.

Also, i have wiped my device many times and changed / updated firmware and this issue persists. However, if i get a brand new device and ROOT it, then reinstall AFWall+, this fixes the issue for about a week, then back to square one again.

The Devices i have used are, Samsung S10 [Android 9], Asus ZenFone 8 [Androin 11 and 13], uleFone Armor 23 Ultra Android 13.

1_Before_crop
2_During_Crop
3_During2_Crop
4_After_Crop

What might also be helpful to know is, where are these rueles stored? is there a way of write protecting the rules so that only AFWall+ can access them? Or maybe an iptables problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant