On Thu, Sep 21, 2000 at 01:24:11PM -0400, Greg A. Woods wrote:
> [ On Thursday, September 21, 2000 at 07:24:01 (-0400), finkels@cybernarian.org wrote: ]
> > Subject: kern/11058: bpf does not work correctly in -current
> >
> > 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?

Yes, it worked until my Tuesday night sup. At least I believe it was the 
Tuesday night sup. It may have been Wednesday night...

> 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.

You could not tcpdump on it, but DHCP worked correctly.

> It does work this way though:
> 
> # ifconfig tlp0 inet 0.0.0.0 netmask 255.255.255.255
> # ifconfig tlp0                                      
> tlp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         media: Ethernet 10baseT
>         status: active
>         inet 0.0.0.0 netmask 0xffffffff 
>         inet6 fe80::722f:53ff:fec0:f02e%tlp0 prefixlen 64 scopeid 0x2
> # tcpdump -vvv -n -i tlp0
> tcpdump: listening on tlp0
> 13:22:49.525336 24.42.191.4 > 24.114.57.77: icmp: echo request (ttl 254, id 38894)

Yes, if you assign an IP address first it works fine. The `0.0.0.0' trick works
for the time being, but if that is going to become a permanent solution, then
it should be in one of the rc files, no?

 - jeff