<?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: Ipchains rules in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/ipchains-rules/m-p/2563351#M89539</link>
    <description>Victor,&lt;BR /&gt;&lt;BR /&gt;I am not sure about using ipchains to restrict these services but you can combine tcp wrappers and utilize the hosts.allow and hosts.deny files to restrict or disable access to services. &lt;BR /&gt;&lt;BR /&gt;Entering something like the example below to your hosts.allow file to give access to telnet and ftp:&lt;BR /&gt;&lt;BR /&gt;in.telnetd: 192.168.1.1&lt;BR /&gt;in.ftpd: 192.168.1.1&lt;BR /&gt;&lt;BR /&gt;hosts.deny has the same syntax except it is used to restrict access to the services.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 08 Aug 2001 20:40:40 GMT</pubDate>
    <dc:creator>Jeffrey S. Sims</dc:creator>
    <dc:date>2001-08-08T20:40:40Z</dc:date>
    <item>
      <title>Ipchains rules</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ipchains-rules/m-p/2563350#M89538</link>
      <description>I have Redhat 7.1, an only have one ethernet card and one ip address, I try to filter telnet and ftp to work only with one remote pc, allow www for all and deny any other port, but when I apply the rules the telnet, ftp and www don't work for any pc or local, the icmp rules work good, there are the rules:&lt;BR /&gt;ipchains -A input -p icmp -s &lt;IP pc=""&gt; -j ACCEPT&lt;BR /&gt;ipchains -A input -p icmp -j DENY&lt;BR /&gt;ipchains -A input -p tcp -s &lt;IP pc=""&gt; ftp -j ACCEPT&lt;BR /&gt;ipchains -A input -p tcp -s &lt;IP pc=""&gt; ftp-data -j ACCEPT&lt;BR /&gt;ipchains -A input -p tcp -s &lt;IP pc=""&gt; telnet -j ACCEPT&lt;BR /&gt;ipchains -A input -p tcp -s 0.0.0.0/0 www -d 0.0.0.0/0 www -j ACCEPT&lt;BR /&gt;ipchains -A input -j DENY -l&lt;BR /&gt;&lt;/IP&gt;&lt;/IP&gt;&lt;/IP&gt;&lt;/IP&gt;</description>
      <pubDate>Wed, 08 Aug 2001 15:55:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ipchains-rules/m-p/2563350#M89538</guid>
      <dc:creator>Victor Salvador</dc:creator>
      <dc:date>2001-08-08T15:55:57Z</dc:date>
    </item>
    <item>
      <title>Re: Ipchains rules</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ipchains-rules/m-p/2563351#M89539</link>
      <description>Victor,&lt;BR /&gt;&lt;BR /&gt;I am not sure about using ipchains to restrict these services but you can combine tcp wrappers and utilize the hosts.allow and hosts.deny files to restrict or disable access to services. &lt;BR /&gt;&lt;BR /&gt;Entering something like the example below to your hosts.allow file to give access to telnet and ftp:&lt;BR /&gt;&lt;BR /&gt;in.telnetd: 192.168.1.1&lt;BR /&gt;in.ftpd: 192.168.1.1&lt;BR /&gt;&lt;BR /&gt;hosts.deny has the same syntax except it is used to restrict access to the services.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 08 Aug 2001 20:40:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ipchains-rules/m-p/2563351#M89539</guid>
      <dc:creator>Jeffrey S. Sims</dc:creator>
      <dc:date>2001-08-08T20:40:40Z</dc:date>
    </item>
    <item>
      <title>Re: Ipchains rules</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ipchains-rules/m-p/2563352#M89540</link>
      <description>The input rules should be &lt;BR /&gt;-d &lt;LOCAL-IP&gt; &lt;SERVICE&gt; -s &lt;PC-IP&gt;&lt;BR /&gt;not &lt;BR /&gt;-s &lt;PC-IP&gt; &lt;SERVICE&gt; &lt;BR /&gt;&lt;BR /&gt;I think ftp-data is the exception.  Check your log file&lt;BR /&gt;for failures. &lt;BR /&gt;&lt;BR /&gt;The tcp-wrappers is a good way to further protect&lt;BR /&gt;services run through inetd (usually not http).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SERVICE&gt;&lt;/PC-IP&gt;&lt;/PC-IP&gt;&lt;/SERVICE&gt;&lt;/LOCAL-IP&gt;</description>
      <pubDate>Thu, 09 Aug 2001 01:41:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ipchains-rules/m-p/2563352#M89540</guid>
      <dc:creator>Bill Thorsteinson</dc:creator>
      <dc:date>2001-08-09T01:41:15Z</dc:date>
    </item>
    <item>
      <title>Re: Ipchains rules</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ipchains-rules/m-p/2563353#M89541</link>
      <description>Dude. ipchains sucks!&lt;BR /&gt;&lt;BR /&gt;iptables Rulez!&lt;BR /&gt;&lt;BR /&gt;(Sorry, I couldn't resist.)</description>
      <pubDate>Thu, 16 Aug 2001 05:21:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ipchains-rules/m-p/2563353#M89541</guid>
      <dc:creator>Elliot Nesterman</dc:creator>
      <dc:date>2001-08-16T05:21:06Z</dc:date>
    </item>
  </channel>
</rss>

