Tom Eastep wrote:
> Steven Jan Springl wrote:
>> Tom
>>
>> Having never used IPSEC, I don't know if this is a bug or I'm missing 
>> something.
>>
>> Masq file entry:
>>
>>      eth0  192.168.0.0/16  -  -  -  strict,next
>>
>> produces error:
>>
>> iptables-restore v1.3.6: policy match: empty policy element
>>
>> Coding 'strict,next' in the zones file works.
>>
> 
> 'strict' and 'next' are only applicable when multiple policies are strung
> together. I'll investigate what is going on in the zones file since
> "strict,next" shouldn't work there either.

Did you just use "strict,next" and nothing else in the zones file? That
shouldn't work either according to the rules generated.

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ [EMAIL PROTECTED]
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key

Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel

Reply via email to