The problem is apk is not installed. How do I install this without apk?
duh, of course ! catch 22.
manually unpack the apk, whatever format it's in ...
I guess the firmware selector is NOT available for primetime yet... have to wait for the "Unsupported profile: linksys_mx4300" error to be fixed when requesting a build. This concludes this test for today and stick with my GitHub builds for now. lol
1 Like
Support for Linksys HomeWRK is ready: https://github.com/openwrt/openwrt/pull/17463
Installation via serial only.
By the way, the code names of the devices:
- MX4200v1 - chiron
- MX4200v2 - jade
- MX4300 - tortuga
- MX5300 - bronx
- MX8500 - diablo
And these probably don't exist:
- MX4300v2 - pearl
- MX4300Sv2 - ruby
4 Likes
Apologies for not following all updates to the firmware. I wanted to check if recent builds have the fix for second 5ghz band working only with lower channel numbers ?
1 Like
I was able to build a customized image for MX4300 using the official image builder!
But, how does this differ from the community builds put together by @lytr @arix @qosmio and will those community members still be putting out specialized builds that are different from the now-official one?
Many thanks for everyone's individual efforts on this device.
1 Like
I assume the official snapshot doesn’t have support for Qualcomm NSS stuff. Ie no proprietary hardware offloads? Just uses the CPU? Correct?
1 Like
Honestly I never noticed a big difference between the NSS builds and the OSS builds, but I may not have used certain features. I have a 1Gbps down/35Mbps up connection and can reach near the highest speed over ethernet, and anywhere from 500-700+ down over WiFi depending on proximity to the router. I don't do any meshing and use no other networking equipment besides a cable modem.
There is no difference in FOSS builds, NSS builds in the other hand will not be official because of the proprietary patches and binaries.
1 Like
Damn! The Master build is giving incredible speeds even on wifi (laptop was about 20 feet away from the router). Impressive!
Build: OpenWrt SNAPSHOT r28476-2456a2fd7f / LuCI Master 25.001.48925~f5c1806 -> from the firmware selector
Have to test the mesh connection tomorrow morning from my desktop and if it performs as well as on wifi, then I don't have to spin any more GitHub builds 
With 24.10 (software offloading enabled) and about 20ft away, 650Mbps for R7800 (non-CT ath10k) and 800Mbps for MX4300. Tested using a Macbook Pro.
1 Like
I am not sure this is helpful for anyone else, but I figured I would post it, since it helped me.
I took the latest FOSS build from here:
And downloaded the .manifest, which lists all the packages that went into the build.
I then yanked out all the "version" info from that, leaving just the package names that went into the build.
This leaves a list you can "paste" into the " Customize installed packages and/or first boot script" section that will generate a custom image for you, with all the packages that were in the FOSS builds we were all using before the merge happened.
This list of packages is as follows:
apk-mbedtls ath11k-firmware-ipq8074 base-files busybox ca-bundle cgi-io dnsmasq dropbear e2fsprogs firewall4 fstools fwtool getrandom hostapd-common ipq-wifi-linksys_mx4200 iw iwinfo jansson4 jshn jsonfilter kernel kmod-ath kmod-ath11k kmod-ath11k-ahb kmod-cfg80211 kmod-crypto-acompress kmod-crypto-aead kmod-crypto-ccm kmod-crypto-cmac kmod-crypto-crc32c kmod-crypto-ctr kmod-crypto-gcm kmod-crypto-geniv kmod-crypto-gf128 kmod-crypto-ghash kmod-crypto-hash kmod-crypto-hmac kmod-crypto-manager kmod-crypto-michael-mic kmod-crypto-null kmod-crypto-rng kmod-crypto-seqiv kmod-crypto-sha3 kmod-crypto-sha512 kmod-fs-ext4 kmod-gpio-button-hotplug kmod-hwmon-core kmod-i2c-core kmod-leds-gpio kmod-leds-pca963x kmod-lib-crc-ccitt kmod-lib-crc16 kmod-lib-crc32c kmod-lib-lzo kmod-libphy kmod-mac80211 kmod-nf-conntrack kmod-nf-conntrack6 kmod-nf-flow kmod-nf-log kmod-nf-log6 kmod-nf-nat kmod-nf-reject kmod-nf-reject6 kmod-nfnetlink kmod-nft-core kmod-nft-fib kmod-nft-nat kmod-nft-offload kmod-nls-base kmod-phy-aquantia kmod-ppp kmod-pppoe kmod-pppox kmod-qca-nss-dp kmod-qca-ssdk kmod-qcom-qmi-helpers kmod-qrtr kmod-qrtr-smd kmod-slhc kmod-thermal kmod-usb-core kmod-usb-dwc3 kmod-usb-dwc3-qcom kmod-usb-xhci-hcd kmod-usb3 libblkid1 libblobmsg-json libc libcomerr0 libe2p2 libext2fs2 libgcc1 libiwinfo-data libiwinfo libjson-c5 libjson-script liblucihttp-ucode liblucihttp0 libmbedtls21 libmnl0 libnftnl11 libnl-tiny1 libpthread librt libsmartcols1 libss2 libubox libubus libuci libuclient libucode libudebug libustream-mbedtls libuuid1 logd losetup luci luci-app-firewall luci-app-package-manager luci-base luci-light luci-mod-admin-full luci-mod-network luci-mod-status luci-mod-system luci-proto-ipv6 luci-proto-ppp luci-theme-bootstrap mtd netifd nftables-json odhcp6c odhcpd-ipv6only openwrt-keyring ppp ppp-mod-pppoe procd procd-seccomp procd-ujail rpcd rpcd-mod-file rpcd-mod-iwinfo rpcd-mod-luci rpcd-mod-rrdns rpcd-mod-ucode ubi-utils uboot-envtools ubox ubus ubusd uci uclient-fetch ucode ucode-mod-digest ucode-mod-fs ucode-mod-html ucode-mod-math ucode-mod-nl80211 ucode-mod-rtnl ucode-mod-ubus ucode-mod-uci ucode-mod-uloop uhttpd uhttpd-mod-ubus urandom-seed urngd usign wifi-scripts wireless-regdb wpad-basic-mbedtls zlib
Hopefully this is helpful for others, as it was for me.
2 Likes
What about the sysupgrade process? Has anything changed with merging the MX4300 devices upstream. Is it possible to do a normal sysupgrade and expect that it will not overwrite the stock firmware on alternative partition and boot to the OpenWrt.
Another way, you can just install owut and run from ssh "owut upgrade" and it should list packages, build and install... I tried just download command and the image generated was fine.
2 Likes
I have MX4200v1 devices with DDWRT installed, and I am interested in helping with OpenWRT to be supported.
How familiar are the hardware between MX4200v1, v2, and MX4300?
I'd also appreciate hardening guides for OpenWRT as well
This is interesting... going from @arix's NSS build to the new official SNAPSHOT resulted in a noticeable memory usage difference:
closeup on when exactly I did the update:
1 Like
Both the v1 and v2 version of the MX4200 are already supported in the upcoming 24.10 release (currently already available in 24.10.0-rc4).
What is it that you are hoping to do/help? You could certainly install 24.10.0-rc4 and provide feedback about the things that are and are not working properly.
- MX4200v1 - 512MB RAM, 512MB Flash + BT (Silicon Labs EFR32MG21)
- MX4200v2 - 1GB RAM, 512MB Flash + BT (Silicon Labs EFR32MG21)
- MX4300 - 2GB RAM, 1GB Flash
Apart from that, there are no major differences.
If you have a choice, it is better to choose a device with at least 1GB RAM.
OK. the current snapshot r28485-2b70b32aef(or the package feed) is totally broken. libubus updated to 20250102 and included in prebuilt snapshot, but package feed remains on older 20241020. So can't even install luci.
# apk add luci
ERROR: unable to select packages:
libubus20250102-2025.01.02~afa57cce-r1:
conflicts: libubus20241020-2024.10.20~252a9b0c-r1[libubus=2025.01.02~afa57cce-r1]
satisfies: world[libubus20250102] dnsmasq-2.90-r3[libubus20250102]
libiwinfo20230701-2024.10.20~b94f066e-r1[libubus20250102]
libudebug-2023.12.06~6d3f51f9[libubus20250102]
logd-2024.04.26~85f10530-r1[libubus20250102]
netifd-2024.12.17~ea01ed41-r1[libubus20250102]
odhcpd-ipv6only-2024.05.08~a2988231-r1[libubus20250102]
procd-2024.12.22~42d39376-r1[libubus20250102]
procd-ujail-2024.12.22~42d39376-r1[libubus20250102]
ubox-2024.04.26~85f10530-r1[libubus20250102]
ubus-2025.01.02~afa57cce-r1[libubus20250102]
ucode-mod-ubus-2024.12.06~209f041f-r1[libubus20250102]
wpad-basic-mbedtls-2024.09.15~5ace39b0-r2[libubus20250102]
libubus20241020-2024.10.20~252a9b0c-r1:
conflicts: libubus20250102-2025.01.02~afa57cce-r1[libubus=2024.10.20~252a9b0c-r1]
satisfies: cgi-io-2022.08.10~901b0f04-r21[libubus20241020]
rpcd-2024.12.02~cc9a471c-r1[libubus20241020]
rpcd-mod-file-2024.12.02~cc9a471c-r1[libubus20241020]
rpcd-mod-iwinfo-2024.12.02~cc9a471c-r1[libubus20241020]
rpcd-mod-luci-20240305-r1[libubus20241020]
rpcd-mod-rrdns-20170710[libubus20241020]
rpcd-mod-ucode-2024.12.02~cc9a471c-r1[libubus20241020]
uhttpd-mod-ubus-2023.06.25~34a8a74d-r4[libubus20241020]
1 Like