Subject: Re: Strange behaviour of ifconfig
To: Marcin Jessa <lists@yazzy.org>
From: Pavel Cahyna <pavel@netbsd.org>
List: current-users
Date: 06/27/2006 10:17:19
On Fri, Jun 16, 2006 at 01:17:32AM +0200, Marcin Jessa 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.

This is now fixed properly, old ifconfig and new kernel should work. But 
a recent ifconfig (built after the update which fixed the problem for you)
probably won't and it will show a similar symptom again. The solution is
to either move back to an older ifconfig, or to rebuild libc and ifconfig
again.

To summarize: if you have an old ifconfig and want to use a new kernel, it
will work. But if you have an ifconfig built from sources after Jun 14
2006, you should rebuild libc and ifconfig to use a new kernel.

Sorry for the inconvenience.

Pavel