search

504109543 / droidwall

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

Logging is enabled but log reports to be empty after firewall successfully blocks outgoing connections per saved rules. #180

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Enabled logging
2. Blocked certain applications via blacklist
3. Attempted to connect to remote servers with blocked applications

What is the expected output? What do you see instead?
Clicking the "show log" option returns a popup dialog box stating "log is empty"

What version of the product are you using? On what operating system?
v1.5.2 on 2.2.2 Froyo

Please provide any additional information below.
When viewing the current rule set from the UI, I've also noticed that at the 
top of the rules list is a repeating string of the following error: "FATAL: 
Could not load /lib/modules/2.6.32.9-00007-g527fe10/modules.dep: No such file 
or directory". I'm unsure if this is related to the absence of log data.

A screenshot is available if needed.

Original issue reported on code.google.com by xallara...@gmail.com on 12 Sep 2011 at 8:13

GoogleCodeExporter commented 8 years ago 
There are two possible causes for this problem:
1. Your kernel does not support "dmesg"
and/or
2. Your kernel does not support the netfilter LOG target

Unfortunately, there is nothing I can don on DroidWall to make the logs work... 
:(

You can try to issue the "dmesg" command on a terminal to see if it is 
supported...
Sorry if I can't help you much.

Original comment by rodrigo...@gmail.com on 12 Sep 2011 at 8:28

GoogleCodeExporter commented 8 years ago 
Thank you for the response. My kernel *does* support "dmesg". I just
tried *dmesg
| grep <various strings>* in a terminal session and my device returned all
related messages just fine.

Can you please at least tell me if you think the "no such file or directory"
/lib/ errors are related to this log failure issue?

Original comment by xallara...@gmail.com on 12 Sep 2011 at 9:03

GoogleCodeExporter commented 8 years ago 
Hello, so the most probable cause is that the netfilter LOG target is not 
supported.
You can probably confirm this by using the "show rules" menu on DroidWall... 
look for a "LOG" target on the rules output (there will probably be none on 
your device).

The errors you described do not affect DroidWall's behavior. In fact, they 
occur on most devices...
They happen because iptables attempt to do a modprobe on every call (and 
DroidWall calls iptables many times, so this causes many errors to be output.)

Original comment by rodrigo...@gmail.com on 13 Sep 2011 at 12:41