Well, I think the same and that´s why I have a lab ready to go.-
Can I update my firewall 3 to 4.0.4? or its complicated?
On 10/10/07, Tom Eastep <[EMAIL PROTECTED]> wrote:
>
> Nico Pagliaro wrote:
> >
> >
> >
> > Ok, I am sending the sump file, but look what I have tested. I put
> > in the policy file
> > nic all ACCEPT info
> >
> > and now works!! so I think that my problem is that the policy
> > nic net ACCEPT doesnt work! so my net zone its ok????
>
> It looks like the 74.53.xxx.xxx addresses are in the 'adm' zone, not the
> 'net' zone.
>
> As an aside, with your configuration you *really* should update to
> Shorewall
> 3.4 or later (4.0.4 with Shorewall-perl preferred) and set OPTIMIZE=1 in
> shorewall.conf. Your ruleset would be a lot smaller.
>
> -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
>
>
> -------------------------------------------------------------------------
> 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
>
>
>
-------------------------------------------------------------------------
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
