<?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: promisconlevel: UNIX error - Device busy in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/promisconlevel-unix-error-device-busy/m-p/6960511#M528462</link>
    <description>&lt;P&gt;"lan900" sounds like an aggregate, VLAN or other virtual construct, not a real physical NIC. You might be able to use the promiscuous mode on physical NICs only.&lt;/P&gt;&lt;P&gt;But do you really need promiscuous mode?&lt;/P&gt;&lt;P&gt;If you are trying to get a dump of network traffic that would already be received by your system without promiscuous mode (i.e. either unicast packetss addressed to that system, or broadcast packets) then you don't need promiscuous mode. at all.&lt;/P&gt;&lt;P&gt;If you are trying to diagnose misaddressed packets, multicasts or something more complicated, then you might need promiscuous mode.&lt;/P&gt;&lt;P&gt;If you add the option '-p' to your tcpdump command line, it will skip setting the interface to promiscuous mode and just dump the regular traffic.. For most application-level troubleshooting, that will be enough.&lt;/P&gt;</description>
    <pubDate>Wed, 26 Apr 2017 14:20:02 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2017-04-26T14:20:02Z</dc:date>
    <item>
      <title>promisconlevel: UNIX error - Device busy</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/promisconlevel-unix-error-device-busy/m-p/6956048#M528461</link>
      <description>&lt;P&gt;Hi ,&amp;nbsp;&lt;/P&gt;&lt;P&gt;tcpdump is not working (tcpdump -XX -i lan900). Error is :&lt;/P&gt;&lt;P&gt;&amp;nbsp;tcpdump: recv_ack: promisconlevel: UNIX error - Device busy&lt;/P&gt;&lt;P&gt;i find using&amp;nbsp;promiscuous mode other process, but i didn't found. And i &amp;nbsp;reinstall tcpdump and reboot server. I didn't fix this.&amp;nbsp;&lt;/P&gt;&lt;P&gt;my server's version is hp-ux 11.31&amp;nbsp;&lt;/P&gt;&lt;P&gt;This command ( tcpdump -XX -i lan900 ) working other hp-ux servers.&lt;/P&gt;&lt;P&gt;How do i fix this error ???&lt;/P&gt;</description>
      <pubDate>Wed, 12 Apr 2017 08:58:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/promisconlevel-unix-error-device-busy/m-p/6956048#M528461</guid>
      <dc:creator>Tumku</dc:creator>
      <dc:date>2017-04-12T08:58:55Z</dc:date>
    </item>
    <item>
      <title>Re: promisconlevel: UNIX error - Device busy</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/promisconlevel-unix-error-device-busy/m-p/6960511#M528462</link>
      <description>&lt;P&gt;"lan900" sounds like an aggregate, VLAN or other virtual construct, not a real physical NIC. You might be able to use the promiscuous mode on physical NICs only.&lt;/P&gt;&lt;P&gt;But do you really need promiscuous mode?&lt;/P&gt;&lt;P&gt;If you are trying to get a dump of network traffic that would already be received by your system without promiscuous mode (i.e. either unicast packetss addressed to that system, or broadcast packets) then you don't need promiscuous mode. at all.&lt;/P&gt;&lt;P&gt;If you are trying to diagnose misaddressed packets, multicasts or something more complicated, then you might need promiscuous mode.&lt;/P&gt;&lt;P&gt;If you add the option '-p' to your tcpdump command line, it will skip setting the interface to promiscuous mode and just dump the regular traffic.. For most application-level troubleshooting, that will be enough.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2017 14:20:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/promisconlevel-unix-error-device-busy/m-p/6960511#M528462</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2017-04-26T14:20:02Z</dc:date>
    </item>
  </channel>
</rss>

