search for: report_cap

From: non-list-member With shorewall 2.0.2c on a kernel 2.6.5 I am finding that the report_capabilities() is being called before load_kernel_modules(). This leads to some problems, one of which is that the reported capabilities is wrong on the first "start" command. If you then "stop" then "start", things go better (now that the kernel modules are loaded)....

Robin Lynn Frank wrote: > I have an entire /8 blacklisted. The problem is there is a single IP in > it I want to exempt from this. Searching the web site, I note there > used to be (circa version 1.3) a whitelist feature, but I couldn''t find > a simple solution to what I want to do. > > What would be the bes/easiest way to accomplish this? I can''t think of a

...save_command loadmodule ip_set_portmap + echo loadmodule ip_set_portmap + read command + case "$command" in + read command + save_command __EOF__ + echo __EOF__ + save_command '''' + echo '''' + echo Initializing... Initializing... + initialize_netfilter + report_capabilities + echo ''Shorewall has detected the following iptables/netfilter capabilities:'' Shorewall has detected the following iptables/netfilter capabilities: + report_capability NAT Yes + local setting= + ''['' xYes = xYes '']'' + setting=Available...

I am getting the following message when Shorewall stops can anybody shed any light on this message and where I should be looking? Thanks root@bobshost:~# shorewall stop Loading /usr/share/shorewall/functions... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... Loading Modules... Stopping Shorewall...Processing /etc/shorewall/stop ... IP Forwarding Enabled