Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-16 Thread Stefan Sperling
On Wed, Mar 16, 2022 at 03:58:59PM +0100, Stefan Sperling wrote: > APs not showing up in the 5GHz band has always been a problem on > Intel cards. It goes back to older drivers like iwn(4) or perhaps > even ipw(4). Oops, I meant wpi(4), not ipw(4) :) (ipw is 11b only)

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-16 Thread Stefan Sperling
On Wed, Mar 16, 2022 at 07:56:20AM -0500, rea...@catastrophe.net wrote: > On Wed, Mar 16, 2022 at 10:11:50AM +0100, Stefan Sperling wrote: > >Looks like a firwmare or driver issue to me. > > > >Sorry, without having a reproducible test case in front of me, there > >is nothing I could do fix this

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-16 Thread readme
On Wed, Mar 16, 2022 at 10:11:50AM +0100, Stefan Sperling wrote: >Looks like a firwmare or driver issue to me. > >Sorry, without having a reproducible test case in front of me, there >is nothing I could do fix this from afar. I mean, in fact it's 100% reproducible. >You could try moving the AP

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-16 Thread Stefan Sperling
On Tue, Mar 15, 2022 at 02:50:29PM -0500, rea...@catastrophe.net wrote: > Ok, please see the following. The card is cleared of its monitor config then > put onto channel 132 in debug mode. > > # ifconfig iwm0 -chan > # ifconfig iwm0 -mediaopt monitor > # ifconfig iwm0 > iwm0: flags=8806 mtu 1500

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-15 Thread readme
On Tue, Mar 15, 2022 at 05:19:34PM +0100, Stefan Sperling wrote: >On Tue, Mar 15, 2022 at 09:09:57AM -0500, rea...@catastrophe.net wrote: [..] >> # ifconfig iwm0 mediaopt monitor mode 11n >> # ifconfig iwm0 chan 132 >> # ifconfig iwm0 up [..] > >> Next I'll try join the network using the 5Ghz

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-15 Thread Stefan Sperling
On Tue, Mar 15, 2022 at 09:09:57AM -0500, rea...@catastrophe.net wrote: > Yes you did, and I greatly appreciate it. However, the interface won't > join to anything once out of monitor mode. > > # uname -a > OpenBSD server.example.org 7.0 GENERIC.MP#5 amd64 > > # ifconfig iwm0 mediaopt monitor

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-15 Thread readme
On Tue, Mar 15, 2022 at 02:15:41PM +0100, Stefan Sperling wrote: >On Tue, Mar 15, 2022 at 08:02:07AM -0500, rea...@catastrophe.net wrote: >> Unfortunately it appears as though I've run into it. Is there any recourse >> to provide more useful debugging information to find the issue? > >I already

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-15 Thread Stefan Sperling
On Tue, Mar 15, 2022 at 08:02:07AM -0500, rea...@catastrophe.net wrote: > On Mon, Mar 14, 2022 at 11:37:15PM +0100, Stefan Sperling wrote: > >In the implementation, the mode determines which channels are available, > >not the other way around. > >And for some reason your interface goes into a mode

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-15 Thread readme
On Mon, Mar 14, 2022 at 11:37:15PM +0100, Stefan Sperling wrote: >On Mon, Mar 14, 2022 at 05:16:32PM -0500, rea...@catastrophe.net wrote: >> Trying to manually monitor channel 132, I get an error, SIOCS80211CHANNEL. >> [..] >> # ifconfig iwm0 chan 132 >> ifconfig: SIOCS80211CHANNEL: Invalid

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-14 Thread Stefan Sperling
On Mon, Mar 14, 2022 at 05:16:32PM -0500, rea...@catastrophe.net wrote: > Trying to manually monitor channel 132, I get an error, SIOCS80211CHANNEL. > > # ifconfig iwm0 > iwm0: flags=8802 mtu 1500 > lladdr 80:19:34:ab:ab:ab > index 5 priority 4 llprio 3 > groups: wlan >

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-14 Thread readme
On Mon, Mar 14, 2022 at 10:34:04PM +0100, Stefan Sperling wrote: >On Mon, Mar 14, 2022 at 04:07:33PM -0500, rea...@catastrophe.net wrote: >> Just sitting around doing nothing I'm seeing 30% loss to my next hop. >> >> # ifconfig iwm0 >> iwm0: flags=808843 mtu 1500 >> lladdr 80:19:34:ab:ab:ab

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-14 Thread Stefan Sperling
On Mon, Mar 14, 2022 at 04:07:33PM -0500, rea...@catastrophe.net wrote: > Just sitting around doing nothing I'm seeing 30% loss to my next hop. > > # ifconfig iwm0 > iwm0: flags=808843 mtu 1500 > lladdr 80:19:34:ab:ab:ab > index 5 priority 4 llprio 3 > groups: wlan egress >

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-14 Thread readme
On Mon, Mar 14, 2022 at 09:42:37PM +0100, Stefan Sperling wrote: >On Mon, Mar 14, 2022 at 03:05:00PM -0500, rea...@catastrophe.net wrote: >> On Mon, Mar 14, 2022 at 08:58:01PM +0100, Stefan Sperling wrote: >> >On Mon, Mar 14, 2022 at 02:34:29PM -0500, rea...@catastrophe.net wrote: >> >> Well, even

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-14 Thread Stefan Sperling
On Mon, Mar 14, 2022 at 03:05:00PM -0500, rea...@catastrophe.net wrote: > On Mon, Mar 14, 2022 at 08:58:01PM +0100, Stefan Sperling wrote: > >On Mon, Mar 14, 2022 at 02:34:29PM -0500, rea...@catastrophe.net wrote: > >> Well, even after adding iwm0 I notice high latency and packet loss anywhere >

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-14 Thread readme
On Mon, Mar 14, 2022 at 08:58:01PM +0100, Stefan Sperling wrote: >On Mon, Mar 14, 2022 at 02:34:29PM -0500, rea...@catastrophe.net wrote: >> Well, even after adding iwm0 I notice high latency and packet loss anywhere >> from 15-50%. This occurs randomly when the device is either 2m, 10m, or 30m

Re: Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-14 Thread Stefan Sperling
On Mon, Mar 14, 2022 at 02:34:29PM -0500, rea...@catastrophe.net wrote: > Well, even after adding iwm0 I notice high latency and packet loss anywhere > from 15-50%. This occurs randomly when the device is either 2m, 10m, or 30m > away from the access point. I did testing to verify I'm seeing

Latency and loss persist with iwm0 (Was Re: Latency with run0 interface)

2022-03-14 Thread readme
On Mon, Mar 14, 2022 at 10:34:23AM -0500, rea...@catastrophe.net wrote: >On Mon, Mar 14, 2022 at 12:43:57AM -, Stuart Henderson wrote: >>On 2022-03-14, rea...@catastrophe.net wrote: >If not, consider hunting down a mini PCIe iwm(4) 7260 card, or an >M.2 AX200 iwx(4) card with an

Re: Latency with run0 interface

2022-03-14 Thread readme
On Mon, Mar 14, 2022 at 12:43:57AM -, Stuart Henderson wrote: >On 2022-03-14, rea...@catastrophe.net wrote: If not, consider hunting down a mini PCIe iwm(4) 7260 card, or an M.2 AX200 iwx(4) card with an adapter from M.2 to mini PCIe. Both would need compatible pigtails and

Re: Latency with run0 interface

2022-03-13 Thread Stuart Henderson
On 2022-03-14, rea...@catastrophe.net wrote: >>>If not, consider hunting down a mini PCIe iwm(4) 7260 card, or an >>>M.2 AX200 iwx(4) card with an adapter from M.2 to mini PCIe. >>>Both would need compatible pigtails and antennas as well. > > So I tried one obtained from here [1] but it sadly

Re: Latency with run0 interface

2022-03-13 Thread readme
On Fri, Mar 11, 2022 at 02:41:05PM -0600, rea...@catastrophe.net wrote: >On Fri, Mar 11, 2022 at 09:01:41PM +0100, Stefan Sperling wrote: >>On Fri, Mar 11, 2022 at 10:57:56AM -0600, rea...@catastrophe.net wrote: >>> I'm using a Panda Express USB WiFi dongle on a PC Engines apu4 machine. >> >>This

Re: Latency with run0 interface

2022-03-12 Thread Stuart Henderson
On 2022-03-12, Stefan Sperling wrote: > On Fri, Mar 11, 2022 at 02:41:05PM -0600, rea...@catastrophe.net wrote: >> >If not, consider hunting down a mini PCIe iwm(4) 7260 card, or an >> >M.2 AX200 iwx(4) card with an adapter from M.2 to mini PCIe. >> >Both would need compatible pigtails and

Re: Latency with run0 interface

2022-03-12 Thread Stefan Sperling
On Fri, Mar 11, 2022 at 02:41:05PM -0600, rea...@catastrophe.net wrote: > >If not, consider hunting down a mini PCIe iwm(4) 7260 card, or an > >M.2 AX200 iwx(4) card with an adapter from M.2 to mini PCIe. > >Both would need compatible pigtails and antennas as well. > > Thanks, I'll get a 7260. Do

Re: Latency with run0 interface

2022-03-11 Thread readme
On Fri, Mar 11, 2022 at 09:01:41PM +0100, Stefan Sperling wrote: >On Fri, Mar 11, 2022 at 10:57:56AM -0600, rea...@catastrophe.net wrote: >> I'm using a Panda Express USB WiFi dongle on a PC Engines apu4 machine. > >This is a strange choice on an APU. Such dongles are really a last >resort, they

Re: Latency with run0 interface

2022-03-11 Thread Stefan Sperling
On Fri, Mar 11, 2022 at 10:57:56AM -0600, rea...@catastrophe.net wrote: > I'm using a Panda Express USB WiFi dongle on a PC Engines apu4 machine. This is a strange choice on an APU. Such dongles are really a last resort, they tend to suffer from cooling issues and small antennas, and OpenBSD only

Latency with run0 interface

2022-03-11 Thread readme
I'm using a Panda Express USB WiFi dongle on a PC Engines apu4 machine. Basic SSH sessions to the device run decent, but when any sort of data transfer is done to the device (even serving back pfstat images from the device's local httpd), I notice high latency. # ifconfig run0 run0: