<?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 IPFilter and ifconfig in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ipfilter-and-ifconfig/m-p/3102049#M751668</link>
    <description>Question to you all.  I was talking with some folks on the IPFilter team, and there is a question about how people tend to use it,  specifically with ifconfig.&lt;BR /&gt;&lt;BR /&gt;The current way that an IPFilter module is plumbed into an interface is automatic... which always exacts a &amp;lt;2% performance hit, but also protects the interface (if there are associated  IPFilter rules).&lt;BR /&gt;&lt;BR /&gt;Is it common within your experience to use IPFilter, but not on every interface?&lt;BR /&gt;&lt;BR /&gt;Should the default be to plumb/install it on every interface and take the performance hit if IPfilter is installed?  &lt;BR /&gt;&lt;BR /&gt;How often do you use ifconfig to bring up an interface (vs. net stop/start) vs. editing /etc/rc.config.d/netconf and rebooting?  &lt;BR /&gt;&lt;BR /&gt;Would you expect ifconfig to load IPFilter and protect the interface by default, or use a "-m &lt;MODULE&gt;" switch to load the interface explicitly? What would you prefer?&lt;/MODULE&gt;</description>
    <pubDate>Fri, 24 Oct 2003 19:21:32 GMT</pubDate>
    <dc:creator>Robert Fritz</dc:creator>
    <dc:date>2003-10-24T19:21:32Z</dc:date>
    <item>
      <title>IPFilter and ifconfig</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ipfilter-and-ifconfig/m-p/3102049#M751668</link>
      <description>Question to you all.  I was talking with some folks on the IPFilter team, and there is a question about how people tend to use it,  specifically with ifconfig.&lt;BR /&gt;&lt;BR /&gt;The current way that an IPFilter module is plumbed into an interface is automatic... which always exacts a &amp;lt;2% performance hit, but also protects the interface (if there are associated  IPFilter rules).&lt;BR /&gt;&lt;BR /&gt;Is it common within your experience to use IPFilter, but not on every interface?&lt;BR /&gt;&lt;BR /&gt;Should the default be to plumb/install it on every interface and take the performance hit if IPfilter is installed?  &lt;BR /&gt;&lt;BR /&gt;How often do you use ifconfig to bring up an interface (vs. net stop/start) vs. editing /etc/rc.config.d/netconf and rebooting?  &lt;BR /&gt;&lt;BR /&gt;Would you expect ifconfig to load IPFilter and protect the interface by default, or use a "-m &lt;MODULE&gt;" switch to load the interface explicitly? What would you prefer?&lt;/MODULE&gt;</description>
      <pubDate>Fri, 24 Oct 2003 19:21:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ipfilter-and-ifconfig/m-p/3102049#M751668</guid>
      <dc:creator>Robert Fritz</dc:creator>
      <dc:date>2003-10-24T19:21:32Z</dc:date>
    </item>
  </channel>
</rss>

