From: David Miller <davem@davemloft.net>
To: the.sator@gmail.com
Cc: kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
jmorris@namei.org, netdev@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] net/ipv4/arp.c: Fix arp reply when sender ip 0
Date: Thu, 15 Nov 2007 15:28:13 -0800 (PST) [thread overview]
Message-ID: <20071115.152813.89410917.davem@davemloft.net> (raw)
In-Reply-To: <cac0ab7d0711151340l1cc91a2dw5ebf36e166d16d7a@mail.gmail.com>
From: "Jonas Danielsson" <the.sator@gmail.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.
next prev parent reply other threads:[~2007-11-15 23:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 11:40 [PATCH] net/ipv4/arp.c: Fix arp reply when sender ip 0 (was: Strange behavior in arp probe reply, bug or feature?) Jonas Danielsson
2007-11-15 15:40 ` Alexey Kuznetsov
2007-11-15 21:40 ` Jonas Danielsson
2007-11-15 23:28 ` David Miller [this message]
2007-11-16 8:30 ` [PATCH] net/ipv4/arp.c: Fix arp reply when sender ip 0 Jonas Danielsson
2007-11-16 9:05 ` David Miller
2007-11-16 14:13 ` Benny Amorsen
2007-11-16 19:26 ` Bill Fink
2007-11-17 22:14 ` Jarek Poplawski
2007-11-19 13:06 ` [PATCH] net/ipv4/arp.c: Fix arp reply when sender ip 0 (was: Strange behavior in arp probe reply, bug or feature?) Alexey Kuznetsov
2007-11-20 5:16 ` Bill Fink
2007-11-20 7:49 ` [PATCH] net/ipv4/arp.c: Fix arp reply when sender ip 0 David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071115.152813.89410917.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=jmorris@namei.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=the.sator@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome