Re: ifconfig -a error

[Iain Hibbert <plunky%rya-online.net@localhost>]

On Tue, 5 Aug 2008, David Young wrote:

> On Mon, Aug 04, 2008 at 11:11:00PM +0100, Iain Hibbert wrote:
> > with the new ifconfig (on i386) I notice an error
> >
> > % ifconfig -a
> > eon0: flags=3<UP,BROADCAST> mtu 1500
> > ifconfig: link_status: ioctl: Invalid argument
> >
> > % ifconfig eon0
> > eon0: flags=3<UP,BROADCAST> mtu 1500
> > ifconfig: link_status: ioctl: Invalid argument
> >
> > % ifconfig ppp0
> > ppp0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
> >         inet 10.34.129.29 -> 10.64.64.64 netmask 0xff000000
> >
> > It seems to be related to the SIOCGLIFADDR in af_link.c but I don't
> > know what that does. I have "options EON,ISO,TPIP" in my kernel config
> > file (though I don't use the eon interface) left over from when I was
> > working in the netiso code so perhaps its an incompatibility with the
> > eon driver?

> There is a bug in eonioctl().  In eonioctl(), change the return value in
> the 'default:' case from EINVAL to ENOTTY.  This is just a stopgap fix.

This does not work btw; I still get the same error with ENOTTY. The EINVAL
is coming from link_proto.c/link_control() at

        switch (cmd) {
        case SIOCALIFADDR:
        case SIOCDLIFADDR:
        case SIOCGLIFADDR:
                iflr = data;

                if (iflr->addr.ss_family != AF_LINK)
                        return EINVAL;

                asdl = satocsdl(sstocsa(&iflr->addr));

                if (asdl->sdl_alen != ifp->if_addrlen)
                        return EINVAL;

how to fix that?

iain