It's being difficult again. FYI, I have two different SSIDs for 2.4GHz and 5GHz so that I can be specific and know the network to which something is connecting. The 2.4GHz network to which I could connect last night appears to have become unresponsive despite not being bothered.
The laptop2 that was connecting to the 2.4GHz network (that's all it has) in ubuntu last night lost its connection and is not longer able to connect to the 2.4GHz network. It can't get an IP address. Here's what logread says:
Tue Apr 4 20:07:33 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:07:45 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED <LAPTOP2_MAC>
Tue Apr 4 20:08:03 2023 daemon.info hostapd: wlan0: STA <LAPTOP2_MAC> IEEE 802.11: authenticated
Tue Apr 4 20:08:03 2023 daemon.info hostapd: wlan0: STA <LAPTOP2_MAC> IEEE 802.11: associated (aid 1)
Tue Apr 4 20:08:03 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED <LAPTOP2_MAC>
Tue Apr 4 20:08:03 2023 daemon.info hostapd: wlan0: STA <LAPTOP2_MAC> WPA: pairwise key handshake completed (RSN)
Tue Apr 4 20:08:03 2023 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED <LAPTOP2_MAC>
Tue Apr 4 20:08:03 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:08:05 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:08:07 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:08:12 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:08:20 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:08:37 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:08:49 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED <LAPTOP2_MAC>
Tue Apr 4 20:08:50 2023 daemon.info hostapd: wlan0: STA <LAPTOP2_MAC> IEEE 802.11: authenticated
Tue Apr 4 20:08:50 2023 daemon.info hostapd: wlan0: STA <LAPTOP2_MAC> IEEE 802.11: associated (aid 1)
Tue Apr 4 20:08:50 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED <LAPTOP2_MAC>
Tue Apr 4 20:08:50 2023 daemon.info hostapd: wlan0: STA <LAPTOP2_MAC> WPA: pairwise key handshake completed (RSN)
Tue Apr 4 20:08:50 2023 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED <LAPTOP2_MAC>
Tue Apr 4 20:08:50 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:08:52 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:08:54 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:08:59 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:09:07 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:09:24 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:09:36 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED <LAPTOP2_MAC>
Tue Apr 4 20:09:37 2023 daemon.info hostapd: wlan0: STA <LAPTOP2_MAC> IEEE 802.11: authenticated
Tue Apr 4 20:09:37 2023 daemon.info hostapd: wlan0: STA <LAPTOP2_MAC> IEEE 802.11: associated (aid 1)
Tue Apr 4 20:09:37 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED <LAPTOP2_MAC>
Tue Apr 4 20:09:37 2023 daemon.info hostapd: wlan0: STA <LAPTOP2_MAC> WPA: pairwise key handshake completed (RSN)
Tue Apr 4 20:09:37 2023 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED <LAPTOP2_MAC>
Tue Apr 4 20:09:37 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:09:39 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:09:41 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:09:46 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:09:55 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:10:12 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:10:23 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED <LAPTOP2_MAC>
It seems like it keeps trying to join the network and these messages repeat over time.
When I try this on the windows partition of laptop2, it has trouble connecting but then says it's connected with no internet. Laptop2 can't reach URLs via a browser. Under the properties of the wifi connection, windows doesn't report having an IPv4 address. Luci says it has an associated station with the MAC address, but no dhcp lease. I've redacted the MAC to identify it as the windows logs, but it's the same value.
Tue Apr 4 20:34:18 2023 daemon.info hostapd: wlan0: STA <LAPTOP2_MAC_WINDOWS> IEEE 802.11: authenticated
Tue Apr 4 20:34:18 2023 daemon.info hostapd: wlan0: STA <LAPTOP2_MAC_WINDOWS> IEEE 802.11: associated (aid 1)
Tue Apr 4 20:34:18 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED <LAPTOP2_MAC_WINDOWS>
Tue Apr 4 20:34:18 2023 daemon.info hostapd: wlan0: STA <LAPTOP2_MAC_WINDOWS> WPA: pairwise key handshake completed (RSN)
Tue Apr 4 20:34:18 2023 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED <LAPTOP2_MAC_WINDOWS>
Tue Apr 4 20:34:18 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:34:22 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:34:26 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:34:34 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:34:51 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:35:24 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:35:29 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:35:37 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:35:53 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
EDIT: Though I don't have the logs (and don't expect them to provide any new info), laptop1 is also unable to connect to the 2.4GHz network in both with ubuntu partition (which has connected in the past) nor the windows partition (which hadn't connected to the network device at all previous to this)/
When I try to connect my Android (in case that's significant) phone to the 2.4GHz network, it won't connect either. It hadn't connected to any of the networks at the time when i tried this. Here are the logs for that connection attempt:
Tue Apr 4 20:19:09 2023 daemon.info hostapd: wlan0: STA <PHONE_MAC> IEEE 802.11: authenticated
Tue Apr 4 20:19:09 2023 daemon.info hostapd: wlan0: STA <PHONE_MAC> IEEE 802.11: associated (aid 1)
Tue Apr 4 20:19:10 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED <PHONE_MAC>
Tue Apr 4 20:19:10 2023 daemon.info hostapd: wlan0: STA <PHONE_MAC> WPA: pairwise key handshake completed (RSN)
Tue Apr 4 20:19:10 2023 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED <PHONE_MAC>
Tue Apr 4 20:19:11 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:19:12 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:19:14 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:19:18 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:19:26 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan0 which has no address
Tue Apr 4 20:19:29 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED <PHONE_MAC>
Tue Apr 4 20:19:29 2023 daemon.info hostapd: wlan0: STA <PHONE_MAC> IEEE 802.11: disassociated
Tue Apr 4 20:19:30 2023 daemon.info hostapd: wlan0: STA <PHONE_MAC> IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Tue Apr 4 20:19:33 2023 daemon.warn dnsmasq-dhcp[1]: no address range available for DHCP request via br-lan
Tue Apr 4 20:19:34 2023 daemon.warn dnsmasq-dhcp[1]: no address range available for DHCP request via br-lan
Tue Apr 4 20:19:34 2023 daemon.warn dnsmasq-dhcp[1]: no address range available for DHCP request via br-lan
The last messages look like they're not related even though they happen at the same time. They look suspicious as well. Nobody should be making dhcp requests via br-lan - at least not the way it's configured now (I'd like to eventually have two of the four lan ports exist on the same network as the wifi, but that's for later).
I'm not sure why the 2.4GHz network seemed fine before, but refuses connection requests (including ones it had before) now without any changes to the config. I tried to rtfm a bit to see if this "new" error was something that had a clear path forward. I see some older threads that necessarily run on an older version of the software than I'm using also evidenced by the fact that a page that used to have a possible answer doesn't even exist anymore so I'm wary of applying fixes or workarounds that may not be necessary or even advised anymore. It seems like the leading possibility to solve this new issue (if it is the issue) might be something like this wlan bridge, but I don't totally understand what's happening here and don't want to make willy-nilly changes without guidance or direction so I don't break things even more or put things in a state that we all haven't agreed upon. I also suspect if it was something that we needed that someone would noticed it already and identified it as a problem.
EDIT: The laptop1 (with a 5GHz radio) is able to connect to the 5GHz network in both the ubuntu and windows partitions. The android phone is also able to connect to the 5GHz network.