From: JF Mezei on
crzzy1 wrote:

> This issue was fixed by having the customer concentrate on his routing
> on his host side.

Question:

If host1 thinks host2 is part of the same subnet, it will send an arp
asking for host2's ethernet address.

That broadcast arp will specify host2's ip address.

So at the low level, when host2 gets the ethernet broadcast, it will see
"this is something that concerns me" and pass it upwards for processing.

If the ethernet broadcast contained an arp request for an ip address not
used by host2, it would not be passed upwards for processing.

So, by the time the "upwards" layer gets the arp request, does it
blindly respond to the ethernet address of the sender of the broadcast ?

Or does the arp response behave as an IP packet and gets routed to a
router if the requestor is not in the same subnet ?

(at which point the arp request would never get to the requestor,
leaving a incomplete arp record at the requestor's arp database)