Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unclear: 40 MHz station on channel 1? #4

Open
knarrff opened this issue Nov 30, 2023 · 0 comments
Open

unclear: 40 MHz station on channel 1? #4

knarrff opened this issue Nov 30, 2023 · 0 comments

Comments

@knarrff
Copy link

knarrff commented Nov 30, 2023

The output of 'iwinfo' produces on one of the local stations:

Cell 04 - Address: REDACTED
          ESSID: "REDACTED"
          Mode: Master  Frequency: 2.412 GHz  Band: 2.4 GHz  Channel: 1
          Signal: -91 dBm  Quality: 19/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 1
                    Secondary Channel Offset: no secondary
                    Channel Width: 40 MHz or higher
          VHT Operation: 
                    Center Frequency 1: 1
                    Center Frequency 2: 0
                    Channel Width: 20 or 40 MHz

Note the last line: "channel width 20 or 40 MHz". This is on 2 GHz: there can (should) not be a 40 MHz station with a center channel of 1. What might maybe just be a little bit odd translates in LUCI receiving the following (in channel_analysis.js as res:

vht_operation: Object { channel_width: 40, center_freq_1: 1, center_freq_2: 0 }
center_freq_1: 1
​​center_freq_2: 0
​​channel_width: 40

This looks wrong to me. Either the width is 20 MHz with channel 1, or the width is 40 MHz, but the center channel is 3 (or there would be some other way than the center channel to know if the secondary channel is "above" or "below" (like for HT, but this is about VHT operation, which does not seem to have that notion). There must be a bug someplace, and I would be willing to hunt, but I am new and could use a hint as to where to start. Is this more likely a bug in iwinfo or in the device driver?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant