Subject: Re: kern/11058: bpf does not work correctly in -current
To: None <gnats-bugs@gnats.netbsd.org (NetBSD GNATS submissions and>
From: None <itojun@iijlab.net>
List: netbsd-bugs
Date: 09/22/2000 02:40:12
>> The bpf device is unusable unless an IP address is first assigned to an
>> interface. This causes dhclient to no longer function at boot.
>Did this work in a less recent -current?
>I noted that I couldn't tcpdump on an interface with no address in 1.4V
>and I suspect this is the same problem.  However I didn't exactly expect
>it to work.

	could you (submitter) clarify if this is specific to some ethernet
	card or not?  i'm using bunch of ethernet cards with IPv6-only 
	configuration, and bpf(4) and tcpdump(8) is working just fine.
	tcpdump(8) had some assumption on IPv4 address, but I have removed
	that when I integrated IPv6 sniffinc capability to tcpdump(8).

	if this is specific to some card, i bet it is related to promisc
	mode/multicast filter setup (the setup is performed only when IPv4
	address is present or something).

itojun