<?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: Iptables in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/iptables/m-p/3772254#M83751</link>
    <description>Shalom Maaz,&lt;BR /&gt;&lt;BR /&gt;Case 1,&lt;BR /&gt;&lt;BR /&gt;The first statement permits persistent connections, which is needed for a session to maintain a connection.&lt;BR /&gt;&lt;BR /&gt;To do it only on port 80 is not exactly standard.&lt;BR /&gt;&lt;BR /&gt;Usually you permit persistent connections for the entire firewall which will apply on any ports that are open. Most port 80 applications will also need port 443 for example.&lt;BR /&gt;&lt;BR /&gt;I think if you conduct testing from outside your firewall you will find the behavior in Case 1 and Case 2 is different. The sockets should be different.&lt;BR /&gt;&lt;BR /&gt;do a netstat -an and after some testing and see what happens.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Sun, 16 Apr 2006 04:56:32 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2006-04-16T04:56:32Z</dc:date>
    <item>
      <title>Iptables</title>
      <link>https://community.hpe.com/t5/operating-system-linux/iptables/m-p/3772253#M83750</link>
      <description>hello Dear GURUS&lt;BR /&gt;&lt;BR /&gt;0, iptables -P INPUT DROP&lt;BR /&gt;&lt;BR /&gt;Case 1&lt;BR /&gt;------&lt;BR /&gt;I found no difference b/w two&lt;BR /&gt;&lt;BR /&gt;1, iptables -A INPUT -m state --state NEW -p tcp --dport 80 -j ACCEPT&lt;BR /&gt;   iptables -A INPUT -m state --state NEW -j DROP &lt;BR /&gt;and&lt;BR /&gt;2, iptables -A INPUT -p tcp --dport 80 -j ACCEPT&lt;BR /&gt;   iptables -A INPUT -j DROP&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Case 2&lt;BR /&gt;------&lt;BR /&gt;I found no difference b/w two&lt;BR /&gt;&lt;BR /&gt;1, iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT&lt;BR /&gt;   iptables -A INPUT -m state --state NEW -j DROP  &lt;BR /&gt;and&lt;BR /&gt;2, iptables -A INPUT ! --syn -j ACCEPT&lt;BR /&gt;   iptables -A INPUT --syn -j DROP&lt;BR /&gt;&lt;BR /&gt;Any Comment...Recommendations...Suggestions..Explanations will be highly appreciated&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Maaz</description>
      <pubDate>Sun, 16 Apr 2006 03:06:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/iptables/m-p/3772253#M83750</guid>
      <dc:creator>Maaz</dc:creator>
      <dc:date>2006-04-16T03:06:49Z</dc:date>
    </item>
    <item>
      <title>Re: Iptables</title>
      <link>https://community.hpe.com/t5/operating-system-linux/iptables/m-p/3772254#M83751</link>
      <description>Shalom Maaz,&lt;BR /&gt;&lt;BR /&gt;Case 1,&lt;BR /&gt;&lt;BR /&gt;The first statement permits persistent connections, which is needed for a session to maintain a connection.&lt;BR /&gt;&lt;BR /&gt;To do it only on port 80 is not exactly standard.&lt;BR /&gt;&lt;BR /&gt;Usually you permit persistent connections for the entire firewall which will apply on any ports that are open. Most port 80 applications will also need port 443 for example.&lt;BR /&gt;&lt;BR /&gt;I think if you conduct testing from outside your firewall you will find the behavior in Case 1 and Case 2 is different. The sockets should be different.&lt;BR /&gt;&lt;BR /&gt;do a netstat -an and after some testing and see what happens.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Sun, 16 Apr 2006 04:56:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/iptables/m-p/3772254#M83751</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-04-16T04:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: Iptables</title>
      <link>https://community.hpe.com/t5/operating-system-linux/iptables/m-p/3772255#M83752</link>
      <description>I think I should elaborate more&lt;BR /&gt;for case1&lt;BR /&gt;---------&lt;BR /&gt;Say I m running web server on my linux machine, which is also connected to the Internet, now I want that only http trafic is allowd from the Internet, and else will be blocked, and *ALSO* I can browse/surf the Internet too. To acheive this target I have used both i.e 1 and 2 separately and both work fine.&lt;BR /&gt;Thats why I m asking that Is there any goog/strong diff b/w the two ? Or simply these(1&amp;amp;2) are simply two diff ways to acheive the target ?&lt;BR /&gt;&lt;BR /&gt;for case2&lt;BR /&gt;---------&lt;BR /&gt;this is a simple linux workstation connected to the Internet via modem&lt;BR /&gt;No traffic from Internet will be allowed, but Internet Browsing, chatting etc will be allowed .. or simply outgoing trafic is allowed. To acheive this target I used both 1 and 2 Separately, and they both works for me &lt;BR /&gt;Thats why I m asking that Is there any goog/strong diff b/w the two ? Or simply these(1&amp;amp;2) are simply two diff ways to acheive the target ?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Maaz</description>
      <pubDate>Sun, 16 Apr 2006 05:34:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/iptables/m-p/3772255#M83752</guid>
      <dc:creator>Maaz</dc:creator>
      <dc:date>2006-04-16T05:34:37Z</dc:date>
    </item>
    <item>
      <title>Re: Iptables</title>
      <link>https://community.hpe.com/t5/operating-system-linux/iptables/m-p/3772256#M83753</link>
      <description>Shalom again Maaz,&lt;BR /&gt;&lt;BR /&gt;In both cases, the first method seems better.&lt;BR /&gt;&lt;BR /&gt;I'm thinking you may want a script that helps with this. It relies on come configuration tables to let you decide open ports both to the net and the lan/dmz and such.&lt;BR /&gt;&lt;BR /&gt;Let me know if such a package will help. It generates iptables code.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Sun, 16 Apr 2006 06:38:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/iptables/m-p/3772256#M83753</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-04-16T06:38:14Z</dc:date>
    </item>
    <item>
      <title>Re: Iptables</title>
      <link>https://community.hpe.com/t5/operating-system-linux/iptables/m-p/3772257#M83754</link>
      <description>Thanks SEP for help&lt;BR /&gt;Yes I m looking forward for such a PACKAGE&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Maaz</description>
      <pubDate>Sun, 16 Apr 2006 12:37:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/iptables/m-p/3772257#M83754</guid>
      <dc:creator>Maaz</dc:creator>
      <dc:date>2006-04-16T12:37:28Z</dc:date>
    </item>
    <item>
      <title>Re: Iptables</title>
      <link>https://community.hpe.com/t5/operating-system-linux/iptables/m-p/3772258#M83755</link>
      <description>Hi Maaz&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.hpux.ws/fireall.tar.gz" target="_blank"&gt;http://www.hpux.ws/fireall.tar.gz&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;This may be a can of worms.&lt;BR /&gt;&lt;BR /&gt;That tar far contains a firewall code generator.&lt;BR /&gt;&lt;BR /&gt;It expects a configuration file at /etc/rc.config.d/firewall.update&lt;BR /&gt;&lt;BR /&gt;You may nodify the location. &lt;BR /&gt;&lt;BR /&gt;It expects other configuration files in /etc/iptables&lt;BR /&gt;&lt;BR /&gt;It is highly flexible and can generate a fierwall based on any port setup you wish.&lt;BR /&gt;&lt;BR /&gt;The variables are aptly named and ip lists are just that valid ip addresses that iptables can read.&lt;BR /&gt;&lt;BR /&gt;It may be overengineered, but I'm prepared to answer questions on it.&lt;BR /&gt;&lt;BR /&gt;SEP&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 16 Apr 2006 16:48:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/iptables/m-p/3772258#M83755</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-04-16T16:48:51Z</dc:date>
    </item>
  </channel>
</rss>

