* Re: [Bugme-new] [Bug 6610] New: dummy interface broadcast destination hardware address is not ff:ff:ff:ff:ff:ff [not found] <200605232316.k4NNGRBp001431@fire-2.osdl.org> @ 2006-05-23 23:31 ` Andrew Morton 2006-05-23 23:53 ` David Miller 0 siblings, 1 reply; 6+ messages in thread From: Andrew Morton @ 2006-05-23 23:31 UTC (permalink / raw) To: bugme-daemon; +Cc: netdev bugme-daemon@bugzilla.kernel.org wrote: > > http://bugzilla.kernel.org/show_bug.cgi?id=6610 > > Summary: dummy interface broadcast destination hardware address > is not ff:ff:ff:ff:ff:ff > Kernel Version: 2.6.16 > Status: NEW > Severity: normal > Owner: jgarzik@pobox.com > Submitter: byyilxoz@no-spam.hu > > > Most recent kernel where this bug did not occur: > Distribution: > Hardware Environment: > Software Environment: > Problem Description: > > Steps to reproduce: > > ifconfig > dummy0 Link encap:Ethernet HWaddr C2:54:E2:F3:38:08 > inet addr:192.168.100.1 Bcast:192.168.100.255 Mask:255.255.255.0 > > tcpdump -XX -i dummy0 icmp > ping -b -c 1 192.168.100.255 > > ------- You are receiving this mail because: ------- > You are on the CC list for the bug, or are watching someone who is. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bugme-new] [Bug 6610] New: dummy interface broadcast destination hardware address is not ff:ff:ff:ff:ff:ff 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 0 siblings, 1 reply; 6+ messages in thread From: David Miller @ 2006-05-23 23:53 UTC (permalink / raw) To: akpm; +Cc: bugme-daemon, netdev From: Andrew Morton <akpm@osdl.org> Date: Tue, 23 May 2006 16:31:42 -0700 > > Summary: dummy interface broadcast destination hardware address > > is not ff:ff:ff:ff:ff:ff Very strange because the dummy device driver calls ether_setup() which does: memset(dev->broadcast,0xFF, ETH_ALEN); Probably tcpdump does not understand the link type, but that also doesn't make sense since clearly the ifconfig output shows "Ethernet" as the link encapsulation type. Stumped... ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bugme-new] [Bug 6610] New: dummy interface broadcast destination hardware address is not ff:ff:ff:ff:ff:ff 2006-05-23 23:53 ` David Miller @ 2006-05-24 1:10 ` Herbert Xu 2006-05-25 22:16 ` David Miller 0 siblings, 1 reply; 6+ messages in thread From: Herbert Xu @ 2006-05-24 1:10 UTC (permalink / raw) To: David Miller; +Cc: akpm, bugme-daemon, netdev David Miller <davem@davemloft.net> wrote: > From: Andrew Morton <akpm@osdl.org> > Date: Tue, 23 May 2006 16:31:42 -0700 > >> > Summary: dummy interface broadcast destination hardware address >> > is not ff:ff:ff:ff:ff:ff > > Very strange because the dummy device driver calls > ether_setup() which does: It's caused by the NO_ARP flag. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bugme-new] [Bug 6610] New: dummy interface broadcast destination hardware address is not ff:ff:ff:ff:ff:ff 2006-05-24 1:10 ` Herbert Xu @ 2006-05-25 22:16 ` David Miller 2006-05-26 0:43 ` Herbert Xu 0 siblings, 1 reply; 6+ messages in thread From: David Miller @ 2006-05-25 22:16 UTC (permalink / raw) To: herbert; +Cc: akpm, bugme-daemon, netdev From: Herbert Xu <herbert@gondor.apana.org.au> Date: Wed, 24 May 2006 11:10:54 +1000 > David Miller <davem@davemloft.net> wrote: > > From: Andrew Morton <akpm@osdl.org> > > Date: Tue, 23 May 2006 16:31:42 -0700 > > > >> > Summary: dummy interface broadcast destination hardware address > >> > is not ff:ff:ff:ff:ff:ff > > > > Very strange because the dummy device driver calls > > ether_setup() which does: > > It's caused by the NO_ARP flag. 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bugme-new] [Bug 6610] New: dummy interface broadcast destination hardware address is not ff:ff:ff:ff:ff:ff 2006-05-25 22:16 ` David Miller @ 2006-05-26 0:43 ` Herbert Xu 2006-05-26 1:18 ` David Miller 0 siblings, 1 reply; 6+ messages in thread From: Herbert Xu @ 2006-05-26 0:43 UTC (permalink / raw) To: David Miller; +Cc: akpm, bugme-daemon, netdev 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? Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bugme-new] [Bug 6610] New: dummy interface broadcast destination hardware address is not ff:ff:ff:ff:ff:ff 2006-05-26 0:43 ` Herbert Xu @ 2006-05-26 1:18 ` David Miller 0 siblings, 0 replies; 6+ messages in thread From: David Miller @ 2006-05-26 1:18 UTC (permalink / raw) To: herbert; +Cc: akpm, bugme-daemon, netdev 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-05-26 1:18 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox