d also fix kern/150148.
>
> I'm guessing there's some work needed in the key handling code in if_ath.
>
> Russell, are you still interested in this problem? Would you be
> interested in giving me a hand?
>
> Thanks Russell/Sam,
>
>
> Adrian
>
> On 25 Jan
-Russ
On Mon, Dec 13, 2010 at 3:49 AM, Adrian Chadd wrote:
> (I'm removing Sam from the CC: ; it seems he's not interested in this
> stuff any longer.)
>
> On 8 December 2010 09:54, Russell Yount wrote:
> > Adrian,
> >
> > Yes, I can help track down this
It seems AP to client broadcasts/multicasts traffic is
broken when using WPA2/802.11i with multiple hostapds in 8.0.
Only the SSID associated with the last hostapd to be started has
AP to client broadcasts/multicasts being delivered correctly.
The AP and client are 8.0 freebsd systems althought I
On Fri, Jan 15, 2010 at 4:50 PM, Graham Menhennitt wrote:
> I've been trying to get reliable wireless AP functionality in my Soekris
> net5501 (http://soekris.com/net5501.htm) box for some time now. In the
> past I've reported a problem with it
> (http://www.mail-archive.com/freebsd-stable@freebs
On Sat, Jan 16, 2010 at 3:21 PM, Sam Leffler wrote:
> Russell Yount wrote:
>
>> It seems AP to client broadcasts/multicasts traffic is
>> broken when using WPA2/802.11i with multiple hostapds in 8.0.
>>
>> Only the SSID associated with the last hostapd to
On Sun, Jan 17, 2010 at 1:45 PM, Sam Leffler wrote:
> Russell Yount wrote:
>
>
>>
>> On Sat, Jan 16, 2010 at 3:21 PM, Sam Leffler > s...@errno.com>> wrote:
>>
>>Russell Yount wrote:
>>
>>It seems AP to client broadcasts/multicas
On Sat, Jan 23, 2010 at 8:22 PM, Sam Leffler wrote:
> Russell Yount wrote:
> > On Sun, Jan 17, 2010 at 1:45 PM, Sam Leffler > <mailto:s...@errno.com>> wrote:
> >
> > Russell Yount wrote:
> >
> >
> >
> > On Sat, Jan 16, 2010
The attached patch for 8.0-STABLE enables multicast key search
capability for devices which support it in the ath(4) driver. This fixes
the problem of corrupted multicast traffic when more than one hostap
VAP is configured on a device.
You can tell if your ath(4) device supports this capability by
