Firmware 2.308 Adguard Home running , VPN OpenVPN Client in use, Killswith enaged, VPN policy
In the past 24 hours 2.4GHz can not be accessed on LAN WiFi or Guest WiFi, can only use 5G network. ESSID are different. When trying to connect from different computers it states can not connect.
I suspect a package was updated incorrectly pertaining to routing tables or Firewall zones.
I have a roku device that is only supposed to connect to the guest network but is showing up as connected to regular network 2.4 ghz, guest network 2.4ghz and guest network 5G. I have different subnets for the regular network(192.168.1.1 DHCP lease starts at 100-249) network and Guest(192.168.2.1 DHCP lease starts at 100-249). the Roku has never connected to the regular network
2.4G was able to be used about 48 hours ago. It has bandwidth set to 20 mhz for older devices. 5G is set to 80mhz. Tried setting 5G to 20/40/80 mhz and all 2.4G disappeared returned 5G to 80mhz and 2.4G came back but still can’t connect.
The issue I had with the Roku was my doing I think having the wrong static IP address assigned(I put 192.168.1.100 instead of 192.168.2.100)
Right now nothing will connect 2.4G
Log:
Mon Jan 24 11:12:22 2022 daemon.info hostapd: ath0: STA 2a:b7:d3:68:77:86 IEEE 802.11: associated (aid 2)
Mon Jan 24 11:12:22 2022 daemon.info hostapd: ath0: STA 2a:b7:d3:68:77:86 WPA: sending 1/4 msg of 4-Way Handshake
Mon Jan 24 11:12:22 2022 daemon.info hostapd: ath0: STA 2a:b7:d3:68:77:86 WPA: sending 1/4 msg of 4-Way Handshake
Mon Jan 24 11:12:22 2022 daemon.info hostapd: ath0: STA 2a:b7:d3:68:77:86 WPA: received EAPOL-Key frame (2/4 Pairwise)
Mon Jan 24 11:12:22 2022 daemon.info hostapd: ath0: STA 2a:b7:d3:68:77:86 WPA: sending 3/4 msg of 4-Way Handshake
Mon Jan 24 11:12:22 2022 daemon.info hostapd: ath0: STA 2a:b7:d3:68:77:86 WPA: received EAPOL-Key frame (4/4 Pairwise)
Mon Jan 24 11:12:22 2022 daemon.info hostapd: ath0: STA 2a:b7:d3:68:77:86 RADIUS: starting accounting session D39A814ECFA1D0E5
Mon Jan 24 11:12:22 2022 daemon.info hostapd: ath0: STA 2a:b7:d3:68:77:86 WPA: pairwise key handshake completed (RSN)
Mon Jan 24 11:12:26 2022 daemon.info dnsmasq-dhcp[31021]: DHCPDISCOVER(br-lan) 2a:b7:d3:68:77:86
Mon Jan 24 11:12:26 2022 daemon.info dnsmasq-dhcp[31021]: DHCPOFFER(br-lan) 192.168.1.102 2a:b7:d3:68:77:86
Mon Jan 24 11:12:26 2022 daemon.info dnsmasq-dhcp[31021]: DHCPREQUEST(br-lan) 192.168.1.102 2a:b7:d3:68:77:86
Mon Jan 24 11:12:26 2022 daemon.info dnsmasq-dhcp[31021]: DHCPACK(br-lan) 192.168.1.102 2a:b7:d3:68:77:86
Mon Jan 24 11:13:29 2022 daemon.info hostapd: ath3: STA 52:8e:6e:03:f6:bc IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Jan 24 11:13:29 2022 daemon.info hostapd: ath3: STA 52:8e:6e:03:f6:bc IEEE 802.11: disassociated
Mon Jan 24 11:23:33 2022 daemon.info hostapd: ath0: STA 2a:b7:d3:68:77:86 IEEE 802.11: disassociated
Mon Jan 24 11:23:34 2022 daemon.info hostapd: ath1: STA 5e:25:e7:52:42:10 IEEE 802.11: authenticated
Mon Jan 24 11:23:34 2022 daemon.info hostapd: ath1: STA 5e:25:e7:52:42:10 IEEE 802.11: authenticated
Mon Jan 24 11:23:35 2022 daemon.info hostapd: ath1: STA 5e:25:e7:52:42:10 IEEE 802.11: authenticated
Mon Jan 24 11:23:36 2022 daemon.info hostapd: ath1: STA 5e:25:e7:52:42:10 IEEE 802.11: authenticated
Mon Jan 24 11:23:36 2022 daemon.info hostapd: ath1: STA 5e:25:e7:52:42:10 IEEE 802.11: authenticated
Mon Jan 24 11:23:37 2022 daemon.info hostapd: ath1: STA 5e:25:e7:52:42:10 IEEE 802.11: authenticated
Mon Jan 24 11:23:38 2022 daemon.info hostapd: ath1: STA 5e:25:e7:52:42:10 IEEE 802.11: authenticated
Mon Jan 24 11:23:41 2022 daemon.info hostapd: ath1: STA 5e:25:e7:52:42:10 IEEE 802.11: authenticated
Mon Jan 24 11:23:41 2022 daemon.info hostapd: ath1: STA 5e:25:e7:52:42:10 IEEE 802.11: authenticated
Mon Jan 24 11:23:42 2022 daemon.info hostapd: ath1: STA 5e:25:e7:52:42:10 IEEE 802.11: authenticated
Mon Jan 24 11:23:43 2022 daemon.info hostapd: ath1: STA 5e:25:e7:52:42:10 IEEE 802.11: authenticated
Mon Jan 24 11:23:43 2022 daemon.info hostapd: ath1: STA 5e:25:e7:52:42:10 IEEE 802.11: authenticated
Mon Jan 24 11:23:44 2022 daemon.info hostapd: ath1: STA 5e:25:e7:52:42:10 IEEE 802.11: authenticated
update:
Got 2.4ghz working not sure how. Noticed that in LuCi wifi overview showed that Generic 802.11AC(5G)WiFi0 and has BSSID 94:83:C4:12:17:25 for both my main network and guest network. Generic 802.11abgn(2.4G)WiFi1 and had a BSSID of 94:83:C4:12:17:26 for main and guest network. I then went to WiFi in LuCi and under device configuration general setup Status showed the channel of 2.4G as 6 but operating frequency Mode was NG Channel was blank and could not be changed. Disabled 2.4G for both networks turned them back (did this 2 times) on and 2.4G started working but was a open network for both(no security) went back to GL-iNet GUI and changed open to wpa2/wpa3-PSK/SAE. This allowed me to connect to 2.4G on both networks. After 5G BSSID is the same but 2.4G BSSID is now root for main and guest network ( I’m not sure if this is correct) Have not restarted and have a log of the past 48hours.
This also just happened to me on my AX-1800 in the last week. I have a printer and doorbell running on my 2.4g network (everything else is on the 5g). Yesterday I noticed that neither of those devices were connected. I then tried to connect to the 2.4g network on my phone and iPad, but they both failed to log in. I have not changed any router/wifi settings in the past week. I can’t think of an explanation as to why my 2.4g network would just stop working.
I have tried the following so far:
Disable/enable 2.4 network
Disable/enable 2.4 guest network
Change channels (it just reverted back to 5 on its own though)
Change security to WPA2 PSK (again, it reverted itself to WPA2/3 SAE/PSK)
Change password
Reboot router
Nothing has worked yet. Did you ever find out what was going on?
Kind of a dumb question do you happen to know how many restarts have been done over the life cycle of the router, I seem to remember reading that at the 10th or so this occurs and was a known glitch in something.
The 2.4G network still showed a strong connection but I couldn’t join it. My 5G network continued to function normally.
I don’t know for sure, but it was probably in the ball park of 10 restarts at this point. It’s about a month old and I have done some troubleshooting a couple of times.
While I was at work today, the 2.4G network suddenly started working again because I started to get notifications from my doorbell and printer again. No one did anything to the router while I was gone today. It just started working again!
Thats similar to what happened to me it just started working. I still reverted it with no settings saved and updated the firmware to the newest. When it occured I was changing the bandwith for 5G to 160Hz(THIS IS NOT SUPPORTED) trying to boost speed and changed 2.4G to 40hz. I think the 2.4g connects to itself and then times out after a while. Current settings a 20hz on 2,4G and 80hz on 5G no issues and running 3.213
It’s been over a month and this problem has continued to persist. I reverted my router to factory settings and set it back up today. The 2.4ghz network worked for a few minutes but it stopped working again. I made sure that Wireguard and Tailscale weren’t interfering with it for some reason. I don’t know what else to try.
What does the system log and kernel log show when 2.4ghz disconnects? Are you reconnecting to the network or forgetting the network and joining it again. What Wifi settings are you using? SSID is broadcasting? Could also be your computers WiFi settings some newer WiFi Cards have advance settings that favor 5 ghz by default. I have three Flints, one running openvpn server, one running wiregaurd server and one running 4.x testing and trying the new software. Sorry you having so much trouble with it.
I’ll work on pulling the logs and posting them here. I’m using the default network settings: broadcasting SSID, 40mhz bandwidth, auto channel selection, WPA2-PSK security (although I have even tried open network. Still doesn’t work). I have used a plethora if devices to try to connect. iPhone 11, iPad Pro, and a Skybell doorbell which only works on 2.4ghz networks. Upon trying to connect using an Apple device, it simply says “unable to connect to network”. It won’t even remember the SSID or store the password. But it remains in the available network list. So to be clear, it’s not that I’m not getting internet access through the 2.4 network. I can’t even connect to it at all. Super strange.
try a bandwidth of 20 MHz only, Change to 802.11 b/g/n in WiFi mode, Change you channel to 1,6,11 if possible I have my security set to wpa2/wpa3-PSK/SAE
You may also want to change the SSID and only connect with one computer
I recently purchased a Flint (GL-AX1800), and while installing and testing it at home, I had the exact same 2.4GHz access point problem (SSID lost, unable to connect even when displayed, signal strength of -0dBm when viewed on LuCI).
Strange, even though it had been working fine up to that point and I had not changed anything. I also could not find anything relevant in the system logs.
I then checked 11b/g/n/ax, 20MHz/40MHz, WPA3/WPA2/WPA, channels, and other settings and could not solve the problem, but to my surprise, after physically changing the way the Flint was placed, the 2.4GHz band started working.
Also, in my environment, it seems that the 2.4GHz band may or may not work depending on the physical placement of the device.
Maybe it is a hardware problem, not firmware…