If you can't reproduce, doesn't mean the problem doesn't exist.
Please let me know what else I can do to you reproduce this problem.
The flash drive was formatted as EXT3 using Rufus
Updated to this 4.7.5-op24 released today and this problem is still there (USB is not mounted after the reboot).
This is not how the firmware developments works.
You should:
a) Pick a STABLE OpenWRT as reference (and not Beta, or Release Candidates);
b) Add your features;
c) Release it as Beta for the community;
d) Fix the reported issues and DON'T change anything else;
e) Use a reasonable version numbering. When you make available the version 4.7.5, I'm supposing it has only bug fixes compared to 4.7.0. No new feature should be present. No different Kernel should be present. No different OpenWRT version should be present.
So far the firmware is working very well, wifi works great, even with 4.7.0 it worked fine, but with this version I noticed less ram usage, which is a good thing.
I completely agree with your points about releases.
as a developer myself in other communities visibility is very important to be transparant about things.
If a release would break that would be incredible rare, such things would happen on a beta, and on a pre release also rare but less rare than release.
What i disslike is that a firmware with bugs get released 4.7.5 it said, then they compile a different one with the exact versioning, now there are two versions 4.7.5 co-existing which is really not done, people should have the right to know what happened and the newer release should be stated 4.7.5.1 or 4.7.5B2 sure we can use hashes and dates to confirm but that is not the software safeguarding what I would recall.
About the openwrt fork this is also true if you go build for a stable release, it is the most logical approach to checkout a full release of OpenWrt than a older revision from master which doesn't count as full release, at current there is also a newer release of OpenWrt 24.10.1.
Besides they claim op24 gets mainlined if it performs better, then they also need to keep in sync with the releases.
^ also because of the kernel mismatches with kernels and user packages, its more logical to do so, so can gl also make use of the openwrt repo for packages thats the beauty of using a release.
Upgrading from 4.7.0-op24 to 4.7.5-op24 I noticed a lower ram usage, maybe in your case it can help, staying with an obsolete version like 4.6.6 doesn't make sense in my opinion.
I have never had crashes or other problems even with 4.7.0-op24, simply now with 4.7.5-op24 it uses less ram with the same settings and conditions, I use adguard but I don't have all the lists you have active, I only have 6, exactly like before, but before the ram use reached about 370 MB, now it doesn't exceed about 280 MB.
I should just see if it remains stable over time and doesn't increase much, but so far everything is ok.
Okay i flash new recommend openwrt-mt6000-4.7.5-op24 Looks not crash after update all bug ADGuard lists but i still face with same issue at web user interface of OpenWrt. LuCI - Legacy rules detected
There are legacy iptables rules present on the system. Mixing iptables and nftables rules is discouraged and may lead to incomplete traffic filtering.
Hook: prerouting (Capture incoming packets before any routing decision), Priority: -151
Policy: accept (Continue processing unmatched packets) any way the time will showing how the router work. Generaly i was hope new model to have 2gb ram so that to handling heavy users and ADguard big block lists.
I had the same bug on Brume 2 after updating to 4.7.0 and had reported it also here:
No USB drive recognized anymore after upgrade to 4.7.0.
Rebooting didnt fix it, regardless how many times.
Unplug usb port, replug it fixed it.
Cant really explain this to me how this worked but a reboot didnt.
