linux-kernel - Re: 2.6.22-rc4-mm2 -- ipw2200 -- SIOCSIFADDR: No buffer space available

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 7 Jun 2007 19:20:55 -0300
From:	"Kevin Winchester" <kjwinchester@...il.com>
To:	"Miles Lane" <miles.lane@...il.com>
Cc:	"Andrew Morton" <akpm@...l.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.22-rc4-mm2 -- ipw2200 -- SIOCSIFADDR: No buffer space available

On 07/06/07, Miles Lane <miles.lane@...il.com> wrote:
> Hi Andrew,
>
> This might be some problem with my kernel configuration.
> I added:
> CONFIG_BONDING=y
>
> # dhclient eth1
> There is already a pid file /var/run/dhclient.pid with pid 134993416
> Internet Systems Consortium DHCP Client V3.0.4
> Copyright 2004-2006 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
> SIOCSIFADDR: No buffer space available
> Listening on LPF/eth1/00:12:f0:5e:db:2f
> Sending on   LPF/eth1/00:12:f0:5e:db:2f
> Sending on   Socket/fallback
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
> DHCPOFFER from 192.168.1.1
> DHCPREQUEST on eth1 to 255.255.255.255 port 67
> DHCPACK from 192.168.1.1
> SIOCSIFADDR: No buffer space available
> SIOCSIFNETMASK: Cannot assign requested address
> SIOCSIFBRDADDR: Cannot assign requested address
> SIOCADDRT: Network is unreachable
> bound to 192.168.1.2 -- renewal in 2993 seconds.
>
> # ping www.yahoo.com
> ping: unknown host www.yahoo.com
>
> Any suggestions what to try now?  I'll go ahead and turn off the
> bonding option and see if that helps.
>

I was seeing this same error last night on my via-velocity based
ethernet interface.  I chalked it up to some config mistake on my
part, but I guess there might be more to it.  Whatever it is, it
doesn't seem to be specific to the ipw2200 driver.

-- 
Kevin Winchester
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/