Hello,
So i have a advanced setup which may complicate the issue though i think it has to be a bug.
Let me make a quick diagram:
Flint 2 ( isp modem, openwrt snapshot) <-> Switch <-> Flint 2 (as dumbap, with oem firmware 4.5.7)
On the isp modem i see this:
2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan.90) 94:83:c4:a6:ef:80
Thu Feb 15 11:03:52 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan.90) 10.87.2.2 94:83:c4:a6:ef:80
Thu Feb 15 11:03:56 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan.90) 94:83:c4:a6:ef:80
Thu Feb 15 11:03:56 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan.90) 10.87.2.2 94:83:c4:a6:ef:80
Thu Feb 15 11:03:57 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-zigbee) 00:0e:c6:87:72:01
Thu Feb 15 11:03:57 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-zigbee) 10.33.77.32 00:0e:c6:87:72:01
Thu Feb 15 11:03:59 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan.90) 94:83:c4:a6:ef:80
Thu Feb 15 11:03:59 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan.90) 10.87.2.2 94:83:c4:a6:ef:80
Thu Feb 15 11:04:00 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-zigbee) 00:0e:c6:87:72:01
Thu Feb 15 11:04:00 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-zigbee) 10.33.77.32 00:0e:c6:87:72:01
Thu Feb 15 11:04:02 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan.90) 94:83:c4:a6:ef:80
Thu Feb 15 11:04:02 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan.90) 10.87.2.2 94:83:c4:a6:ef:80
Thu Feb 15 11:04:03 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-zigbee) 00:0e:c6:87:72:01
Thu Feb 15 11:04:03 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-zigbee) 10.33.77.32 00:0e:c6:87:72:01
Thu Feb 15 11:04:05 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan.90) 94:83:c4:a6:ef:80
Thu Feb 15 11:04:05 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan.90) 10.87.2.2 94:83:c4:a6:ef:80
Thu Feb 15 11:04:08 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan.90) 94:83:c4:a6:ef:80
Thu Feb 15 11:04:08 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan.90) 10.87.2.2 94:83:c4:a6:ef:80
Thu Feb 15 11:04:11 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan.90) 94:83:c4:a6:ef:80
Thu Feb 15 11:04:11 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan.90) 10.87.2.2 94:83:c4:a6:ef:80
Thu Feb 15 11:04:14 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan.90) 94:83:c4:a6:ef:80
Thu Feb 15 11:04:14 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan.90) 10.87.2.2 94:83:c4:a6:ef:80
This means that the dhcp server on the dumbap keeps requesting dhcp, if i restart the issue is fixed, but this strange phenomenon randomly happens and then it keeps forgetting any dhcp and becomes inaccessible, wireless and internet still works however.
Ive been told that the setup of mixing other dsa vlans from other bridges into other bridges could break as OpenWrt may has it not intended that way, that only counts for br-zigbee where i added br-lan.50 on the isp modem only, but not for the ayaneo one which is br-lan.90
I suspect it has to be a issue in the software because no other router or device acts this way, i also have a Mango which also does not spam dhcp.
luckily on wired I was able to get some logdata which makes it extra strange, it says there is no dhcp range available but when I check in luci it just has a dhcp lease…
logread2.tar (205.5 KB)
and lets make a stripped backup so other people can check too if they want 
backup-GL-MT6000-2024-02-15.tar (14.4 KB)
just rename extension to .tar.gz the upload field blocked .gz files
edit
I can confirm if I disable dnsmasq its also fixed for me with the chattyness, although I think its still strange behaviour maybe should be considered as a bug report, but if I go to the web admin panel from wireless its super slow maybe a mtu issue here.