On 2019-07-26, Stefan Sperling wrote:
Internally to net80211, there are two channels: The 'default' channel
(referred to as "ic_ibss_chan" in source code) and the 'desired'
channel (referred to as "ic_des_chan" in source code).
The default channel is initialized when the driver attaches (usually
to channel 1). Monitor mode uses this default channel, which you've
modified while the interface was in monitor mode.
ifconfig shows this channel while the interface is down.
Furthermore, the channel for each known AP is stored alongside other
data such as the AP's SSID. While the interface is up, ifconfig shows
the channel of the currently selected AP. This selection is ineffective
in monitor mode because no connection to any AP is initiated, but data
from the previous connection is still there and is being displayed.
So as far as I understand, when I issued
# ifconfig iwn0 mediaopt monitor chan 4
I have modified the *default channel*, which monitor mode uses? And in
monitor mode, what `ifconfig iwn0` shows as the AP (after 'ieee80211:')
can be disregarded, including the channel, because those settings are
ineffective in monitor mode?
But this would mean that the interface is indeed set to use channel 4,
as desired. However:
---snip---
# airodump-ng --channel 4 iwn0
CH 4 ][ Elapsed: 1 min ][ 2019-07-26 13:48 ][ fixed channel iwn0: 12
...
---snip---
Is this an issue with aircrack-ng? Did I misunderstand you?
I would be happy about patches which make monitor mode less confusing
to use but I won't fix trivial things like this myself because there
are more important things which need fixing in the wireless stack.
I am considering contributing to the project myself, but I am afraid my
knowledge is not quite there yet.
And thank you for your response!
--
Bertalan Z. Péter <bertalan.pe...@bertalanp99.eu>
FB9B 34FE 3500 3977 92AE 4809 935C 3BEB 44C1 0F89
/"\
\ / ASCII Ribbon Campaign
X against HTML email & proprietary attachments
/ \ www.asciiribbon.org
