* [ISSUE] hostapd: 2.10 breaks ap functionality
@ 2022-02-05 18:06 zlice
2022-02-14 5:29 ` zlice
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: zlice @ 2022-02-05 18:06 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1892 bytes --]
New issue by zlice on void-packages repository
https://github.com/void-linux/void-packages/issues/35420
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
`Void 5.15.12_1 x86_64 AuthenticAMD notuptodate rFF`
* package:
`hostapd-2.9_3`
### Expected behavior
Wireless AP starts
### Actual behavior
*dmesg*
```
[ 943.200854] br0: port 5(wifi0) entered blocking state
[ 943.200861] br0: port 5(wifi0) entered disabled state
[ 943.200957] device wifi0 entered promiscuous mode
[ 943.201616] device wifi0 left promiscuous mode
[ 943.201650] br0: port 5(wifi0) entered disabled state
```
*hostapd*
```
hostapd -S /etc/hostapd/hostapd.conf
ACS: Automatic channel selection started, this may take a bit
ACS: No available channels found
wifi0: IEEE 802.11 Configured channel (0) or frequency (0) (secondary_channel=0) not found from the channel list of the current mode (2) IEEE 802.11a
wifi0: IEEE 802.11 Hardware does not support configured channel
Could not select hw_mode and channel. (-3)
wifi0: interface state UNINITIALIZED->DISABLED
wifi0: AP-DISABLED
wifi0: Unable to setup interface.
wifi0: interface state DISABLED->DISABLED
wifi0: AP-DISABLED
wifi0: CTRL-EVENT-TERMINATING
hostapd_free_hapd_data: Interface wifi0 wasn't started
nl80211: deinit ifname=wifi0 disabled_11b_rates=0
nl80211: Failed to remove interface wifi0 from bridge br0: Invalid argument
```
### Steps to reproduce the behavior
*lspci*
`0b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)`
tried changing channels, `iw reg set` region, moving around bridge and interfaces, "wds" and "4addr" settings i found. reverting to 2.9 allows AP to start.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: hostapd: 2.10 breaks ap functionality
2022-02-05 18:06 [ISSUE] hostapd: 2.10 breaks ap functionality zlice
@ 2022-02-14 5:29 ` zlice
2022-02-14 20:25 ` [ISSUE] [CLOSED] " zlice
2022-02-14 20:25 ` zlice
2 siblings, 0 replies; 4+ messages in thread
From: zlice @ 2022-02-14 5:29 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
New comment by zlice on void-packages repository
https://github.com/void-linux/void-packages/issues/35420#issuecomment-1038661491
Comment:
more precise `-dd`
```
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=30 dBm
ACS: Automatic channel selection started, this may take a bit
ACS: No available channels found
wifi0: IEEE 802.11 Configured channel (0) or frequency (0) (secondary_channel=1) not found from the channel list of the current mode (2) IEEE 802.11a
wifi0: IEEE 802.11 Hardware does not support configured channel
Could not select hw_mode and channel. (-3)
wifi0: interface state UNINITIALIZED->DISABLED
wifi0: AP-DISABLED
```
Pretty sure this is a hostapd, firmware or kernel bug (or a combination or all three? i can't keep up with wifi on linux, swear something changes every time a dev sneezes thinking of wifi). But I have tried everything at this point, hostapd-2.10 is broken.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ISSUE] [CLOSED] hostapd: 2.10 breaks ap functionality
2022-02-05 18:06 [ISSUE] hostapd: 2.10 breaks ap functionality zlice
2022-02-14 5:29 ` zlice
@ 2022-02-14 20:25 ` zlice
2022-02-14 20:25 ` zlice
2 siblings, 0 replies; 4+ messages in thread
From: zlice @ 2022-02-14 20:25 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
Closed issue by zlice on void-packages repository
https://github.com/void-linux/void-packages/issues/35420
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
`Void 5.15.12_1 x86_64 AuthenticAMD notuptodate rFF`
* package:
`hostapd-2.9_3`
### Expected behavior
Wireless AP starts
### Actual behavior
*dmesg*
```
[ 943.200854] br0: port 5(wifi0) entered blocking state
[ 943.200861] br0: port 5(wifi0) entered disabled state
[ 943.200957] device wifi0 entered promiscuous mode
[ 943.201616] device wifi0 left promiscuous mode
[ 943.201650] br0: port 5(wifi0) entered disabled state
```
*hostapd*
```
hostapd -S /etc/hostapd/hostapd.conf
ACS: Automatic channel selection started, this may take a bit
ACS: No available channels found
wifi0: IEEE 802.11 Configured channel (0) or frequency (0) (secondary_channel=0) not found from the channel list of the current mode (2) IEEE 802.11a
wifi0: IEEE 802.11 Hardware does not support configured channel
Could not select hw_mode and channel. (-3)
wifi0: interface state UNINITIALIZED->DISABLED
wifi0: AP-DISABLED
wifi0: Unable to setup interface.
wifi0: interface state DISABLED->DISABLED
wifi0: AP-DISABLED
wifi0: CTRL-EVENT-TERMINATING
hostapd_free_hapd_data: Interface wifi0 wasn't started
nl80211: deinit ifname=wifi0 disabled_11b_rates=0
nl80211: Failed to remove interface wifi0 from bridge br0: Invalid argument
```
### Steps to reproduce the behavior
*lspci*
`0b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)`
tried changing channels, `iw reg set` region, moving around bridge and interfaces, "wds" and "4addr" settings i found. reverting to 2.9 allows AP to start.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: hostapd: 2.10 breaks ap functionality
2022-02-05 18:06 [ISSUE] hostapd: 2.10 breaks ap functionality zlice
2022-02-14 5:29 ` zlice
2022-02-14 20:25 ` [ISSUE] [CLOSED] " zlice
@ 2022-02-14 20:25 ` zlice
2 siblings, 0 replies; 4+ messages in thread
From: zlice @ 2022-02-14 20:25 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 360 bytes --]
New comment by zlice on void-packages repository
https://github.com/void-linux/void-packages/issues/35420#issuecomment-1039521393
Comment:
Found a uh, workaround. Hardware works mostly, hostapd "works" mostly. So I have to assume it's a "fix" in 2.10 and firmware that's labeling things as not-usable when they damn well are and should be. lil mad. closing.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-02-14 20:25 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-05 18:06 [ISSUE] hostapd: 2.10 breaks ap functionality zlice
2022-02-14 5:29 ` zlice
2022-02-14 20:25 ` [ISSUE] [CLOSED] " zlice
2022-02-14 20:25 ` zlice
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).