MrEngineerMind

I too see this issue in 3.5.2.

I know if you reboot the device, it will fix the problem. But I think if you do a manual "Apply Rules" in the app, that might also fix the...

Try adding this custom script to afwall+ and see if tethering starts to work (it worked for me): iptables -I afwall-wifi-tether 1 -p udp -m owner --uid-owner 1052 -m udp...

Sometimes you need to reboot the phone for them to work, and sometimes just doing an "Apply Rules" works too.

OK, I am not an IPtables expert, so I have some questions... I have a Pixel 4a Running Android 10. 1) In the "Startup Directory path for script" I am...

So, can this be done... Modify the script so that it doesn't try to access /data/data so that the script can fully run even before the phone is unlocked. And...

I'm confused, most cell networks won't allow incoming connections unless an outgoing connection to that source was initiated first. And, since your phone's cellular connection IP address will often change...

Did you update AFWall or is auto-update enabled for it in the playstore? I have seen AFWall reset to default mode after an update.

I can confirm that this issue happens when upgrading from 3.5.1 to 3.5.2.

Your issue is that there is no wifi calling when afwall enabled. That means afwall is blocking "something" that wifi needs to work. So, to figure out what that "something"...