You should update your  ifconfig sources and you should be fine.
There was a new constant introduced recently.


dheeraj
On 6/15/06, Marcin Jessa <lists@yazzy.org> wrote:
> Hi guys.
>
> Something fishy is going on with CURRENT.
> The ifconfig command shows only one interface and fails showing others
> saying:
> ifconfig: socket: Address family not supported by protocol family
> even though the other interfaces are up and working and they can be
> seen using their iface name.
> Both kernel and userland are in sync.
>
> #uname -a
> NetBSD xyz.yazzy.net 3.99.21 NetBSD 3.99.21 (XEN2_0) #1: Fri Jun 16
> 01:07:57 CEST 2006
> root@xyz.yazzy.net:/usr/obj/sys/arch/i386/compile/XEN2_0 i386
>
> This is a XEN0 v. 2. The same goes for the XENU hosts.
>
>
> troll# ifconfig -a
> re0:
> flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> mtu
> 1500
> capabilities=3d80<TSO4,IP4CSUM_Rx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
> enabled=0 address: 00:0a:cd:0a:78:ba media: Ethernet autoselect
> (100baseTX full-duplex) status: active
>         inet 192.168.98.2 netmask 0xffffff00 broadcast 192.168.98.255
>         inet6 fe80::20a:cdff:fe0a:78ba%re0 prefixlen 64 scopeid 0x1
> ifconfig: socket: Address family not supported by protocol family
>
> troll# ifconfig vlan0
> vlan0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu
> 1500 vlan: 1 parent: re0
>         address: 00:0a:cd:0a:78:ba
>         inet 11.22.33.44 netmask 0xfffffff8 broadcast 81.175.13.143
>         inet6 fe80::20a:cdff:fe0a:78ba%vlan0 prefixlen 64 scopeid 0x5
> ifconfig: socket: Address family not supported by protocol family
>
>
> Marcin.
>


-- 
dheeraj