ok, so far it indeed looks like a block-ack window issue. Which is weird, because i thought I had fixed all the transmit block-ack window stuff a looong time ago :(
Oh, can you please update to the very latest -HEAD? I only recently just fixed some multicast / queue handling issues which may fix your issues. It needs to be done on both the STA and AP side. -adrian On 4 February 2017 at 10:15, clutton <clut...@zoho.com> wrote: > They are too big for hosting now. I'll attach. > > falling time around: Sat 4 Feb 2017 20:03:29 EET > > > On Sat, 2017-02-04 at 10:02 -0800, Adrian Chadd wrote: >> all of em togethe. >> >> (I'm going to go look at the element ids that aren't being processed, >> in case it's something stupid I missed.) >> >> On 4 February 2017 at 10:00, clutton <clut...@zoho.com> wrote: >> > >> > On Sat, 2017-02-04 at 09:48 -0800, Adrian Chadd wrote: >> > > >> > > ugh, uhm, redo this on the client and AP side, and include >> > > "wlandebug >> > > +crypto +11n" too. >> > > >> > > thx, >> > Just with +crypto+11n or >> > with >> > input+scan+assoc+elemid+node+output+inact+roam+rate++crypto+11n >> > >> > I'm doing with second now it's still working for now. _______________________________________________ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
