Re: iwm(4): Tx aggregation

2021-04-30 Thread Landry Breuil
On Fri, Apr 30, 2021 at 12:03:41AM +0200, Stefan Sperling wrote: > This is another patch for Tx aggregation support in iwm(4). > I have tested 7265, 8265, and 9560, and they seem to work. > > Causes of various fatal firmware errors from my earlier attempts at > getting this to work have been

Re: iwm(4): Tx aggregation

2021-04-30 Thread Stefan Sperling
On Fri, Apr 30, 2021 at 06:00:00PM +, Kevin Chadwick wrote: > On 4/30/21 12:18 PM, Stefan Sperling wrote: > > Our default group cipher is CCMP which should not involve any TKIP MIC > > checks on the AP. Such checks occuring would be a bug in this case. > > TKIP has been so easily crackable

Re: iwm(4): Tx aggregation

2021-04-30 Thread Theo de Raadt
Kevin Chadwick wrote: > On 4/30/21 12:18 PM, Stefan Sperling wrote: > > Our default group cipher is CCMP which should not involve any TKIP MIC > > checks on the AP. Such checks occuring would be a bug in this case. > > TKIP has been so easily crackable for over a decade that I wonder if it has

Re: iwm(4): Tx aggregation

2021-04-30 Thread Matthias Schmidt
Hi Stefan, * Stefan Sperling wrote: > This is another patch for Tx aggregation support in iwm(4). > I have tested 7265, 8265, and 9560, and they seem to work. > > Causes of various fatal firmware errors from my earlier attempts at > getting this to work have been identified and fixed in this

Re: iwm(4): Tx aggregation

2021-04-30 Thread Kevin Chadwick
On 4/30/21 12:18 PM, Stefan Sperling wrote: > Our default group cipher is CCMP which should not involve any TKIP MIC > checks on the AP. Such checks occuring would be a bug in this case. TKIP has been so easily crackable for over a decade that I wonder if it has a place in OpenBSD, atleast

Re: iwm(4): Tx aggregation

2021-04-30 Thread Stefan Sperling
On Fri, Apr 30, 2021 at 02:31:22PM +0200, Mark Kettenis wrote: > media autoselect mediaopt hostap > nwid openbsd chan 60 wpakey password > inet 192.168.32.1 > > and this is what ifconfig athn0 shows: > > athn0: flags=8843 mtu 1500 > lladdr 6c:71:d9:33:44:55 > index 3 priority 4

Re: iwm(4): Tx aggregation

2021-04-30 Thread Mark Kettenis
> Date: Fri, 30 Apr 2021 14:18:46 +0200 > From: Stefan Sperling [ Dropping Florian from the CC ] > On Fri, Apr 30, 2021 at 12:36:57PM +0200, Mark Kettenis wrote: > > Since booting into a kernel with this diff, I've started seeing the > > following messages on my OpenBSD AP that uses athn(4): >

Re: iwm(4): Tx aggregation

2021-04-30 Thread Stefan Sperling
On Fri, Apr 30, 2021 at 12:36:57PM +0200, Mark Kettenis wrote: > Since booting into a kernel with this diff, I've started seeing the > following messages on my OpenBSD AP that uses athn(4): > > Apr 30 02:13:54 smetana /bsd: athn0: Michael MIC failure > Apr 30 02:14:40 smetana /bsd: athn0: Michael

Re: iwm(4): Tx aggregation

2021-04-30 Thread Mark Kettenis
> Date: Fri, 30 Apr 2021 11:56:49 +0200 > From: Florian Obser > > This still works fine on > > iwm0 at pci2 dev 0 function 0 "Intel AC 7260" rev 0x83, msi > iwm0: hw rev 0x140, fw ver 17.3216344376.0 Since booting into a kernel with this diff, I've started seeing the following messages on my

Re: iwm(4): Tx aggregation

2021-04-30 Thread Florian Obser
This still works fine on iwm0 at pci2 dev 0 function 0 "Intel AC 7260" rev 0x83, msi iwm0: hw rev 0x140, fw ver 17.3216344376.0 Thanks, Florian -- I'm not entirely sure you are real.

Re: iwm(4): Tx aggregation

2021-04-29 Thread Bjorn Ketelaars
On Fri 30/04/2021 00:03, Stefan Sperling wrote: > This is another patch for Tx aggregation support in iwm(4). > I have tested 7265, 8265, and 9560, and they seem to work. > > Causes of various fatal firmware errors from my earlier attempts at > getting this to work have been identified and fixed

Re: iwm(4): Tx aggregation

2021-04-29 Thread Dave Voutila
Stefan Sperling writes: > This is another patch for Tx aggregation support in iwm(4). > I have tested 7265, 8265, and 9560, and they seem to work. > > Causes of various fatal firmware errors from my earlier attempts at > getting this to work have been identified and fixed in this version. > In