
3 Feb
2012
3 Feb
'12
1:44 p.m.
On Thursday 19 January 2012 19:53:30 Joe Hershberger wrote:
Cisco's arp-proxy feature fails to ignore the link-local address range This means that a link-local device on a network with this Cisco equipment will reply to ARP requests for our device (in addition to our reply) ... --- a/net/arp.c +++ b/net/arp.c
/*
* Work-around for brain-damaged Cisco equipment with
* arp-proxy enabled.
*
* If the requesting IP is not on our subnet, wait 5ms to
* reply to ARP request so that our reply will overwrite
* the arp-proxy's instead of the other way around.
*/
if ((NetReadIP(&arp->ar_tpa) & NetOurSubnetMask) !=
(NetReadIP(&arp->ar_spa) & NetOurSubnetMask))
udelay(5000);
shouldn't this sit behind a link local ifdef then ? -mike