Re: Problem Starting Shorewall - ULOG problem

Mekabe Ramein
Thu, 06 Aug 2009 18:46:10 -0000

On Thu, Aug 6, 2009 at 12:46 AM, Tom Eastep<teastep@shorewall.net>
wrote:
> Mekabe Ramein wrote:
>
>>
>> Thank you. It really solved the problem. I assume this patch will be
>>  included in the final release, right ?
>
> We distribute Betas and Release Candidates in order to identify *and
> remove* defects before final.
>
>> Btw, ACCEPT rule with ULOG parameter was being accepted while
>> REDIRECT was not.
>
> I know. If you read
>
http://www1.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-RC2/known_problems.txt,
> you will find this characterization of the defect:
>
> 1)  A nat rule (DNAT, REDIRECT, etc.) which changes the destination
>    port number and that has logging specified can cause invalid
>    iptables input to be generated.
>
>    Example of rule:
>
>            REDIRECT:ULOG   wall    82      tcp     80
>
>    Example of error message:
>
>       iptables v1.3.5: Need TCP or UDP with port specification
>        Try `iptables -h'' or ''iptables --help''
for more information.
>        ERROR: Command "/sbin/iptables -A log0 -j REDIRECT --to-port
>        82" Failed
>
> -Tom
> --
> Tom Eastep

Thanks for the detailed explanation.
What about the following warning message:

WARNING: RFC1918_LOG_LEVEL=ULOG ignored. The ''norfc1918''
interface/host option is no longer supported

Regards.