From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: akpm@osdl.org, bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 6610] New: dummy interface broadcast destination hardware address is not ff:ff:ff:ff:ff:ff
Date: Thu, 25 May 2006 18:18:13 -0700 (PDT) [thread overview]
Message-ID: <20060525.181813.66176551.davem@davemloft.net> (raw)
In-Reply-To: <20060526004324.GA762@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Fri, 26 May 2006 10:43:24 +1000
> On Thu, May 25, 2006 at 03:16:02PM -0700, David Miller wrote:
> >
> > Perhaps RTN_BROADCAST should take precedence over IFF_NOARP
> > (but not IFF_LOOPBACK)? I'm talking about the code in
> > net/ipv4/arp.c that causes this behavior.
>
> Sure, I don't see any harm in that.
>
> However, I'm curious as to the purpose of all this. What application
> is there for sending broadcasts through a dummy device with the
> Ethernet broadcast address?
Good point. dummy is just a black hole to point routes to
while your real connection is down.
Running tcpdump on it and having any kind of expectations
about broadcast addresses and whatnot is pointless.
prev parent reply other threads:[~2006-05-26 1:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200605232316.k4NNGRBp001431@fire-2.osdl.org>
2006-05-23 23:31 ` [Bugme-new] [Bug 6610] New: dummy interface broadcast destination hardware address is not ff:ff:ff:ff:ff:ff Andrew Morton
2006-05-23 23:53 ` David Miller
2006-05-24 1:10 ` Herbert Xu
2006-05-25 22:16 ` David Miller
2006-05-26 0:43 ` Herbert Xu
2006-05-26 1:18 ` David Miller [this message]
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=20060525.181813.66176551.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
/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