It connects fine to my main router (Netgear R8000, OpenWrt 21.02.0) and I can connect wirelessly to the dumb AP fine, however, my wired clients connecting to the dumb AP do not get DHCP offers (manually setting the IP on those clients work and I can get to the internet)
Any idea why, despite everything being bridged and dnsmasq being disabled in the dumb AP, wireless clients would get DCHP offers, but wired would not?
Let me know if you need me to paste the contents of any file.
I don't think eth0 belongs in this list, unless you have something different like a USB ethernet adapter or something. Most DSA devices use named ports (i.e. lan1, wan, etc.) not the device name (eth0).
Try changing this to one of the non-overlapping channels: 1, 6, 11. Don't use any of the others.
This is a DFS channel (at least in the US)... try using one of the lower channels instead (maybe 36)
not all devices work well with WPA2/3 mixed mode operation. Try using WPA2-PSK (on both bands).
You may also want to try using 20MHz channel width for the 2.4G band, and 40MHz for the 5GHz band if you still have issues.
WPA2/3 mixed mode can cause problems when client devices don't know how to use them.
The non-overlapping channels are the same world-wide: 1, 6, 11 (some countries have more than 11 channels, but within the first 11, this is the recommended set). That is, at least, if you want to have 3 useful channels. You need to have 4 unused channels between the actual channels you are using to avoid overlap. Meanwhile, using non-standard channels can, in some cases, prevent the network from operating properly (some client devices don't like it).
Try my recommendations one at a time (starting with the wpa2 psk option) to see if any/all of them help your situation.
Also, I just looked at the Australian channels map -- you are using a DFS channel on your 5G band. Try using something that is not DFS and you may have better luck -- maybe just use channel 36 to start.
hmm... I'd love to see the default configuration file... it's probably generated at first boot.
Any chance you can take a backup and reset your router to defaults? From there you could grab the network file (/etc/config/network) as it is in the true default state. You can restore the backup if you want (although unless there is anything specific that is working and special, maybe best to start with a clean slate anyway).
That will need to wait till the weekend
Working from home this week.
I had started from clean states a few times, but not since I upgraded to the RC for 22.03 (was using snapshot before as this router is not supported in 21.02), so I was planning to do that anyway. BTW, DHCP offers have never worked in this router since I installed OpenWRT in it (official firmware works fine, but is not OpenWRT!)
Hopefully we can figure out why. Oddly, there are some situations where firmware can effectively swallow DHCP packets for no apparent reason. Unifi APs had been plagued with this issue for 1-2 years (may still be dealing with it, actually), and normal thinking about what constitutes a bridge couldn't explain the problem. So it could be a bug with OpenWrt, or (hopefully) just a configuration quirk.
Anyway, ping back when you can reset the device, and post the default network and wireless files.