And you have no other interfaces like a vpn which may can cause this behaviour on the mac due to a killswitch?
I have flashed alot of routers also non gl ones and even the more complicated ones like the ax6s.
Sometimes a reboot isn't supported after a upgrade and often the led stays on, to avoid another brick make sure the led is no longer processing and wait atleast 5 min.
Then try to replug the device and see if it boots normal on its led indicator.
I waited a long time after the flashing allegedly was successful as per the message shown in the web UI. Then it shows a loading spinner and tells me that the device is now rebooting.
The power LED remains blue and the device is inaccessible via 192.168.8.1.
I had the same issue, i.e no access to 192.168.8.1, even after (successfully) uploading new firmware. I reached out to Gl-inet support who sent me this message:
Our engineers have released a special firmware for fixing the issue on your MT2500 router, do you mind giving it one last try?
If it suddenly stopped working after you were "messing around", did you by any chance happen to include descriptions when setting up static IPs?
If so, you might have run into the same bug that I just did - it's possible to enter characters that screw up the dnsmasq config and prevent it from loading (which will prevent clients from getting DHCP leases).
Double quotes are one example, so it'll happen if you put something like:
65" TV
The part that makes it tricky is that unless you check logs after making changes, there's no clear indication you've broken things until your leases run out and devices that weren't manually configured start dropping off the network.
Manual config for gateway / netmask / dns seemed to be enough to connect to fix things without needing to reset config.
openwrt-mt2500-4.6.10-1118-1731927038.bin
This is a temporary alpha (near beta) firmware, not sure if there are other bugs.
This firmware only test through email channels, small-scale testing, to verify whether what result is, collect validation data, don't want to test on a large scale.
If there is no problem with the test data, we will release the beta firmware version for public.
In order not to expand the impact, we have to temporarily hide the post, truly sorry.