<?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: restricting network access on two lan cards in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/restricting-network-access-on-two-lan-cards/m-p/2759052#M583428</link>
    <description>It's correct that inetd.sec does not support "per interface" filtering, but it works for me because I know what subnets are are connected to this lan card.&lt;BR /&gt;&lt;BR /&gt;So I did in inetd.sec:&lt;BR /&gt;&lt;BR /&gt;telnet deny 10.*&lt;BR /&gt;http   deny  193.*&lt;BR /&gt;&lt;BR /&gt;This enables me to block telnet requests arriving at lan card 10.43.181.222 and http requests arriving at 193.16.33.253&lt;BR /&gt;&lt;BR /&gt;But I'll have a look at your recomended links.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Rainer&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;                                         &lt;BR /&gt;                                         &lt;BR /&gt;</description>
    <pubDate>Tue, 09 Jul 2002 14:12:58 GMT</pubDate>
    <dc:creator>Rainer von Bongartz</dc:creator>
    <dc:date>2002-07-09T14:12:58Z</dc:date>
    <item>
      <title>restricting network access on two lan cards</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restricting-network-access-on-two-lan-cards/m-p/2759047#M583423</link>
      <description>&lt;BR /&gt;My hosts uses multiple lan cards with ip addresses in different networks&lt;BR /&gt;&lt;BR /&gt;lan0 : ip a.b.c.d&lt;BR /&gt;lan1:  ip w..x.y.z&lt;BR /&gt;&lt;BR /&gt;can I restrict different network access to this addresses, i.e. telnet should be allowed to a.b.c.d only while http should only be allowed to w.x.y.z&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Rainer&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Jul 2002 06:04:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restricting-network-access-on-two-lan-cards/m-p/2759047#M583423</guid>
      <dc:creator>Rainer von Bongartz</dc:creator>
      <dc:date>2002-07-08T06:04:21Z</dc:date>
    </item>
    <item>
      <title>Re: restricting network access on two lan cards</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restricting-network-access-on-two-lan-cards/m-p/2759048#M583424</link>
      <description>Hi Rainer,&lt;BR /&gt;&lt;BR /&gt;You can restrict the traffic from your apache web server to certain IP's from within your apache httpd.conf file. Have a look here for &lt;BR /&gt;virtual hosts.&lt;BR /&gt;&lt;A href="http://httpd.apache.org/docs/misc/FAQ.html" target="_blank"&gt;http://httpd.apache.org/docs/misc/FAQ.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If you wish to restrict telnet you will need to use something like ssh and have telnet turned off. &lt;BR /&gt;&lt;BR /&gt;Michael</description>
      <pubDate>Mon, 08 Jul 2002 06:45:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restricting-network-access-on-two-lan-cards/m-p/2759048#M583424</guid>
      <dc:creator>Michael Tully</dc:creator>
      <dc:date>2002-07-08T06:45:42Z</dc:date>
    </item>
    <item>
      <title>Re: restricting network access on two lan cards</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restricting-network-access-on-two-lan-cards/m-p/2759049#M583425</link>
      <description>you can also look at inetd.sec: try man inetd.sec&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;inetd.sec(4)                                                   inetd.sec(4)&lt;BR /&gt;&lt;BR /&gt; NAME&lt;BR /&gt;      inetd.sec - optional security file for inetd&lt;BR /&gt;&lt;BR /&gt; DESCRIPTION&lt;BR /&gt;      When inetd accepts a connection from a remote system, it checks the&lt;BR /&gt;      address of the host requesting the service against the list of hosts&lt;BR /&gt;      to be allowed or denied access to the specific service (see&lt;BR /&gt;      inetd(1M)).  The file inetd.sec allows the system administrator to&lt;BR /&gt;      control which hosts (or networks in general) are allowed to use the&lt;BR /&gt;      system remotely.  This file constitutes an extra layer of security in&lt;BR /&gt;      addition to the normal checks done by the services.  It precedes the&lt;BR /&gt;      security of the servers; that is, a server is not started by the&lt;BR /&gt;      Internet daemon unless the host requesting the service is a valid host&lt;BR /&gt;      according to inetd.sec.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Jul 2002 07:09:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restricting-network-access-on-two-lan-cards/m-p/2759049#M583425</guid>
      <dc:creator>Scott Van Kalken</dc:creator>
      <dc:date>2002-07-08T07:09:55Z</dc:date>
    </item>
    <item>
      <title>Re: restricting network access on two lan cards</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restricting-network-access-on-two-lan-cards/m-p/2759050#M583426</link>
      <description>ok , the simplest way is indeed inetd.sec&lt;BR /&gt;just add a line like :&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;telnet allow ip-range&lt;BR /&gt;&lt;BR /&gt;http allow ip-range &lt;BR /&gt;&lt;BR /&gt;will effectively block any incomming request on that process to ip adresses comming from a different ip range , the allow hold an implicit deny any other range will be refused , however if you also want to prevent outgoing telnets (I don't think that is the case) you need a firewall type of applications which closes of the socket for telnet and http for defined ranges in outgoing traffic</description>
      <pubDate>Mon, 08 Jul 2002 08:13:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restricting-network-access-on-two-lan-cards/m-p/2759050#M583426</guid>
      <dc:creator>sven verhaegen</dc:creator>
      <dc:date>2002-07-08T08:13:38Z</dc:date>
    </item>
    <item>
      <title>Re: restricting network access on two lan cards</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restricting-network-access-on-two-lan-cards/m-p/2759051#M583427</link>
      <description>I don't think inetd.sec supports "per interface" filtering.  httpd.conf virtual address setup is rather arcane, and won't meet your telnet need, as noted.&lt;BR /&gt;&lt;BR /&gt;To have the box self-defend, you'll probably need a package like IPF (&lt;A href="http://coombs.anu.edu.au/~avalon/ip-filter.html)" target="_blank"&gt;http://coombs.anu.edu.au/~avalon/ip-filter.html)&lt;/A&gt;&lt;BR /&gt;or you might be able to do what you want with TCPWrappers&lt;BR /&gt;(&lt;A href="ftp://ftp.porcupine.org/pub/security)" target="_blank"&gt;ftp://ftp.porcupine.org/pub/security)&lt;/A&gt;&lt;BR /&gt;Depending on what sort of router you have, the easiest thing to do might be to have the router do the filtering.</description>
      <pubDate>Tue, 09 Jul 2002 13:59:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restricting-network-access-on-two-lan-cards/m-p/2759051#M583427</guid>
      <dc:creator>W.C. Epperson</dc:creator>
      <dc:date>2002-07-09T13:59:21Z</dc:date>
    </item>
    <item>
      <title>Re: restricting network access on two lan cards</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restricting-network-access-on-two-lan-cards/m-p/2759052#M583428</link>
      <description>It's correct that inetd.sec does not support "per interface" filtering, but it works for me because I know what subnets are are connected to this lan card.&lt;BR /&gt;&lt;BR /&gt;So I did in inetd.sec:&lt;BR /&gt;&lt;BR /&gt;telnet deny 10.*&lt;BR /&gt;http   deny  193.*&lt;BR /&gt;&lt;BR /&gt;This enables me to block telnet requests arriving at lan card 10.43.181.222 and http requests arriving at 193.16.33.253&lt;BR /&gt;&lt;BR /&gt;But I'll have a look at your recomended links.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Rainer&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;                                         &lt;BR /&gt;                                         &lt;BR /&gt;</description>
      <pubDate>Tue, 09 Jul 2002 14:12:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restricting-network-access-on-two-lan-cards/m-p/2759052#M583428</guid>
      <dc:creator>Rainer von Bongartz</dc:creator>
      <dc:date>2002-07-09T14:12:58Z</dc:date>
    </item>
  </channel>
</rss>

