[127239] in North American Network Operators' Group
Re: Sending ARP request to unicast MAC instead of broadcast MAC
daemon@ATHENA.MIT.EDU (Chris Woodfield)
Thu Jun 17 17:45:33 2010
From: Chris Woodfield <rekoil@semihuman.com>
In-Reply-To: <7D4FBC01-E09F-4659-B620-310DCB11C20A@semihuman.com>
Date: Thu, 17 Jun 2010 14:45:01 -0700
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Looks like all the replies I got were private, so thanks all - to =
summarize, I got everything from "Read The Fine Kernel Source" to "Read =
The Fine RFC" to "Read RFC 1122, Section 2.3.2.1, it's quite a Fine =
read".=20
So for other folks out there like me who obviously can't read RFCs, the =
answer is "yes". :)
-C
On Jun 16, 2010, at 3:57 51PM, Chris Woodfield wrote:
> OK, this sounds Really Wacky (or, Really Hacky if you're into puns) =
but there's a reason for it, I swear...
>=20
> Will typical OSS UNIX kernels (Linux, BSD, MacOS X, etc) reply to a =
crafted ARP request that, instead of having FF:FF:FF:FF:FF:FF as its =
destination MAC address, is instead sent to the already-known unicast =
MAC address of the host?=20
>=20
> Next, what would be your utility of choice for crafting such a packet? =
Or is this something one would need to code up by hand in a lower-level =
language?
>=20
> Thanks,
>=20
> -C
