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 argument
>
>The device should support this channel. This gives a list: ifconfig iwm0 chan
I see the channel, for sure.
$ ifconfig iwm0 chan | wc -l
46
$ ifconfig iwm0 chan | grep 132
132 5660 MHz passive scan
[..]
>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 that only supports
>2 GHz band channels.
>This should be fixed, when the user says "chan 132" ifconfig or the kernel
>should figure out that the mode needs to be switched if it is incompatible
>with the requested channel. It's one of those bugs that nobody ever runs
>into unless they are debugging things.
Unfortunately it appears as though I've run into it. Is there any recourse
to provide more useful debugging information to find the issue?
[..]
>> Even after a clean reboot I can't bring the interface up in monitor mode
>> and join anything other than channels 1-11.
>
>That is expected.
>You cannot use network in monitor mode at all, only listen to a channel.
>In order to join a network, you need to disable monitor mode again first:
>ifconfig iwm0 -mediaopt monitor -mode -chan
Good to know, thank you.
