From owner-freebsd-wireless@freebsd.org Sat Nov 28 18:06:31 2015 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 1BF5FA37400 for ; Sat, 28 Nov 2015 18:06:31 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EB8051D92; Sat, 28 Nov 2015 18:06:30 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from [10.0.1.96] (cpe-071-065-239-148.nc.res.rr.com [71.65.239.148] (may be forged)) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id tASI6KD4079348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 28 Nov 2015 18:06:26 GMT (envelope-from swills@FreeBSD.org) To: freebsd-wireless@freebsd.org From: Steve Wills Subject: urtwn broken at r291262 Message-ID: <5659ED1D.70003@FreeBSD.org> Date: Sat, 28 Nov 2015 13:06:21 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Sat, 28 Nov 2015 18:06:26 +0000 (UTC) X-Spam-Status: No, score=-1.0 required=4.5 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.98.7 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 28 Nov 2015 18:06:31 -0000 Hi, My Raspberry Pi has a urtwn USB WiFi device. It was working previously, at r281469. It's been a while, but I updated to r291262 and now it seems to associate, but can't get a DHCP lease. When I run tcpdump, it looks like it's receiving but not transmitting. (But obviously it transmits enough to associate.) Looking at recent commits, I'm building r290629 and will test that, as I suspect r290630. Any suggestions or should I just bisect to the exact commit? I can send more detailed debugging info if needed, just let me know what would help. Thanks, Steve