<?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 Identifying network port pairs in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/identifying-network-port-pairs/m-p/2936956#M577102</link>
    <description>Is there a fast way of identifying the network port pairs? I am trying to identify the local and remote port pairs that are in use at a particular point in time, and found that netstat takes forever, and ndd is unreliable. Is there a simple method that I am missing?</description>
    <pubDate>Thu, 27 Mar 2003 09:32:47 GMT</pubDate>
    <dc:creator>George Spencer</dc:creator>
    <dc:date>2003-03-27T09:32:47Z</dc:date>
    <item>
      <title>Identifying network port pairs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/identifying-network-port-pairs/m-p/2936956#M577102</link>
      <description>Is there a fast way of identifying the network port pairs? I am trying to identify the local and remote port pairs that are in use at a particular point in time, and found that netstat takes forever, and ndd is unreliable. Is there a simple method that I am missing?</description>
      <pubDate>Thu, 27 Mar 2003 09:32:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/identifying-network-port-pairs/m-p/2936956#M577102</guid>
      <dc:creator>George Spencer</dc:creator>
      <dc:date>2003-03-27T09:32:47Z</dc:date>
    </item>
    <item>
      <title>Re: Identifying network port pairs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/identifying-network-port-pairs/m-p/2936957#M577103</link>
      <description>Use lsof, it will do it. You can download from;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://hpux.cs.utah.edu/ftp/hpux/Sysadmin/lsof-4.64/" target="_blank"&gt;http://hpux.cs.utah.edu/ftp/hpux/Sysadmin/lsof-4.64/&lt;/A&gt;</description>
      <pubDate>Thu, 27 Mar 2003 09:49:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/identifying-network-port-pairs/m-p/2936957#M577103</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2003-03-27T09:49:55Z</dc:date>
    </item>
    <item>
      <title>Re: Identifying network port pairs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/identifying-network-port-pairs/m-p/2936958#M577104</link>
      <description>Instead of netstat -a try&lt;BR /&gt;netstat -an&lt;BR /&gt;or better&lt;BR /&gt;netstat -an |grep tcp&lt;BR /&gt;&lt;BR /&gt;The delay is caused by netstat looking up the hostname for each IP address via DNS.  The n option says just give us the ip address and don't worry about the hostnames.&lt;BR /&gt;&lt;BR /&gt;Ron</description>
      <pubDate>Thu, 27 Mar 2003 14:43:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/identifying-network-port-pairs/m-p/2936958#M577104</guid>
      <dc:creator>Ron Kinner</dc:creator>
      <dc:date>2003-03-27T14:43:38Z</dc:date>
    </item>
    <item>
      <title>Re: Identifying network port pairs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/identifying-network-port-pairs/m-p/2936959#M577105</link>
      <description>lsof -i tcp:23  (* list open files for tcp socket 23 *)&lt;BR /&gt;&lt;BR /&gt;lsof -i udp:123 (* list open files for udp socket 123 *)&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 27 Mar 2003 14:59:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/identifying-network-port-pairs/m-p/2936959#M577105</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2003-03-27T14:59:38Z</dc:date>
    </item>
  </channel>
</rss>

