search

longchuan1985 / droidwall

Automatically exported from code.google.com/p/droidwall
0 stars 0 forks source link

Correct work but "Log is empty" #96

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
product version 1.4.8, Android 2.1, Huawei U8110, rooted.

Programm works exellent, but I can't see its log - when I try it, I get message 
"Log is empty". Logging enable, accepting rules is correct, for getting clear 
results access allowed for any processes through WiFi and bloced for any 
processes through GPRS (Browser excluded).

Maybe criminal: Some time ago, but before DroidWall installation, I fixed 
permissions with ROM Manager.

Original issue reported on code.google.com by Svami.H...@gmail.com on 11 Feb 2011 at 10:07

GoogleCodeExporter commented 8 years ago 
If your log is always empty (even after DroidWall has blocked an application), 
it means that your kernel does not support the "iptables LOG target".

I found out that most ROM kernels were compiled with this option enabled, but 
there are a few ones without it... on this case the log cannot work. sorry

Original comment by rodrigo...@gmail.com on 11 Feb 2011 at 11:27

GoogleCodeExporter commented 8 years ago 
Damn it :(

I saw in the code part where - it seems - log enabling checks and do nothing if 
it not enable, but I was not sure due to bad understunding this programming 
language.

Do You know any modes or applications wich can correct this feature?
My Internet tariff is free and unlimited but I'm a paranoiac, and I hope this 
FireWall help me to understand wich program operates "in an underhand way" 
:)

Original comment by Svami.H...@gmail.com on 11 Feb 2011 at 12:03

GoogleCodeExporter commented 8 years ago 
Installing a customized ROM would probably allow you to use all DroidWall 
features, since most custom ROMs have less stripped-down kernels.

Google for "Huawei U8110 ROM" or something similar and you should find some 
ROMs for your device ;)

Original comment by rodrigo...@gmail.com on 11 Feb 2011 at 12:23

GoogleCodeExporter commented 8 years ago 
Thank's
I'd like to avoid ROM replacing, but where therapy is powerless maybe surgery 
can help. 
:)))

Original comment by Svami.H...@gmail.com on 11 Feb 2011 at 1:51

GoogleCodeExporter commented 8 years ago 
I have the same problem. I am using Darky's ROM  9.2. I don't think this is a 
module missing in the kernel because "iptables -A FORWARD -j LOG" works fine. 
The line is inserted into the FORWARD table and I can see it with "iptables -L 
FORWARD".

In droidwall-reject, the LOG target is here too.

I am not familiar with Android platform (yet). How should the kernel provides 
logs to userspace? Maybe the syslog daemon is missing?

Original comment by vince.be...@gmail.com on 5 Mar 2011 at 2:02

GoogleCodeExporter commented 8 years ago 
Looking at the source code, I see that DroidWall uses dmesg to get kernel logs. 
My dmesg is empty. I should find why...

Original comment by vince.be...@gmail.com on 5 Mar 2011 at 5:24

GoogleCodeExporter commented 8 years ago 
With Darky's ROM 9.5 and using Voodoo kernel, dmesg is not empty anymore.

Original comment by vince.be...@gmail.com on 29 Mar 2011 at 2:09

GoogleCodeExporter commented 8 years ago 
Having this problem on a HTC EVO LTE with the new stock JB OTA.  Is it possible 
to compile the log target as a kernel module and add it to the phone?

Original comment by shad...@gmail.com on 21 Dec 2012 at 8:47