Erm, I've actually gone and fixed these crypto programming (multicast key) bugs in FreeBSD.
If they still exist, please give me a very specific test case using FreeBSD-HEAD and I'll go and get it fixed quick smart. I work at Atheros now - not on *BSD stuff, but I have access to all the shiny things here. I've been using AR9280/AR9285/AR9280 in STA/hostap mode for > 12 months now and I've not seen this particular issue after I fixed multicast key handling. Thanks, Adrian On 19 January 2012 09:45, Justin Sherrill <jus...@shiningsilence.com> wrote: > As Matthias pointed out: > > http://leaf.dragonflybsd.org/mailarchive/commits/2010-11/msg00120.html > > > > On Thu, Jan 19, 2012 at 3:31 AM, ssgriffonuser <ssgriffonu...@gmail.com> > wrote: >> I just installed DFBSD on my EEE netbook and the ath driver seems to be >> failing after wpa_supplicant is run. The connection is established but the >> message "ath_reset" is also printed. After that message is printed, >> dhclient wlan0 cannot connect to the dhcp server. >> >> I had a similar problem when I installed FreeBSD 8.2 on the same netbook. >> However, Adrian Chadd had already fixed the problem in -HEAD so I was able >> to update the driver and everything worked fine. >> >> I'm fairly certain that these problems were one in the same but if somebody >> else has any ideas I'm all ears. >> >> If Adrian is listening on this list, do you remember what that problem was? >> If so, is it something that I can fix or do I need to know the inner >> workings of the ath card that are hidden behind an NDA? >> >> Thanks >
