amartinz / droidwall

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

Log Empty #175

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. install 1.5.2 version
2. configure to use white list
3. select a few application in the white list on 3g 
4. apply filters and activate firewall
5. activate logs
6. use your phone
7. check that some application still work and some are blocked (the job is well 
done)

What is the expected output? What do you see instead?
to have logs in the logfile
- logs for what whas autorised
- logs for what was rejected

instead of having logs, i still have a message : logfile is empty

What version of the product are you using? On what operating system?
droidwall 1.5.2
Galaxy S on 2.1.1 (FROYO.XWJS8)
rooted (super-utilisateur v21.3.6.1) (log of super-utilisateur checked : 
DroidWall is autorised )

Please provide any additional information below.

Original issue reported on code.google.com by jerome.l...@gmail.com on 24 Aug 2011 at 10:54

GoogleCodeExporter commented 9 years ago
seem to be explained by issue 96, but i have an official rom not a tweaekd one 
, that's why i posted these new issue

Original comment by jerome.l...@gmail.com on 24 Aug 2011 at 11:00

GoogleCodeExporter commented 9 years ago
Your ROM (official or not) must support the iptables LOG target in order for 
DroidWall's log to work.
Most official ROMs don't - so the only solution is to flash a new (tweaked) 
kernel.

Sorry, but here is nothing I can do on DroidWall.

Original comment by rodrigo...@gmail.com on 24 Aug 2011 at 1:24