Did you use the web method and download that file from the users google drive to flash or the tftp method?
trx from google then sysupgrade with bin.
1 Like
You ARE on a stable router, my Flint2 is running w/o issues since 12/2023.
Starting with snapshot, now on 23.05.5, no problem ever.
You might try the vendor FW to rule out a SW issue.
1 Like
Yeah I thought I was on one. I figured I had done something horribly wrong. My next step was reset mt6000 and / or revert to oem. I did buy the tuf-4200 as well because I want this solved soon. All I want is a secure home lab environment.
I really wanted to avoid having to learn the stock oem ui too on the gl.
The Vendor GUI offers an "advanced interface" similar to the the one of OpenWRT.
(If I remember correctly, only had the vendor FW in use to verify the HW is OK)
Could you accept a possibility of deviant (not necessarily bad) batch?
For sure, shit happens ...
Like the hardware itself? Like requesting a RMA? I gotta go back to stock oem to even be able to compete with RMA.
1 Like
Like I proposed before.
Check if the issue persists with the Vendor FW, if so, request an RMA.
2 Likes
RMA may yield you "new improved power supply" and "complementary stickers pack".
1 Like
So I have 34 days uptime on the mt6000! Whoo hoo. All I did was reset the router back to the bare sysupgrade-ed version of OpenWrt. I didn't go all the way back to OEM. Kind of weird. I guess in all my configuration and botching the configuration I messed something up.
EDIT 1:
In the past, I did try to mix tagged and untagged on the same port. So I would have one untagged and then a few tagged. For some reason, this seemed to break IPv6 and I could no longer get an IPv6 address. Maybe it was something weird with the firewall or ICMP.
It is hardware or driver limitation or a bug, in normal ethernet you can use 4095 vlans on top of normal lan. You are correct that you measured whether it works.
eg
This happened to me once. I had a VLAN also set on my WAN port and my device crashed.
MT-6000. ( I use IPv6 also )
Removed the VLAN - been stable ever since.
@systemcrash @mattcargile interesting, could you try ethtool -k/-K and try to disable vlan offloads to change code paths around supposed clans causing crashes?
I just removed the VLAN config. Did not actually need it. I may experiment with WAN VLAN at a later stage.