[Beowulf] Network problem: Why are ARP discovery requests sent to specific addresses instead of a broadcast domain
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Rahul Nabar rpnabar at gmail.comMon Jul 12 21:04:48 PDT 2010
- Previous message: [Beowulf] shutting down pbs server and maui for half an hour will affect running jobs?
- Next message: [Beowulf] Network problem: Why are ARP discovery requests sent to specific addresses instead of a broadcast domain
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I am puzzled by a bunch of ARP requests on my network that I captured using tcpdump. Shouldn't ARP discovery requests always be sent to a broadcast address? I have requests of the type below which seemingly are addressed to a specific mAC address. 00:26:b9:58:d7:2f > 00:26:b9:58:eb:b8, ARP, length 42: arp who-has 10.0.0.36 tell 10.0.3.2 00:26:b9:58:eb:b8 > 00:26:b9:58:d7:2f, ARP, length 60: arp reply 10.0.0.36 is-at 00:26:b9:58:eb:b8 Now if mumble:d7:2f already knew that mumble:eb:b8 was 10.0.0.36 (which it indeed is) then why would it send out an ARP discovery request? I can see that something doesn't make sense here but I cannot figure out what is causing the problem. Any ideas? Has anyone seen this before? -- Rahul
- Previous message: [Beowulf] shutting down pbs server and maui for half an hour will affect running jobs?
- Next message: [Beowulf] Network problem: Why are ARP discovery requests sent to specific addresses instead of a broadcast domain
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
