Originally Posted by
jre
Just make sure that firestarter is started before MoBlock. Then go with the Moblock 0.9 default settings (i.e. FONT="Courier New"]IPTABLES_SETTINGS="1"[/FONT] and MARKing on). Every firestarter change then requires a moblock-control restart.
I have just added informations to post #1 how you can verify correct settings.
If the above doesn't work for you you can go with the other old instructions.
Finally you may try this (not tested, please give feedback if you do this):
Keep the MoBlock configuration as it is. In the firehol.conf add as last line moblock-control restart.
IIRC firehol works that way that commands in its conf are simply executed, so this way you can make sure that MoBlock is restarted after every firehol change (firehol purges all other iptables rules).
Is there a default firehol example file ? I have the old default settings like
Code:
iptables --new moblock
iptables -A moblock -j NFQUEUE
and i moblock
Code:
IPTABLES_SETTINGS="0"
IPTABLES_ACTIVATION="0"
but I saw that now recommend iptables_settings=1. I tried both but when i do the moblock-control test all I get are fails. Also tail -f /var/log/moblock/moblock.log doesn't give the ips address it's blocking. How can i check if moblock-control is up and running
Bookmarks