Re: [Bugme-new] [Bug 6610] New: dummy interface broadcast destination hardware address is not ff:ff:ff:ff:ff:ff

2006-05-25 Thread David Miller
From: Herbert Xu [EMAIL PROTECTED] Date: Wed, 24 May 2006 11:10:54 +1000 David Miller [EMAIL PROTECTED] wrote: From: Andrew Morton [EMAIL PROTECTED] Date: Tue, 23 May 2006 16:31:42 -0700 Summary: dummy interface broadcast destination hardware address

Re: [Bugme-new] [Bug 6610] New: dummy interface broadcast destination hardware address is not ff:ff:ff:ff:ff:ff

2006-05-25 Thread Herbert Xu
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

Re: [Bugme-new] [Bug 6610] New: dummy interface broadcast destination hardware address is not ff:ff:ff:ff:ff:ff

2006-05-25 Thread David Miller
From: Herbert Xu [EMAIL PROTECTED] 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

Re: [Bugme-new] [Bug 6610] New: dummy interface broadcast destination hardware address is not ff:ff:ff:ff:ff:ff

2006-05-23 Thread David Miller
From: Andrew Morton [EMAIL PROTECTED] 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:

Re: [Bugme-new] [Bug 6610] New: dummy interface broadcast destination hardware address is not ff:ff:ff:ff:ff:ff

2006-05-23 Thread Herbert Xu
David Miller [EMAIL PROTECTED] wrote: From: Andrew Morton [EMAIL PROTECTED] 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