You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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?
The text was updated successfully, but these errors were encountered:
The output of 'iwinfo' produces on one of the local stations:
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
: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?
The text was updated successfully, but these errors were encountered: