netdev - Re: [PATCH] net/ipv4/arp.c: Fix arp reply when sender ip 0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 15 Nov 2007 15:28:13 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	the.sator@...il.com
Cc:	kuznet@....inr.ac.ru, linux-kernel@...r.kernel.org,
	jmorris@...ei.org, netdev@...r.kernel.org,
	akpm@...ux-foundation.org
Subject: Re: [PATCH] net/ipv4/arp.c: Fix arp reply when sender ip 0

From: "Jonas Danielsson" <the.sator@...il.com>
Date: Thu, 15 Nov 2007 22:40:13 +0100

> Is there a reason that the target hardware address isn't the target
> hardware address?

Linux subscribes to the host based addressing model rather
than an interface based addressing model.  Both approaches
are valid by RFCs.

Because of this, in cases where a choice can be made Linux will
advertise what is most likely to result in successful communication.

This is likely why we are changing that target address to the one of
the interface actually sending back the reply rather than the zero
value you used.

In fact I think this information can be useful to the sender of
the DAD request.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html