hello Tom

>Another very likely cause is that Shorewall-shell is generating a pkttype
>test to identify multicast packets. This can be unreliable and can be
>avoided by setting PKTTYPE=No in shorewall.conf.

After using  PKTTYPE=No in shorewall.conf ,  my syslog is clean now.

Do you mean that adding  the following line  in  /etc/shorewall/interfaces is 
suffiscient?
  dmz     eth1            81.91.225.255

If  so  how to define dmz   and  another  zone  through  eth1? 
thank you very much 








      
_____________________________________________________________________________ 
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail 
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to