| 28 Oct 2025 | 
|  |  @kraynyan:tchncs.de left the room. | 23:56:27 | 
| 29 Oct 2025 | 
|  |  danishsouls joined the room. | 15:51:50 | 
|  crushing-smite | Wireless chip is MT7922. And here's mywireless.nix: {
  config,
  lib,
  pkgs,
  ...
}: {
    boot.extraModprobeConfig = ''
        options cfg80211 ieee80211_regdom="DE"
    '';
    hardware.wirelessRegulatoryDatabase = true;
    services.hostapd = {
        enable = true;
        radios."wlp5s0" = {
            settings.ieee80211h = lib.mkForce false;
            wifi5 = {
                enable = true;
                operatingChannelWidth = "20or40";
                require = true;
            };
            countryCode = "DE";
            channel = 36;
            band = "5g";
            networks.wlp5s0 = {
                logLevel = 1;
                ssid = "SsidName";
                authentication = {
                    mode = "wpa3-sae";
                    saePasswords = [
                        { password = "Password"; }
                    ];
                    enableRecommendedPairwiseCiphers = true;
                };
                settings = {
                    bridge = "br0";
                    beacon_int = 50;
                };
            };
        };
    };
}
 Issues: 
Only Linux and MacOS clients can connect to this network. iOS 18 and Windows 11, both obviously supporting Wifi5, cannot connect to it - it is visible in the list of networks, but both fail upon connection try.On Linux and MacOS, it takes some time for network to become visible in the list. On Linux via nmcli dev wifi listit may take even a minute or two for it to show up. This is not a recurring issue, but it happens about 1/3 of all the times.I could not switch operatingChannelWidth = "20or40";to80- I can apply the option, the system rebuilds and boots fine, network is visible and allows to connect to, there is WAN, but network itself is still 20 MHz (not even 40), as confirmed by bothcat /run/hostapd/wlp5s0.hostapd.confon router (output below) andwavemonon Linux client (reportswidth: 20 MHz). Please also mind ht_capab and vht_capab (looks suspisious to me). [root@nixos:~]# cat /run/hostapd/wlp5s0.hostapd.conf
# Radio base configuration: wlp5s0
################################
channel=36
country_code=DE
driver=nl80211
ht_capab=[HT40][SHORT-GI-20][SHORT-GI-40]
hw_mode=a
ieee80211ac=1
ieee80211d=1
ieee80211h=0
ieee80211n=1
noscan=0
require_ht=0
require_vht=1
vht_capab=
vht_oper_chwidth=0
# BSS 0: wlp5s0
################################
interface=wlp5s0
ap_isolate=0
auth_algs=1
beacon_int=50
bridge=br0
ctrl_interface=/run/hostapd
ctrl_interface_group=wheel
ieee80211w=1
ignore_broadcast_ssid=0
logger_stdout=-1
logger_stdout_level=1
logger_syslog=-1
logger_syslog_level=1
macaddr_acl=0
rsn_pairwise=CCMP GCMP GCMP-256
sae_pwe=2
sae_require_mfp=1
ssid=SsidName
transition_disable=0x01
utf8_ssid=1
wmm_enabled=1
wpa=2
wpa_key_mgmt=SAE
wpa_pairwise=CCMP GCMP GCMP-256
sae_password=password
 | 21:09:23 | 
|  crushing-smite | Now, how to troubleshoot/which other info do you need? | 21:09:39 | 
|  K900 | Check hostapd logs for when your clients fail to associate | 21:13:50 | 
|  crushing-smite | brb | 21:13:57 | 
|  K900 | Also depending on the hardware Windows especially can be iffy about WPA3-only APs | 21:14:23 | 
|  crushing-smite | Nothin in there | 21:15:01 | 
|  crushing-smite | Tried from WIn 11, which says "Can't connect to this network", but nothing new via journalctl -u hostapd --follow | 21:15:27 | 
|  K900 | You probably want to set the log level to 0 | 21:15:44 | 
|  crushing-smite | remind me how to please | 21:16:02 | 
|  crushing-smite | and would ir trequire a rebuild/reboot | 21:16:07 | 
|  K900 | Rebuild and hostapd restart | 21:16:17 | 
|  K900 | There's an option | 21:16:19 | 
|  K900 | I forgot what it is exactly | 21:16:24 | 
|  K900 | Also, wlp5s0 looks like running an AP off a desktop/laptop? Which means it's very possible your wireless chip just doesn't support AP operation at higher rates | 21:17:08 | 
|  K900 | That is fairly normal | 21:17:38 | 
|  K900 | Especially for not-latest hardware | 21:17:45 | 
|  K900 | Intel chips are also very picky about how they'll operate in AP mode on top of normal regulatory restrictions for whatever reason | 21:18:31 | 
|  crushing-smite | What do you mean a running of laptop/desktop? It isMT7922which was suggested by you 2 or so years ago specifically for AP purposes, and it is inside a standalone router (NUC-like). It supports Wifi6/7 too. | 21:20:37 | 
|  K900 | I mean not an actual AP designed to operate as an AP | 21:21:07 | 
|  K900 | But yes MT7922 should be able to run at those rates | 21:21:18 | 
|  crushing-smite | nixos-rebuid boot+systemctl restart hostapd, ornixos-rebuild switch(latter would require a reboot)? | 21:21:27 | 
|  crushing-smite | elaborate please | 21:21:36 | 
|  K900 | nixos-rebuild switch | 21:21:48 | 
|  K900 | Why would that require a reboot? | 21:21:48 | 
|  K900 | Most actual access points, as in hardware that is explicitly sold as an access point (home router, whatever) are purpose built to run as access points | 21:22:21 | 
|  K900 | Which in most cases means a small ARM SoC with a big wireless frontend attached | 21:22:35 | 
|  crushing-smite | probably nixos issues itself, cause it caused a chat between emily and ElvishJerricco yesterday in main NixOS channel (gets stuck at reloading + requires a dbus reload) | 21:22:46 | 
|  K900 | That sounds very wrong | 21:23:01 |