From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 10:25:30 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6440B16A41F for ; Mon, 8 Aug 2005 10:25:30 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id F28FF43D46 for ; Mon, 8 Aug 2005 10:25:29 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from [62.142.71.181] (KMMLXXXI.dsl.saunalahti.fi [62.142.71.181]) by gw02.mail.saunalahti.fi (Postfix) with ESMTP id 65A53D1193; Mon, 8 Aug 2005 13:25:26 +0300 (EEST) Message-ID: <42F7331B.6000707@pp.nic.fi> Date: Mon, 08 Aug 2005 13:25:31 +0300 From: Pertti Kosunen User-Agent: Mozilla Thunderbird 1.0.2 / FreeBSD 5.4-STABLE X-Accept-Language: en-us, en MIME-Version: 1.0 To: "freebsd-stable@freebsd.org" References: <42E12A3B.8040804@pp.nic.fi> <42F62DDD.8000902@pp.nic.fi> <42F64856.2010506@mac.com> In-Reply-To: <42F64856.2010506@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: dhclient: send_packet: No buffer space available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 10:25:30 -0000 Chuck Swiger wrote: > Typically, that sort of message indicates that the firewall rules are > preventing traffic from going out, or packets are getting stuck in a > queue until it fills up, or maybe even a bug somewhere in the > particular combination of kernel firewall options enabled, high > optimization or CPUTYPE settings, and your particular hardware, > depending on how lucky you are. :-) > > Does the problem go away if you use a trivial "permit all" PF ruleset? > Does the problem go away if you use a trivial IPFW "permit all" > instead of PF? > Does the problem go away if you use a stock 5.4 release kernel? > > The 3Com 3c905B-TX is an OK NIC, apparently the later C revision or > the 918/920's are pretty decent, but anyway-- > > ...does the problem go away if you switch to another (known good) NIC? > System was ok with 5.3-RELEASE & custom kernel with ipfw. PF logs all block rules and nothing gets to pflog on those dhclient errors. I try those tips you gave, thanks. Stuck in a queue sounds most likely to be the case.