Date: Sat, 28 Nov 2015 20:43:58 +0200 From: "Andriy Voskoboinyk" <avos@freebsd.org> To: "Steve Wills" <swills@freebsd.org> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: urtwn broken at r291262 Message-ID: <op.x8tqbkpw4dikkl@localhost> In-Reply-To: <5659ED1D.70003@FreeBSD.org> References: <5659ED1D.70003@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Sat, 28 Nov 2015 20:06:21 +0200 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Steve Wills = <swills@freebsd.org>: > 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 see= ms > 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 in= fo > if needed, just let me know what would help. > Hi, 1) chip name? 2) have you tried to run 'tcpdump -y IEEE802_11_RADIO = --no-promiscuous-mode'? > but not transmitting Which device is used to monitor the traffic? If this is the same device,= then you will not know about transmission failure/success, since tcpdump uses info from ieee80211_radiotap_tx(). > Any suggestions or should I just bisect to the exact commit? Probably, yes (it works for me without any issues on any revision). P.S. If problem is in r290630, then you can try to replace URTWN_MACID_B= C = with URTWN_MACID_BSS in urtwn_tx_data() (it was hardcoded as 0 in previous = revision). > Thanks, > Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.x8tqbkpw4dikkl>