There is also the outer box to consider. This is the labels from mine.
Give me some time (an hour or so). At the moment I have ddwrt installed on the two I opened as I have been doing some testing for Brainslayer.
I will unbox the others soon and get back to you.
These labels are not really useful. I posted my screenshot which is the same as the OTHER Linksys routers that I have and NOT sure why you keep insisting that it is a HomeWRK webif. Even @lytr and the other user, @Tour, posted a screenshot which is TOTALLY different from mine. I am fairly confident that mine is the stock MX4300 and NOT the HomeWRK one, like you claim it is, fwiw!
This is the HomeWRK webif posted by @Tour:
This is the Linksys stock webif (mine):
Anyone else care to shed some light on this as it's confusing as hell? smh
1 Like
Correct. I have the identical box and mine is NOT the HomeWRK version.
1 Like
As long as you have serial access to it, it shouldn't matter which .bin you flash. You can always easily recover from uboot. But if you do not have serial access, unless openwrt flashes over both partitions (which is should not), you can always get back to OEM by toggling the power switch 3 times (with ~5 second delay between them).
Something else to consider, if indeed there are different versions of this router, then why does Linksys only have ONE firmware download available for them?
Sorry @cdes. This was not meant to be a reply to you.
All my 3 units' outer box have the wording of "HOMEWRK". But they have the same blue Linksys Smart Wi-Fi (non-HomeWRK) home page. I confirm they are MX4300 as they ran fine on Qosmio build. As a matter of fact, I made a mistake flashing the wrong build on my 1st one and bricked it. I had to cycle power multiple times to boot to the working partition and flashed again to fix the broken partition.
1 Like
@RainGater
I'm sure your Linksys stock webif snapshot indicates this is a non-Homewrk version and you should use the lytr's image with the "mx4300" string in it.
1 Like
Wow! You changed your tune when others attest what I posted is true. lol
My other Linksys devices (MR9000, MR8300) have the same interface as the LN1301 and that's why I was fairly confident that it is the stock MX4300 web interface. In any case, now it's clear. Peace out!
1 Like
Until somebody can come up with actual specs that prove there are two different hardware versions of this router, I am sticking to my belief there is only one version of it. While I am certain there are these things out there with original Linksys/Fortinet FW that were sold back in 2021/22, all those sold by Woot and Amazon are going to be identical H/W with a redo of Linksys FW replacing the original.
The ONLY reason they have 1GB FLASH and 2GB of RAM is to accompany the bloated Fortinet firmware they were originally sold with.
If there were two different H/W versions, then Linksys themselves would have firmware available for each one. They do not.
the hardware could be identical for mx4300 and mx4300-homewrk, but (based on posts up higher in this unwieldy thread) the bootlog, u-boot environments, and mtd maps are different. this could have been accomplished by changing uboot defaults. so identical hardware may not mean ithat the firmwares are interchangeable without some more advanced tweaking.
i tried flashing a homewrk version to my mx4300 and it soft-bricked, requiring power cycling to get back to the alternative partition.
i'm wondering if anyone with the homewrk version could upload their u-boot partition?
i'll upload my mx4300 uboot when i get access to my device later.
thx
2 Likes
Is the MX4200 the same as the E4200?
I can see that the E4200 firmware is available via the firmware selector tool.
Is there a stable MX4200 firmware available?
This makes the most sense of anything else I've seen so far. I've only one connected via serial ATM but I will check and compare the uboot versions on the other three at some point in the next few days.
I built your git and have these two errors. Safe to ignore because I used -a to include all the packages from all feeds?
fed@Chronos:~/ow/mx4300$ ./scripts/feeds install -a
Collecting target info: done
WARNING: Makefile 'package/feeds/telephony/freeswitch/Makefile' has a dependency on 'libpcre', which does not exist
WARNING: Makefile 'package/feeds/luci/luci-app-polipo/Makefile' has a dependency on 'polipo', which does not exist
Installing all packages from feed packages.
Installing all packages from feed luci.
Installing all packages from feed routing.
Installing all packages from feed telephony.
Installing all packages from feed nss_packages.
Installing all packages from feed sqm_scripts_nss.
You can ignore them. Also, do not try to rebase as the newer kernel version may break its NSS and ath11k patches.
You can also use the NSS image I had posted in this thread. One problem with the qosmio's NSS branch for MX4300 is that it seems to have problem with VLAN. If you may encounter such VLAN problem, you have to build from the OpenWrt master branch (with lytr's changes of course).
If you read lytr's earlier posts when he was trying to create a build for HomeWrk, you would understand their difference.
1 Like
Do you have a link to the bin?
I see this is what you posted but it's saying that available downloads: 0. Also, the website is asking me to login?
I built qosmio's version and ran my setup script as I have multiple vlans and all of them were properly assigning the vlan specific ip's just fine but they were not able to provide internet. May be there was a config issue so I will try again but for now I took lytr's build adding Adguard/Wire guard/Avahi and built and deployed and its working fine.
I have a Omada EAP773 so that takes care of most of the wifi duties.. For me its the routing part that matters more. Upon checking all my 50+ devices mostly connect to Omada instead of ln1301 except if I am in basement where the ln1301 is located.
I don't know why I bought 2 of ln1301 also now I have a spare Onhub
How long does it take to compile @qosmio build? I have a powerful machine but it's running for a while.
❯ git clone https://github.com/qosmio/openwrt-ipq mx4300 -b qualcommax-6.x-nss-mx4300
❯ cd mx4300
❯ ./scripts/feeds update
❯ ./scripts/feeds install -a
❯ cp nss-setup/config-nss.seed .config
❯ make defconfig V=s -j4
❯ make
It's been compiling for more than 30 minutes now. Is this normal?
I got @qosmio build to compile and generated the images. I used his .config file to seed it. Where do I add the config files from his example?
- nss-setup/example/02-mesh-sat-node
- nss-setup/example/03-uci-defaultsfile
I am planning to setup wireless mesh and need one binary for the main parent and the other one for wireless node. So, where do these example configs go during the build process?
For wireless mesh, this file (nss-setup/example/01-mesh-node) is NOT needed. Correct?
thanks. is it support NSS?