Why the stack doesn't process ("unexpected") ARP replies that it receives?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




 Is it normal behaviour of the IP stack that it DOES NOT process
 ARP replies that do not result from requests sent by that stack
 itself? Or do I have something misconfigured? See below.

 I need to learn the MAC address of a remote network node
 in an application executing as 'root' on Linux 2.4.19.

 Scenario 1)
 The MAC address IS NOT in the ARP cache, so ioctl() 
 fails. I'm building the ARP request and sending it myself
 thru a packet socket. That's OK. And the reply is received
 from the destination node. However... the IP stack on my machine 
 doesn't seem to handle the ARP reply! The resulting MAC address 
 IS STILL NOT in the cache! ioctl() still fails!

 Scenario 2) (obvious)
 I'm sending a piece of data through a plain datagram socket
 to the remote node, my stack handles the ARP resolution 
 on my behalf and I after that I can see the resulting 
 MAC address in the cache.

 I sniffed the ARP frames in both scenarios and undoubtedly 
 they are byte-after-byte the same.


_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux