Astaro User Bulletin Board
Go Back   Astaro User Bulletin Board > Astaro Gateway Products > Network Security: Firewall, NAT, QoS, IPS and more

Welcome to the Astaro User Bulletin Board.
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 02-16-2004, 08:52 AM
Member
 
Join Date: Nov 2003
Posts: 32
Default policy not work

Because our intranet have a lot of attack and ASL is busy to record these log, so ASL's CPU usage is full. I want to set any->any->any->drop under a policy that allow HTTP,SMTP,POP3 etc.But I found there are still a lot of drop log into live log, it means the drop policy don't work. If I set a policy to drop special ports such as 135,137,139 or 445 ports, it works. I don't know why, pls help me. [img]/images/graemlins/confused.gif[/img]
Reply With Quote
  #2 (permalink)  
Old 02-16-2004, 08:58 AM
Wizard
 
Join Date: Jun 2003
Location: geocenter
Posts: 623
Default Re: policy not work

'ANY ANY ANY DROP' applies to the forwarding chain and this is why packets directed to the firewall interfaces are still being logged.

Test a rule like 'ANY ANY IP_of_FW', you should enable this for testing only. Better drop only those ports which appear in the log frequently.

Greetings
cyclops
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 09:11 AM.

 

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.


These pages are specifically maintained for the discussion of firewall issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases. issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases.