I'm encountering a strange issue on my Slate 7: under specific configurations, its DHCP server does not seem to work normally after reboots.
To reproduce:
Make sure a Slate 7 is on firmware 4.7.3 and is awaiting initialization.
Set it to Repeater mode and connect it to an existing 802.11ac Wi-Fi network.
Disable Slate's 2.4GHz and 5GHz Wi-Fi; leave only MLO active.
In the GL stock UI, configure the following:
Enable DNS Rebinding Attack Protection, Override DNS Settings of All Clients, and Cloudflare ODoH;
Enable IGMP Snooping version 3;
Create an LCD display schedule;
Change the ports for Admin Panel and LuCI to random ports, and enable Force HTTPS for both of them.
In LuCI, configure the following:
Under Network > Interfaces > Global Network Options, enable Packet Steering;
Under Network > Firewall, enable Software Flow Offloading and Hardware Flow Offloading.
Make sure client devices can access the internet normally. Then reboot the Slate, either using the web panel or by cutting off power. Wait for the reboot to complete.
Client devices, whether by cable or by Wi-Fi, will have difficulty connecting to the Slate. Even if connected, they will be unable to access the internet. If using macOS, System Settings > Network may show "Self-Assigned IP".
I've previously documented this strange problem in Reddit; after GL's email support suspected there's a hardware issue they did an RMA but I could still reproduce this symptom even on the new router. Hopefully someone could replicate the issue and submit it to the devs.
Could you also try these steps to reproduce on a Flint 3? I just received my Flint 3 and based on my preliminary testing it has exactly this same bug as Slate 7. My Flint 3 runs firmware 4.7.11. (Is it the latest firmware, by the way? I saw references of 4.7.13 somewhere else on the forum but the router won't show it as an update.)
According to the latest firmware version of the firmware download center, which it is v4.7.11, v4.7.13 has not been officially released yet, please wait.
We also reproduced this problem on Flint3.
The issue is caused by the Luci firewall accelerate rules flow_offloading '1' and flow_offloading_hw '1'.
The accelerate of Flint3 and Slate 7 use qca-nss-ecm module, which is not adapted with the Luci. After configuring it in Luci, and the /etc/init.d/firewall restart will report the errors, or aftet restarting the router, the firewall LAN rule is lost (br-lan traffic does not allow access to the router local service), resulting in all services are unable to access, like DHCP, SSH and Web UI, etc.
Please configure "disable/enable" the network accelerate feature in the GL GUI.
@bruce and @Harvey1 what is interesting is that Qualcomm advertises this chipset as being "Openwrt, Linux Kernel 5.4 supported" and "Open API porting for multi-source development (OpenWRT, RDK-B, PrplOS) and support of OpenSync™ and TIP OpenWiFi for easy integration of customized services" in their product brief. @bruce someone from your sourcing team should really jump on Qualcomm as they are not holding up their end of the deal. Immersive-Home-3210-product-brief.zip (121.3 KB)
Also in Flint 2 with latest Nightly, the option Sw and Hw Offloading from Lucy uncheck after reboot. Also notice the option Network Acceleration enables after reboots. Theses 3 options changes in the next reboot. Had to manually enable and disables. Very annoying. Any suggestion?