Frequent disconnect on my Deco M5
We have 2 Deco M5 on AP mode. Both are connected directly via ethernet cable to our ISP's (Globe Telecom) modem router. Smart DHCP, Beamfoaming and Fast Roaming are disabled. Wifi is only on 5 Ghz. I've set our ISP's modem router to be on Google DNS (8.8.8.8, 8.8.4.4). And we only have mostly less than 10 devices connected to it. I've reserved the IP address for the decos to be on 192.168.254.100 and 192.168.254.101 on the ISP's modem router also set IPv4 Firewall Level to Low.
ISP's modem router is a Huwawei HG8145V5
My decos frequently turns red for a few secs. I noticed that it occurs whenever my brother plays FF14 and he says he's connecting to FF14 servers by using a VPN. Although when it turns red he doesn't get disconnected but devices connected to it will momentarily lose internet connection and it takes around 1-2 mins to get internet back. On the ISP's modem router portal shows that we're still connected to the internet though.
Here are the error logs on the Deco M5:
Wed Jan 12 20:03:46 2022 daemon.err udhcpc[5910]: udhcpc (v1.22.1) started
Wed Jan 12 20:03:46 2022 daemon.err udhcpc[5910]: Sending discover...
Wed Jan 12 20:03:46 2022 daemon.err conn-indicator: [send_query] Failed to send DNS query: Network is unreachable
Wed Jan 12 20:03:48 2022 daemon.err udhcpc[5910]: Sending select for 192.168.254.101...
Wed Jan 12 20:03:49 2022 user.emerg syslog: tp217,505[5962]:
Wed Jan 12 20:11:33 2022 user.err smartip: [lan] !!ip addr del!! ip addr del 192.168.254.101 dev br-lan
Wed Jan 12 20:11:33 2022 daemon.err udhcpc[5921]: Received SIGTERM
Wed Jan 12 20:11:34 2022 daemon.err udhcpc[9379]: udhcpc (v1.22.1) started
I tried resetting and rebooting the decos also rebooting the modem router. But it still keeps occuring. I'm thinking to have my brother's PC where he plays FF14 to have it directly connected to our ISP's modem router and see if it still occurs.
UPDATE: Tested a few scenarios with FF14 and the VPN (mudfish) used. Connected another laptop directly to ISP's modem router and issue still persisted so it might be on the ISP side