I recently purchased a Brume 2 for Tailscale site to site setup. When upgrading from the factory v21 to the OpenWrt v24 (as v21 is not listed in the OpenWrt instructions and to just be up to date), the interfaces seem to carry over properly but the 2.5GbE port no longer shows a physical connection. I can view luci and ssh through the Lan port just fine (the only other ethernet port on the device). Reverting back to factory using Uboot restores the connection.
This is my first delve into OpenWrt, so I'm not sure how to troubleshoot the problem. The "wan" interface is lowercase and luci reports that a mac address is assigned (same as in the v21) but no data is passing and the icon is greyed out. Is this a common issue and/or is there a package to be installed? Help is appreciated.
Did you do a factory reset during/after upgrade to 24.10? Upgrading across multiple major versions is not supported as the config might not be compatible anymore.
To start, I accessed luci from the factory firmare and uploaded the sysupgrade from OpenWrt's firmware selector. After seeing the wan port no longer worked, I used Uboot to revert to factory and saw the port was working again.
OK, but did you do a config reset during or after the sysupgrade? If not, you should try that.
I'll give it a go. Just to make sure i would be doing as requested, is this just holding the reset button to initiate or would this be an SSH command? Though It'll be a later this evening till I get back home to try it.
Look here - good info
I have reinstalled 24.10.0 and tried bot the "perform reset" button in Flash operations tab and firstboot in ssh. Neither seemed to correct the behavior. I have also become more aware to the fact that I can't update the packages due to the misbehaving wan port.
I saw that thread. I thought that the stable release would work since someone mentioned rc5 had functioned. Was a lil bummed that the thread ended in a recommend of a different product since this is what i have on hand now. I'll give RC5 a go and see what happens.
With MT-2500 and a few other targets...
Might consider reverting back to GL_Inet stock firmware so they can update the mediatek u-boot they build with...
Once done, one can make the jump back via u-boot recovery on MT2500...
That looks promising, but for some reason the UBoot update starts and then fails. It didn't brick anything, but refuses to continue.
Yeah - but at the same time - something was/is going on with the upsteam uboot code...
Part of me wonders if this is also related to the OKD issues with Belkin RT3200 where devices just die after a period of time - and there, after a lot of work by both openwrt team members and Mediatek directly, it was an ARM trust-zone issue...
with GL-Inet gear these days, best to do from u-boot recovery - this clears all the configs and get one to a fresh place...
side note for folks searching - look at the model - the QC AX1800/AXT1800 devices do a different switch over...