<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Question about iptables limit match in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005546#M47829</link>
    <description>I put second script at begining of firts script ang got desired results.&lt;BR /&gt;&lt;BR /&gt;Regards</description>
    <pubDate>Wed, 27 Sep 2006 05:14:22 GMT</pubDate>
    <dc:creator>debian111</dc:creator>
    <dc:date>2006-09-27T05:14:22Z</dc:date>
    <item>
      <title>Question about iptables limit match</title>
      <link>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005541#M47824</link>
      <description>Hi , I have two firewall scripts first and second. When I run FIRST my firewall response on every ping request, and rule &lt;BR /&gt;iptables -A INPUT -p icmp -m limit --limit 1/s --limit-burst 1 -j ACCEPT&lt;BR /&gt;iptables -A INPUT -p icmp -j DROP&lt;BR /&gt;does  not working.&lt;BR /&gt;&lt;BR /&gt;when I run SECOND the above rule works propery.&lt;BR /&gt;I really do not know what is wrong with my first script and why above rule does not working. As you can see the second script is part of first. Just look at these scripts and if you know, and you can see what is wrong write it down. &lt;BR /&gt;Thanks &lt;BR /&gt; &lt;BR /&gt;I did &lt;BR /&gt;iptables -F&lt;BR /&gt;iptables -X for first,&lt;BR /&gt; &lt;BR /&gt;and then run second, and then above rule works &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;#################### FIRST ###################&lt;BR /&gt;iptables -F&lt;BR /&gt;iptables -t nat -F&lt;BR /&gt;iptables -t mangle -F&lt;BR /&gt;&lt;BR /&gt;iptables -X&lt;BR /&gt;iptables -t nat -X&lt;BR /&gt;iptables -t mangle -X&lt;BR /&gt;&lt;BR /&gt;iptables -P INPUT DROP&lt;BR /&gt;iptables -P OUTPUT DROP&lt;BR /&gt;iptables -P FORWARD DROP&lt;BR /&gt;&lt;BR /&gt;iptables -A INPUT -s 127.0.0.1/255.0.0.0 -i eth1 -j ACCEPT&lt;BR /&gt;iptables -A OUTPUT -d 127.0.0.1/255.0.0.0 -o eth1 -j ACCEPT&lt;BR /&gt;&lt;BR /&gt;iptables -A INPUT -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT&lt;BR /&gt;iptables -A OUTPUT -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT&lt;BR /&gt;&lt;BR /&gt;iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE&lt;BR /&gt;&lt;BR /&gt;iptables -A INPUT -p icmp -s 127.0.0.1 -i eth1 -j ACCEPT&lt;BR /&gt;iptables -A INPUT -p icmp -m limit --limit 1/s --limit-burst 1 -j ACCEPT&lt;BR /&gt;iptables -A INPUT -p icmp -j DROP&lt;BR /&gt;iptables -A OUTPUT -p icmp -j ACCEPT&lt;BR /&gt;iptables -A OUTPUT -p tcp --dport 22 -j ACCEPT&lt;BR /&gt;&lt;BR /&gt;##################### FIRST ###################&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;#######################  SECOND ###############&lt;BR /&gt;&lt;BR /&gt;iptables -A INPUT -p icmp -m limit --limit 1/s --limit-burst 1 -j ACCEPT&lt;BR /&gt;iptables -A INPUT -p icmp -j DROP&lt;BR /&gt;&lt;BR /&gt;##################### SECOND #################&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Tue, 26 Sep 2006 12:11:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005541#M47824</guid>
      <dc:creator>debian111</dc:creator>
      <dc:date>2006-09-26T12:11:53Z</dc:date>
    </item>
    <item>
      <title>Re: Question about iptables limit match</title>
      <link>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005542#M47825</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;run iptables -L after running the first script. iptables essentially reads it sections top to bottom. You may see a confict, but in essense, last rule wins.&lt;BR /&gt;&lt;BR /&gt;You may want to reverse the order of the two icmp statements and see if you do better.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 26 Sep 2006 12:25:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005542#M47825</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-09-26T12:25:20Z</dc:date>
    </item>
    <item>
      <title>Re: Question about iptables limit match</title>
      <link>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005543#M47826</link>
      <description>I tryed all, &lt;BR /&gt;I first run script FIRST try rules ( they does not working ) then &lt;BR /&gt;iptables -F&lt;BR /&gt;iptables -X&lt;BR /&gt;and thed SECOND script, there is no influence of first script to second, they are independent of each other. &lt;BR /&gt;Just one scrip in time of testing.&lt;BR /&gt;REgards</description>
      <pubDate>Tue, 26 Sep 2006 13:00:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005543#M47826</guid>
      <dc:creator>debian111</dc:creator>
      <dc:date>2006-09-26T13:00:15Z</dc:date>
    </item>
    <item>
      <title>Re: Question about iptables limit match</title>
      <link>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005544#M47827</link>
      <description>From where are you testing the ping? If localhost, then there is the problem, because the rules are checked in order, and localhost in FIRST has ACCEPT as rule.</description>
      <pubDate>Tue, 26 Sep 2006 15:51:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005544#M47827</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-09-26T15:51:33Z</dc:date>
    </item>
    <item>
      <title>Re: Question about iptables limit match</title>
      <link>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005545#M47828</link>
      <description>Hi Debian111,&lt;BR /&gt;&lt;BR /&gt;Easiest way to trece what's wrong is, comment out (put # before the rule) one rule at a time and then run the script. You will be able to find out exactly which rule is allowing ICMP requests without limit.&lt;BR /&gt;&lt;BR /&gt;If you are pinging from local machine, no limit will work, because you have accpted all input &amp;amp; output on localhost.</description>
      <pubDate>Tue, 26 Sep 2006 23:52:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005545#M47828</guid>
      <dc:creator>kcpant</dc:creator>
      <dc:date>2006-09-26T23:52:10Z</dc:date>
    </item>
    <item>
      <title>Re: Question about iptables limit match</title>
      <link>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005546#M47829</link>
      <description>I put second script at begining of firts script ang got desired results.&lt;BR /&gt;&lt;BR /&gt;Regards</description>
      <pubDate>Wed, 27 Sep 2006 05:14:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005546#M47829</guid>
      <dc:creator>debian111</dc:creator>
      <dc:date>2006-09-27T05:14:22Z</dc:date>
    </item>
    <item>
      <title>Re: Question about iptables limit match</title>
      <link>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005547#M47830</link>
      <description>Thanks</description>
      <pubDate>Wed, 27 Sep 2006 05:15:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/question-about-iptables-limit-match/m-p/5005547#M47830</guid>
      <dc:creator>debian111</dc:creator>
      <dc:date>2006-09-27T05:15:03Z</dc:date>
    </item>
  </channel>
</rss>

