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)
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
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
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
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
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
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
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
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
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
>
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
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
>
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
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
>
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
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
16 matches
Mail list logo
