firewall bug

Avast Mobile Security Avast Mobile Security for Android
1

Hi guys,
on my samsung galaxy s plus (GT-I9001) with stock gingerbread 2.3.6 (rooted, baseband: I9001XXKPH, kernel version 2.6.35.7-perf, build: GINGERBREAD.AIKP4) with latest AMS 2.0.3380, after a reboot firewall rules are not applied (I checked with the command “iptables -L” from the terminal), even if the firewall is apparently enabled according to the avast mobile security application.
If I disable the firewall and then I re-enable it, I get all avast firewall rules applied and they stay there seamlessly until
next reboot,

thanks
Cristiano

2

did you try to enable the “take highest priority” firewall setting?

3

yes I did and it is the same, the only good thing is that
this problem is systematic i.e. it happens every time I reboot,

regards,
Cristiano

4

Performance kernels can disable some iptables politics on the startup. You can try to flash another kernel with netfilter support. Also you can enable kernel logging in tweaks and see, what exactly happen during start. Some speedmode kernels are not very friendly for statica rules due their support of NAT and balance routing.

5

this specific problem did not happen with previous AMS version 2.0.2880 and droidwall works fine
hence I do not believe it is a kernel issue, but something specific to AMS.

regards
Cristiano

6

i heard the issue from another user as well - we checked the logs and there was no errors, rules were applied normally. do you have any other tools installed that could conflict?

7

Dear Reinhard,
I have droidwall, are there any other possible conflicting application?
I could try to uninstall it and see…

regards Cristiano

8

please try to uninstall droid wall and check!

9

I uninstalled droidwall and I rebooted…unfortunately it is the same

regards Cristiano

10

Absolutely the same problem here as posted by the OP.

Samsung GT-5830i (Ace i), Baseband S5830IXXLA2, Android-Version 2.3.6, with Rafael Baugis Kernel 2.36.5.7.

Would be nice to get a fix in the next version.

Oh and yes, 2.0.2880 works ok but also doesn’t start automatically. However, starting the firewall by using the widget works ok.

Cheers.

11

strange as i said, the logs say no problem. it really seems to be some conflicting app.

12

…but droidwall works fine and old AMS 2.0.2880 in my case did not have such issue at boot

13

if we could reproduce it… on our phones we do not have any such issues. maybe you (cridemichel) could send me a log maybe there’s something different. contact me at holzner (at) avast.com and refer to this thread.

14

ok I will send you soon a log
regards
Cristiano

15

Dear Reinhard,
could you please remind me how to enable the ams logging?

regards,
Cristiano

16

a) Create an empty file called “avast-debug” on your /sdcard root directory (on Android 4.x phones there might be a user subdirectory in the sdcard path – if yes use that)
b) REBOOT your phone
c) Now Avast generates a lot of log
d) Try to reconstruct your problem
e) After that, open Mobile Security or Anti-Theft (depending in which product your problem occurs) and go to the feedback screen (About)
f) Check “Send system log”
g) Create a case there giving your email address and mention this conversation as well as a short description of the problem (maybe someone else will get the case)
h) Then remove the avast-debug file again
i) REBOOT your phone
j) Everything back to normal

17

logfile sent

18

anything useful in the log file which I have sent?
regards
Cristiano

19

sorry i did not get a ticket. can you get me the case#?

20

Dear Reinhard,
ticket number is KCN-240-28570, anyway I saw it has been wrongly considered “solved”.
If needed I can submit a new one with a new logfile, let me know

regards,
Cristiano