From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 22:15:18 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0A78E288 for ; Sat, 23 Aug 2014 22:15:18 +0000 (UTC) Received: from albert.telenet-ops.be (albert.telenet-ops.be [195.130.137.90]) by mx1.freebsd.org (Postfix) with ESMTP id 95B7333A4 for ; Sat, 23 Aug 2014 22:15:16 +0000 (UTC) Received: from [192.168.0.95] ([141.134.88.3]) by albert.telenet-ops.be with bizsmtp id iNFE1o00604KsaM06NFErn; Sun, 24 Aug 2014 00:15:14 +0200 Message-ID: <53F9127F.9090602@telenet.be> Date: Sun, 24 Aug 2014 00:15:27 +0200 From: Chris Van Steenlandt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour References: <201408231238.s7NCc8ME057766@fire.js.berklix.net> <53F8F086.1070207@telenet.be> <53F8F605.80006@telenet.be> <53F9009F.2020603@telenet.be> <53F90E0A.3060800@telenet.be> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Aug 2014 22:15:18 -0000 Indeed, I forgot about dhcp :( If I do that, it works ok. What I did notice after 'dhclient wlan0' is after a while the message : dhclient [2628]: send_packet : No buffer space available Chris On 23-08-14 23:58, Adrian Chadd wrote: > Hi, > > Ther'es two separate problems; 5ghz transmit, and your connectivity > > Oh, the third thing to try after all that manual stuff? > > dhclient wlan0 > > Then see if it successfully gets an IP address. > > > > -a