| 29 Oct 2025 |
 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 is MT7922 which 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, or nixos-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 |
| crushing-smite | * probably nixos issues itself, cause after me pointing out some issues, it caused a chat between emily and ElvishJerricco yesterday in main NixOS channel (gets stuck at reloading + requires a dbus reload) | 21:23:26 |
| crushing-smite | * probably nixos issues itself, cause after me pointing out some issues with my setup, it caused a chat between emily and ElvishJerricco yesterday in main NixOS channel (gets stuck at reloading + requires a dbus reload) | 21:23:34 |
 ElvishJerricco | I mean, my conclusion in that conversation was "nixos-rebuild did totally normal stuff w.r.t. reloading dbus / networkd and I don't know why it got stuck" | 21:23:36 |
| crushing-smite | I would rebuild for loglevel=0 slightly later, as the router is currently in active use | 21:24:22 |
|  Nico joined the room. | 21:38:05 |
