Shorewall users - Jul 2007 - Re : DMZ and LOG

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/

Victor OYETOLA wrote:
> Do you mean that adding  the following line  in
> /etc/shorewall/interfaces is suffiscient?
>   dmz     eth1            81.91.225.255
If the DMZ is the only zone on eth1, yes.
> 
> If  so  how to define dmz   and  another  zone  through  eth1?
Please see http://www.shorewall.net/Multiple_Zones.html for information
about configuring multiple zones on an interface. It makes a difference
whether the zones are nested or disjoint (parallel).

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



-------------------------------------------------------------------------
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/