[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.
08/22/2009 at 02:49PM PDT, ID: 24673984
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
9.4

iptables comments and preventing iptables.log getting too big

Asked by shaunwingin in Linux Network Security, IP Tables/IP Chains

Say, Any comments appreciated as regards my iptable below as regards its security etc. Also how can I prevent the logfile from being flooded and growing too big too quick?
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [42:27102]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m tcp --dport 22 -m state --state NEW -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 25 -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m tcp --dport 1022 -m state --state NEW -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m tcp --dport 1023 -m state --state NEW -j ACCEPT
-A RH-Firewall-1-INPUT -d 141.1.39.6 -p tcp -m tcp --dport 5060 -m state --state NEW -j ACCEPT
-A RH-Firewall-1-INPUT -d 141.1.39.6 -p udp -m udp --dport 10000:20000 -m state --state NEW -j ACCEPT
-A RH-Firewall-1-INPUT -d 141.1.39.6 -p udp -m state --state NEW -m udp --dport 4569 -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp ! --tcp-flags FIN,SYN,RST,ACK SYN -j LOG --log-prefix "ALERT,NewNotSyn from eth:"
-A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp ! --tcp-flags FIN,SYN,RST,ACK SYN -j DROP
-A RH-Firewall-1-INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -j LOG --log-prefix "ALERT,NEW FROM eth DROP:"
-A RH-Firewall-1-INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -j DROP
-A RH-Firewall-1-INPUT -p icmp -m icmp --icmp-type 8 -j LOG --log-prefix "ALERT PING DROP:"
-A RH-Firewall-1-INPUT -p icmp -m icmp --icmp-type 8 -j DROP
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
-A RH-Firewall-1-INPUT -j LOG --log-prefix "ALERT, REST INPUT DROP:"
-A RH-Firewall-1-INPUT -j DROP
COMMIT
# Completed on Sat Aug 22 23:45:37 2009
# Generated by iptables-save v1.3.5 on Sat Aug 22 23:45:37 2009
*nat
:PREROUTING ACCEPT [1:48]
:POSTROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
COMMIT
# Completed on Sat Aug 22 23:45:37 2009
# Generated by iptables-save v1.3.5 on Sat Aug 22 23:45:37 2009
*mangle
:PREROUTING ACCEPT [31:2417]
:INPUT ACCEPT [31:2417]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [42:27102]
:POSTROUTING ACCEPT [42:27102]
#DSCP Marking
-A OUTPUT -p udp -m udp --sport 4569 -j DSCP --set-dscp 0x2e
-A OUTPUT -p udp -m udp --sport 10000:20000 -j DSCP --set-dscp 0x2e
-A OUTPUT -p udp -m udp --sport 5060 -j DSCP --set-dscp 0x2e
COMMIT
[+][-]08/23/09 03:57 PM, ID: 25164640

Assisted solutions are selected by the member who asked the question as a comment that contributed to their question's solution.

Start your 30-day free trial to view this Assisted Solution or ask the Experts your question.

 
[+][-]08/24/09 12:10 AM, ID: 25166105

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]08/24/09 12:27 AM, ID: 25166160

Assisted solutions are selected by the member who asked the question as a comment that contributed to their question's solution.

Start your 30-day free trial to view this Assisted Solution or ask the Experts your question.

 
[+][-]08/24/09 01:00 AM, ID: 25166295

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Linux Network Security, IP Tables/IP Chains
Sign Up Now!
Solution Provided By: noci
Participating Experts: 2
Solution Grade: A
 
 
 
Loading Advertisement...
20090824-EE-VQP-74 - Hierarchy / EE_QW_3_20080625