> 	Also, when I startup ipf at boottime, setting it to YES in
> rc.conf, when I use my /etc/ppp/nat-up script I get this:
> 
> hobbes# ./nat-up
> Current IP address is 206.163.57.84
> Cleaning out IPNAT
> 0 entries flushed from NAT table
> 0 entries flushed from NAT list
> SIOCFRENB: Device busy
> Setting up IPNAT for IP address 206.163.57.84
> hobbes#
> 
> 	So, I'm thinking that with a dynamic IP, I should NOT start it up
> at boottime, correct? Since, I have not yet been assigned an IP at
> boottup. 

I think you're right. Fire up ipnat when the ppp connection comes up,
not at boot.

> DESCRIPTION
>        ipfstat examines /dev/kmem using  the  symbols  _fr_flags,
>        _frstats,  _filterin, and _filterout.  To run and work, it
>        needs to be able to read both  /dev/kmem  and  the  kernel
>        itself.  The kernel name defaults to /vmunix.
> 
>        The  default  behaviour of ipfstat is to retrieve and dis-
>        play the accumulated statistics which  have  been  accumu-
>        lated  over time as the kernel has put packets through the
>        filter.
> 
> ---
> 	Is this still true?? Because for NetBSD nowadays, I KNOW the
> kernel's name isn't /vmunix ;-) If it IS, I'm thinking that there needs to
> be something updated ;-)

This is a bug. Normally, I'd emplore you to send-pr the problem. But this
one's been fixed.  My source shows the change was early this month (I
picked it up in the Dec 4 SUP).

Take care,

Bill