what is the reason for such a difference between the OEM reserved RAM amount vs openwrt's reserved RAM amount? Is it possible to lower the reserved amount in somehow? I saw it is different from the mx4300 as well (182 MiB reserved)
Could you confirm the first 4 digits of that v2 serial number? I'm pretty sure now that is the only way to know (from a sealed box ofc). The 4th digit should be a 2 and the v1 should all be 1.
Been digging through documentations to see if this is documented anywhere but do we have a way currently to expand the limited storage available on MX4300? (From the original PR adding support, there's app2 and app2_data with ~500 MB of unused space)
Wow, 2 speed tests, separated by a minute, yields the best results on MX4300 so far and am on r29268. Impressive, to say the least, and thank you @arix for keeping up with the builds.
Yes, NSS is enabled. No, I don't want to bother with this setup as the tests that I posted above are from a desktop that is wired to a WIRELESS NODE and is positioned about 40 feet away from the main router. I maxed out the link speed and can't do any better than this, imho!
Super duper happy, to say the least, as I never expected a wireless MESH will achieve the full throughput as if I am hard wired to the main router. Thanks to Linksys for the $15 fire sale (only snagged 5... lol) and OpenWRT community to make it much better than the stock firmware!
This morning I upgraded my Linksys HomeWRK to the OpenWrt SNAPSHOT r29425-241343a2f2. Unfortunately when try to add zabbix-agentd it gives the below error, do I just need to wait for a snapshot that has the correct dependencies? Previous snapshots worked. Thanks in advance!
root@OpenWrt:~# apk update && apk add zabbix-agentd
[https://downloads.openwrt.org/snapshots/targets/qualcommax/ipq807x/packages]
[https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/base]
[https://downloads.openwrt.org/snapshots/targets/qualcommax/ipq807x/kmods/6.6.87-1-02c1fc412ac05a28c288f2700b588065]
[https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/luci]
[https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/packages]
[https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/routing]
[https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/telephony]
[https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/video]
OK: 10566 distinct packages available
ERROR: unable to select packages:
zabbix-agentd (no such package):
required by: world[zabbix-agentd]
I just installed the latest @arix build and it no longer has the NSS SQM script. I'm pretty sure my first install had it in there after installing the SQM scripts and luci SQM.
edit update: built from qosimo repo (@ 4eed9d25272d) directly and it has NSS SQM included by default.
@RainGater@arix I am running Qosmio's NSS from November last year - had used uci_defaults to configure APs and done the build using codespace.
With the arix build r28897 that you referred, would you use the binaries directly or do your own build? I couldn't find a way to build - as codespace is disabled.
If the suggestion is to use the binaries directly, How do I execute uci_defaults to set up my APs...
Will appreciate your guidance...
It was there in an old build 2 weeks ago, no idea why it's missing now. I can see it set to m instead y even I explicitly set to y, thus missing in the binary. Maybe some modules trigger it to m...need some debugging.
Is there a reason your not just using Qosimo's seed config. It seems to have everything i need in it (luci-sqm nss SQM scripts etc by default) I just setup a build to build off his repo when i sync my fork..
However if you sysupgrade to say 24.10.2 in some months then it won't boot properly due to dual partition. First, you want to do the winscp method to install the squashfs factory image to the other partition to essentially have this:
Partition 1 (P1): OpenWRT 24.10.1 with your configured settings
Partition 2 (P2): OpenWRT 24.10.1 default
Then when that boots to P2 you actually then sysupgrade which will then flash the first partition you were on.
Partition 1 (P1): OpenWRT 24.10.2 with your configured settings (if decided to keep)
Partition 2 (P2): OpenWRT 24.10.1 default
Then if you wanted to keep P2 updated you would sysupgrade from P1 to leave you with:
Partition 1 (P1): OpenWRT 24.10.2 with your configured settings (if decided to keep)
Partition 2 (P2): OpenWRT 24.10.2 default
Alternatively if you keep stock firmware (probably a good idea on partition 1 or 2) you would flash OpenWRT as normal, install luci-app-advanced-reboot and then when you wanted to sysupgrade your OpenWRT partition, have that app boot you into other partition then flash sysupgrade via Linksys stock firmware?
I think, all or most of your post is correct but there are a couple more options:
You can upgrade into the same partition (P1 in your examples). I have not used it so I don't remember all the details. In particular I am not sure if the upgrade into the same partition is possible from the luci interface or with either ASU or owut but it is clearly possible from the command line. The command with appropriate options is somewhere in the thread.
Once you flash openwrt onto P2, you can mark "keep settings" when upgrading and it will install the new version into P2 as well as copy the settings from P1 to P2.
