<?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: tcpdump and local packet capturing in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/tcpdump-and-local-packet-capturing/m-p/3216466#M566739</link>
    <description>Currently it's not possible. tcpdump (or actually libpcap) won't listen to lo0 because it can't find /dev/lo0. My system at least is missing the loopback interface device file.&lt;BR /&gt;&lt;BR /&gt;The correct syntax would be tcpdump -i lo0&lt;BR /&gt;If -i is not specified, tcpdump will use the lowest network interface found (usually lan0).&lt;BR /&gt;&lt;BR /&gt;Plaese speak out if you know some way to tweak this.</description>
    <pubDate>Wed, 22 Sep 2004 18:02:50 GMT</pubDate>
    <dc:creator>Mika Sipila</dc:creator>
    <dc:date>2004-09-22T18:02:50Z</dc:date>
    <item>
      <title>tcpdump and local packet capturing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tcpdump-and-local-packet-capturing/m-p/3216464#M566737</link>
      <description>How do I capture the IP packets from client to server when both ends exist on the same server.  The packets do not go through the interface but are routed internally.&lt;BR /&gt;&lt;BR /&gt;HPUX 11&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Thu, 11 Mar 2004 14:04:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tcpdump-and-local-packet-capturing/m-p/3216464#M566737</guid>
      <dc:creator>Marc Bohnert</dc:creator>
      <dc:date>2004-03-11T14:04:36Z</dc:date>
    </item>
    <item>
      <title>Re: tcpdump and local packet capturing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tcpdump-and-local-packet-capturing/m-p/3216465#M566738</link>
      <description>try using localhost or 127.0.0.1 as the host your listening to.  &lt;BR /&gt;&lt;BR /&gt;tcpdump host localhost&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Martin.</description>
      <pubDate>Mon, 15 Mar 2004 10:51:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tcpdump-and-local-packet-capturing/m-p/3216465#M566738</guid>
      <dc:creator>The Real MD</dc:creator>
      <dc:date>2004-03-15T10:51:04Z</dc:date>
    </item>
    <item>
      <title>Re: tcpdump and local packet capturing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tcpdump-and-local-packet-capturing/m-p/3216466#M566739</link>
      <description>Currently it's not possible. tcpdump (or actually libpcap) won't listen to lo0 because it can't find /dev/lo0. My system at least is missing the loopback interface device file.&lt;BR /&gt;&lt;BR /&gt;The correct syntax would be tcpdump -i lo0&lt;BR /&gt;If -i is not specified, tcpdump will use the lowest network interface found (usually lan0).&lt;BR /&gt;&lt;BR /&gt;Plaese speak out if you know some way to tweak this.</description>
      <pubDate>Wed, 22 Sep 2004 18:02:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tcpdump-and-local-packet-capturing/m-p/3216466#M566739</guid>
      <dc:creator>Mika Sipila</dc:creator>
      <dc:date>2004-09-22T18:02:50Z</dc:date>
    </item>
  </channel>
</rss>

