The mac ageing timeout on the bridge interface is exactly 5 minutes.
Maybe it has something to do with it?
But hostapd directly runs on the wlan* interface(s) so that would be a bit strange?
You can also increase the inactivity timer with max_inactivity option.
I patched my builds to have a mac ageing timeout of 35minutes.
Also patched the default ARP/NDP timeouts to 20 minutes
(because there is this random timer thing (*3/2) it can be high as 30 minutes.)
The default 60sec seems a bit low...
It says in inactivity timeout options that the default max inactivity is 5 minutes so that's probably why. For disassoc_low_ack it says "This depends on the driver capabilities and may not be available with all drivers." Does the option not work with WRT1900ACS?
Stubby is just query encrypt system, and only support DoT (DNS-Over-TLS), not DoH (DNS-Over-HTTPS).
SmartDNS is DNS accelerator first - it have nice features to decrease overall DNS latency and uses zone prefetch as well. Really faster responses in my case. And as a bonus it supports both DoH and DoT for uplink DNS connections.
At my router, with heavy caching, it's only uses 5M of RAM.
2all: I experiment with 160Mhz at 5.x core. Now it works in low channels (36,40) as well. Still not so stable and some adapters can't connect, but if it works i got 110-115MBps from Samba instead of 70 (seems like Samba have no speed cap, but connection are).
Got to be careful with Adblock as well. It’s now V4.0.5 in this build. Pre V4 is different.
Followed your advice by doing backup, modified the backup tarball, sysupgrade straight - no carry config, restore modded backup.
So, restoring the adblock config from v3.x to v4.x broke my dnsmasq. Can no longer use any “option serversfile “ entries, and lost all resolution.
So, if upgrading from Adblock V3.x to V4.x, don’t carry over the config. Edit /etc/config/dhcp and comment out any “option serversfile” entries. In luci Adblock interface set your NV Storage for Backup and Report dirs and take the defaults for everything else. Go from there.
.
To put a bit more nuance into my statement (read the article and didn't do enough research on the OpenWRT function), by default the setting is enabled and the "no acks" come from Android and iOS devices so the advice of OpenWRT is to disable it (https://openwrt.org/faq/disconnected_due_to_excessive_missing_acks). Which lowers the reliability of the network in the end.
The only issue I had with Wi-Fi disconnecting after a while was on 5Ghz, I named my 2.4Ghz and 5Ghz the same and since that moment I never lose Wi-Fi connection now on my Android devices. On my laptop it always goes to 5Ghz and never dissacotiates though, so not sure if this is a hacky/coincidental solution or the way it was intended.
So, now I was not giving the complete picture and wanted to right that. So the conclusion is, that disabling the no ack setting (which is enabled by default) could solve issues, which I do not experience on any device since I named my networks the same and have switch between 2.4 and 5Ghz networks themselves.
Enabling skip_inactivity_poll (set to 1) will immediately disconnect stations when they are idle for amount of time specified by max_inactivity without doing a check before disconnecting the station.
Which is what I said
Maybe I didn't come over like that, then I hope this clarifies it. Just explaining the settings and that effectively it will not matter. I now run with no ack on (which presumably keeps disconnecting, if disabling it is even supported in mwlwifi) and I do not have issues with the r13342 build and unified naming for 2.4/5Ghz bands. Even with it disabled it keeps disconnecting on 5Ghz on my Android devices (and falling back on the 2.4Ghz, so I always am connected to my Wi-Fi).
So my assumption is that either the mwlwifi driver doesn't support turning "Disassociate On Low Acknowledgement" off or it is intended behavior on the 5Ghz band. Either way, you don't want low acknowledgements polluting the ether on 5Ghz, so I think (even if it isn't intended behavior on the 5Ghz with the setting off) it is good that this happens on the 5Ghz band as it is commonly used for more speed and reliable services.
I have:
disassoc_low_ack 0
max_inactivity to 1800 (30 min)
dtim_period 3
wpa_group_rekey 86400 (24h)
Works fine for my (Android) devices.
When you only have a few devices and never reach the AP station limit (255?) I think it's save to increase max_inactivity to 24h.
The wpa_group_rekey option maybe can also cause hiccups in connectivity.
Hostapd's default is 24h for WPA2 with AES.
OpenWRT used to set a lower value (5min) for security reasons? But I'm not sure if this is still the case.
After upgrading to r13342 from r12394 my Apple devices aren't working correctly if they have IPv6 enabled. Some web pages partially load or don't load at all until I set IPv6 to link-local or drop off wifi to cellular. My windows devices don't seem to be having issues. Sites like test-ipv6.com give full marks for all devices (both Apple and non-Apple) I've tested it on. I can access ipv6.google.com when I have IPv6 enable on my apple devices.
After my first attempt for r13342 I wiped my settings and started fresh but the issue persists. dnscrypt-proxy2 has ipv6 enabled and listening. My devices have dhcp6 leases and ip addresses.
One example website I've been having issues with is facebook. I can see the top of the page but once I start scrolling I just get empty content. The web developer menu shows requests to static.xx.fbcdn.net but they just hang forever. I can nslookup the AAAA record from my mac and it resolves. Once I disable IPv6 the requests go through.