AFWall+ not working after reboot

Hello,

I recently opened #699 but it seems that actually the problem is another: I uninstalled and reinstalled AFWall+ and bought the license and had an empty setup. In this everything was okay, i.e., all apps were blocked - also VPN based.

Yet, after an immediate reboot of the phone (AICP based on LineageOS, Android 7.1, device HTC10) I noticed that beside the fact that no app was selected for traffic (i.e., all should still be blocked) internet traffic was flowing normally. The browser could access any page, Google Play was working, etc.

So it seems that after a device reboot AFWall+ does not get activated again though it says that it is active.

[github-tomster]

i can confirm this. AOKP 7.1.2 rom build on 2017-04-18.
AFWall is the first apk installed on the phone.
it shows enabled, and applying rules is working.
though no traffic is blocked. all apps do have network access...
i rebootet: still all app can access
i disabled AFWall, enabled AFWall (no reboot) and the AFWall works.
the next reboot AFWall was still working...

[java-py-c-cpp-js]

Hi,

I seem to have the same or at least a very similar Problem, but in my case blocking mobile Internet works, blocking WiFi doesn't. I'm using LineageOS with Android 7.1.2 also. Dis- and enabling AFWall doesn't fix the problem.

[watchmoretv]

Hi,
i can confirm github-tomster's afwall behaviour on LineageOS 14 (7.1.2).
Showing enabled, but not working after boot up, even with "Startup delay" enabled. Another problem, not an issue but more related to my own incapability, regarding SELinux and "Fix startup data leak" init.d:
dmesg gives me tons of

[ xxx.xxxxx] type=1400 audit(123.456): avc: denied { getattr } for pid=229 comm="afwallstart" path="/data/data/com.android.providers.downloads" dev="mmcblk0p14" ino=32233 scontext=u:r:sysinit:s0 tcontext=u:object_r:app_data_file:s0:c512,c768 tclass=dir permissive=0

and i know nothing about SELinux. I would be glad if someone could tell me how to "chcon u:object_r:" this.

After boot and restarting Afwall, it even stopped working randomly, but i could solve this by disabling the battery save mode. On Lineage you can make exceptions for background apps, but afwall won't stay on that list, so i think this issue is LineageOS related.

Ukanth, thank your for afwall. At least a contraceptive in this filthy, dirty virtual world ;-)

[gytisrepecka]

I can also confirm same issue on Motorola Nexus 6 device running Lineage OS 14.1 with addon-superuser - after reboot AFWall doesn't block any traffic, it works only when manually applying rules. Startup delay enabled, but still no luck...

[github-tomster]

me again.
sorry to bother.
fresh flash all wiped/formated
afwall first app installed after supersu flashed via recovery zip
not working unfortunately. all apps have network-access.
it seems a bit weird that afwall doesnt detects the active interface.

===========
System info

Android version: 7.1.2
Manufacturer: Samsung
Model: GT-I9195
Build: lineage_serranoltexx-userdebug 7.1.2 N2G47E fa709cffc5 test-keys
Active interface: unknown
Tether status: unknown
Roam status: no
IPv4 subnet:
IPv6 subnet:
/system/bin/su: not present
/system/xbin/su: not present
/system/app/Superuser.apk: not present
Superuser: eu.chainfire.supersu v2.79

===========
Preferences

activeNotification: false
activeRules: true
addStartupDelay: false
appVersion: 15940
blockIPv6: true
disableIcons: false
enableAdmin: true
enableConfirm: true
enableDeviceCheck: false
enableIPv6: false
enableLAN: true
enableLogService: true
enableRoam: false
enableVPN: false
fixLeak: false
hasRoot: true
ipurchaseddonatekey: false
logDmesg: OS
logPingTimeout: 10
logTarget: NFLOG
notifyAppInstall: true
oldLogView: true
passSetting: p0
patternMax: 3
ruleTextSize: 10
showFilter: true
showLogToasts: false
showUid: true
storedPid: []
sysColor: -10432
toast_pos: bottom
Profile Mode : whitelist
Status : Enabled

======
Logcat

22:05:10 Selected Profile: AFWallPrefs
22:05:10 Now assuming NO connection (all interfaces down)
22:05:10 Selected Profile: AFWallPrefs
22:05:10 applySavedIptablesRules invoked
22:05:10 Setting OUTPUT to Drop
22:05:10 Setting OUTPUT to Accept
22:05:10 Starting root shell...
22:05:10 [libsuperuser] [SU%] START
22:05:10 Starting Log Service: echo $$ & /data/user/0/dev.ukanth.ufirewall/app_bin/nflog 40 for LogTarget: NFLOG
22:05:10 rootSession is not Null
22:05:10 [libsuperuser] [SU%] START
22:05:10 Cleanup session
22:05:11 Root shell is open
22:05:17 BOOT_COMPLETED: applied rules at 1493669117336
22:05:39 Selected Profile: AFWallPrefs

[java-py-c-cpp-js]

In my case I could solve the problem by disabling Lan control. As soon as I enable it again and apply the rules afwall blocks nothing, even after restarting android. It makes no difference whether I enabling or disabling battery optimisation for AfWall.

[gytisrepecka]

Thanks, disabling LAN control in Preferences > Rules/Connectivity did fix the issue - now all rules are working after reboot.

[github-tomster]

i can not confirm that here.
after the reboot, still ALL apps have access and the active_interface
is still unknown, though a wifi connection is established.
hence all apps have network access.
right after the check of afwall rules and closing afwall interface
a toast appears stating su rights for afwall granted
right after that network connections are restricted as wanted!
when i check the rules now, the active_interface is wifi and the rules are working
correct.
is there anything i can do? or is there an explanation of the cause?
maybe it is a linage error? i can test if one tells me how and what steps to do.
the device is a test device, not productive.

[gytisrepecka]

Which superuser app do you use?

[github-tomster]

===========
System info

Android version: 7.1.2
Manufacturer: Samsung
Model: GT-I9195
Build: aokp_serranoltexx-userdebug 7.1.2 N2G47E e0fd8da3e5 test-keys
Active interface: wifi
Tether status: no
Roam status: no
IPv4 subnet: 192.168.xxx.xxx/24
IPv6 subnet: xxx
/system/bin/su: 79468 bytes
/system/xbin/su: 79468 bytes
/system/app/Superuser.apk: not present
Superuser: eu.chainfire.supersu v2.79

this is my systeminfo

[ThatLarsGuy]

I have the same issue. LineageOS 14.1 (Android 7.1) on a Galaxy S5 - AFWall+ only blocks traffic if I disable LAN control in Preferences > Rules/Connectivity.

[github-tomster]

i have to add that the LAN control is essential to me as some apps indeed
only are allowed to use LAN ressources.
@ukanth
what can i do to help solving the issue?

[rancidfrog]

On 2.9.5, still the case.
After boot from switch off state or reboot apps have access even though blocked.
Opening app sometimes applies rules, if not manual reapply needed.