<?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: ndd -get /dev/arp arp_cache_report in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ndd-get-dev-arp-arp-cache-report/m-p/2851936#M579544</link>
    <description>Sivikumar is pretty much right about the first too.  We disagree on the 3rd item.&lt;BR /&gt;&lt;BR /&gt;1) just means this is your NIC.  The other entries are for other devices on the LAN that it currently has in the ARP cache.&lt;BR /&gt;&lt;BR /&gt;2) This is the multicast broadcast address range that all new NICs know to listen to.&lt;BR /&gt;&lt;BR /&gt;3)  IS the IP mask.  A 255.255.255.255 mask indicates a single host and thus a single MAC.  If you look at the entry for 224.0.0.0 you see that it has a mask of 240.0.0.0 which means that it is valid for 224.0.0.0 through 239.255.255.255 which is the multicast IP range and corresponds to a MAC of 01:00:5e:00:00:00 through 01:00:5e:7f:ff:ff.  There is a slight mismatch here since bits 7 and 8 of the IP address (counting from the left) are not used when converting to the Multicast MAC.  &lt;BR /&gt;&lt;BR /&gt;Your machine is probably set up with a default route to the local router.  If you did not have a default route to the local router but instead pointed the default route back to your PC then the NIC would ARP for every address and the local router would be expected to give a Proxy ARP reply where it sends its own MAC instead of the MAC of the device on the far end which it probably doesn't know.  In this case your arp cache would be much more interesting and would contain lots of entries for devices on other networks (all strangely enough with the same MAC - that of the local router).&lt;BR /&gt;&lt;BR /&gt;Ron</description>
    <pubDate>Tue, 26 Nov 2002 16:44:38 GMT</pubDate>
    <dc:creator>Ron Kinner</dc:creator>
    <dc:date>2002-11-26T16:44:38Z</dc:date>
    <item>
      <title>ndd -get /dev/arp arp_cache_report</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ndd-get-dev-arp-arp-cache-report/m-p/2851934#M579542</link>
      <description>the above command will give output similar to this:&lt;BR /&gt;&lt;BR /&gt;ifname   proto addr      proto mask      hardware addr     flags&lt;BR /&gt;lan0     150.150.007.010 255.255.255.255 00:10:83:b8:1b:cb&lt;BR /&gt;lan0     150.150.007.016 255.255.255.255 00:30:6e:2b:2c:06&lt;BR /&gt;lan0     150.150.007.025 255.255.255.255 00:30:6e:2c:85:8e PERM PUBLISH LOCAL&lt;BR /&gt;lan0     224.000.000.000 240.000.000.000 01:00:5e:00:00:00 PERM MAPPING&lt;BR /&gt;&lt;BR /&gt;can anybody explain what is the following values mean:&lt;BR /&gt;1)PERM PUBLISH LOCAL&lt;BR /&gt;2)224.0.0.0 (why is it here?)&lt;BR /&gt;3)255.255.255.255 (why not showing the configured net mask of the Lan interface?)&lt;BR /&gt;&lt;BR /&gt;thanks in advance.</description>
      <pubDate>Tue, 26 Nov 2002 05:45:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ndd-get-dev-arp-arp-cache-report/m-p/2851934#M579542</guid>
      <dc:creator>S.C. Fun</dc:creator>
      <dc:date>2002-11-26T05:45:54Z</dc:date>
    </item>
    <item>
      <title>Re: ndd -get /dev/arp arp_cache_report</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ndd-get-dev-arp-arp-cache-report/m-p/2851935#M579543</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;PERM  means that entry is a permanent one , it does not expire .&lt;BR /&gt;&lt;BR /&gt;PUBLISH means that arp entry is for Proxy ARP.&lt;BR /&gt;which means this interface will answer ARP requests for the MAC address of some other interface or server which is LOCAL . &lt;BR /&gt;&lt;BR /&gt;224.0.0.0 is the ARP entry for multicast support. &lt;BR /&gt;#ifconfig lan0&lt;BR /&gt;&lt;MULTICAST&gt;&lt;BR /&gt;&lt;BR /&gt;The 255.255.255.255 is not the net mask field in the ARP cache but like a filter.&lt;BR /&gt;&lt;BR /&gt;It means that 150.150.7.25 is the ip to be matched for the MAC address table. In other words 255.255.255.255 means that ARP request&lt;BR /&gt;for IP 150.150.7.25 will only be answered with respective MAC address.&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;U.SivaKumar&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/MULTICAST&gt;</description>
      <pubDate>Tue, 26 Nov 2002 06:01:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ndd-get-dev-arp-arp-cache-report/m-p/2851935#M579543</guid>
      <dc:creator>U.SivaKumar_2</dc:creator>
      <dc:date>2002-11-26T06:01:25Z</dc:date>
    </item>
    <item>
      <title>Re: ndd -get /dev/arp arp_cache_report</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ndd-get-dev-arp-arp-cache-report/m-p/2851936#M579544</link>
      <description>Sivikumar is pretty much right about the first too.  We disagree on the 3rd item.&lt;BR /&gt;&lt;BR /&gt;1) just means this is your NIC.  The other entries are for other devices on the LAN that it currently has in the ARP cache.&lt;BR /&gt;&lt;BR /&gt;2) This is the multicast broadcast address range that all new NICs know to listen to.&lt;BR /&gt;&lt;BR /&gt;3)  IS the IP mask.  A 255.255.255.255 mask indicates a single host and thus a single MAC.  If you look at the entry for 224.0.0.0 you see that it has a mask of 240.0.0.0 which means that it is valid for 224.0.0.0 through 239.255.255.255 which is the multicast IP range and corresponds to a MAC of 01:00:5e:00:00:00 through 01:00:5e:7f:ff:ff.  There is a slight mismatch here since bits 7 and 8 of the IP address (counting from the left) are not used when converting to the Multicast MAC.  &lt;BR /&gt;&lt;BR /&gt;Your machine is probably set up with a default route to the local router.  If you did not have a default route to the local router but instead pointed the default route back to your PC then the NIC would ARP for every address and the local router would be expected to give a Proxy ARP reply where it sends its own MAC instead of the MAC of the device on the far end which it probably doesn't know.  In this case your arp cache would be much more interesting and would contain lots of entries for devices on other networks (all strangely enough with the same MAC - that of the local router).&lt;BR /&gt;&lt;BR /&gt;Ron</description>
      <pubDate>Tue, 26 Nov 2002 16:44:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ndd-get-dev-arp-arp-cache-report/m-p/2851936#M579544</guid>
      <dc:creator>Ron Kinner</dc:creator>
      <dc:date>2002-11-26T16:44:38Z</dc:date>
    </item>
  </channel>
</rss>

