From owner-freebsd-wireless@freebsd.org Sun Apr 10 11:26:02 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCF8BAE23F7 for ; Sun, 10 Apr 2016 11:26:02 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 579781C08 for ; Sun, 10 Apr 2016 11:26:02 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: by mail-lf0-x235.google.com with SMTP id c126so124327049lfb.2 for ; Sun, 10 Apr 2016 04:26:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:subject:references:date:mime-version:content-transfer-encoding :from:message-id:in-reply-to:user-agent; bh=ofMe3B7UdyA2MYPEiH0LMSxCam7BaRYp/y1DCKWfQxA=; b=pDhZctRdjbwGfgEw9WfcpvmGEhG7vib+oBJkn2lTYQ79p/mWv7olPIdIgEMbmzqmjX oIi49H/HLe9k6SWUEAuGo6P7B2zfjGKHAl4MFey4r6Q2NWugWsGkVImcbJBI92bBtMji jzdRyWHNz06XkoCFqxZQr0sVa1osvgkhi7tC16hVF9ou397Nryd2s+HFtz53IAi+5i/m nGtjP49FdgsKqJGR/vr0hxy1qrr2isMT8KSJqEOs6POOH0Y/kMcz8d0pU0t5Wr5dTzEo toBVcs98K6L1FgXf3TmyvSKwKphYioDzh0cxlGq+8UAeWONWJDRwqpfpiUPwGISP7pof XCEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=ofMe3B7UdyA2MYPEiH0LMSxCam7BaRYp/y1DCKWfQxA=; b=fD7k9+cZVTG9GRLCgDA8so24nIpHTYX8iGR7dJSlpfk8OsUHW0FkoTglpx+yConFnV oDVTmJA5gaXLWlNz+Z91XcKCA6Z/VA6zL3oUrp7uWfnNOkpMkq4vBCcvPMP7QXruFeiD 5D1XB01yRL411ZV34TPWbw36rxvwfpeV04xAvm89jMKBJw7v5RXyRO3aFtHqsh9fDyMN f+JwGBYN79iSnoex06CkH6feag8ggJxJANZNxDnQ3Kl5s/5rfPxhKbsASktQOFaw3sPV wdtPCuF28c9roGb6VM3ZPy9LMk62/GIizHSvUXVyxcGFl4bpfHuZTx95QpiQl3IUqu64 Y7nA== X-Gm-Message-State: AD7BkJJH4o36fiWdQcwBptStCagS/fRHOho0FpP68qGhWk6u6LSZl4LIAJAQmV7oqLJgYw== X-Received: by 10.25.28.80 with SMTP id c77mr6926539lfc.5.1460287560544; Sun, 10 Apr 2016 04:26:00 -0700 (PDT) Received: from localhost (host-176-37-109-22.la.net.ua. [176.37.109.22]) by smtp.gmail.com with ESMTPSA id j39sm3607359lfi.9.2016.04.10.04.25.59 (version=TLS1 cipher=AES128-SHA bits=128/128); Sun, 10 Apr 2016 04:25:59 -0700 (PDT) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-wireless@freebsd.org, "Dave Cottlehuber" Subject: Re: "no buffer space available" EDIMAX EW-7811UN Wireless USB Adapter References: <1460286122.3298383.574172017.3A717528@webmail.messagingengine.com> Date: Sun, 10 Apr 2016 14:25:57 +0300 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: <1460286122.3298383.574172017.3A717528@webmail.messagingengine.com> User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.21 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: Sun, 10 Apr 2016 11:26:02 -0000 Sun, 10 Apr 2016 14:02:02 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Dave Cottlehuber = : > Hi, > > I got an EDIMAX EW-7811UN Wireless USB Adapter [1] > (150 Mbit/s, IEEE802.11b/g/n) to use on a few systems that > don't yet have supported onboard adapters. > > While using this I get `no buffer space available` regularly, > including from dhclient. It an old bug - dhclient listens to the RTM_IEEE80211_ASSOC event, and, when it arrives, tries to send a request. However, in an encrypted netwo= rk, this event goes before 4-way handshake occurs - so, there is a chance, that packet will be discarded because there is no key available yet. (also, this event is used by wpa_supplicant, so we cannot just send it later) > This sometimes requires me to > hard reboot to regain network connectivity. Is there anything > I can do about this? > There is some instability with RTL8188CUS chipset (sometimes its just stops working); you can restart it with 1) ifconfig wlan0 down 2) ifconfig wlan0 destroy 3) usbconfig -d power_off 4) usbconfig -d power_on > BTW specific recommendations on better-supported USB widgets > are welcome. For me, TP-Link TL-WN725N works a bit better (but there may be some better supported chipsets).