Rookie mistake, I just had to re-enter the country code to US and it is happy. Default country code was set to 00.
Wifi speeds are excellent at over 800 Mbp/s with an 80 MHz channel. As far as I can tell, everything seems to work.
I was researching the mystery of what these LN1301/MX4300 devices are and here's what I've got.
These are old stock "Linksys HomeWRK for Business | Secured by Fortinet" routers. Sometimes known as model MX4301 or MX4300, launched back in 2021.
On mine, you can see evidence of the rebrand. The "Fortinet" logo on the plastic base has been scrubbed off and you can see some of the scuffing on the plastic. Labels were removed, replaced, or layered over, which explains a bit of extra glue and some units having labels which are not entirely fixed properly.
If you look at the Linksys website firmware download for this device, the first release version is from February, just a few months ago. I am willing to wager that will also be the last ever official release. This is a dead product being dumped via fire sale.
Here is a PDF product data sheet:
At $600-$800 each, they were outrageously expensive, even for business devices. No wonder they didn't sell well.
It looks like Linksys and Fortinet went big into this product line with a ton of PR and marketing material out there, but their pricing sucked, and then "return-to-office" ruined their plans, so I suspect they just didn't sell and now they were stuck with a ton of unsold and unsalable inventory.
I am willing to bet this is what is on those last two partitions. I've dumped mine but I have not had time to review them yet.
Here's a bunch of PR and other product info:
8 Likes
https://downloads.linksys.com/support/assets/releasenotes/MX4300V1_3.10.2_Customer_Release_Note.txt
There is MX4301 firmware release note for fortinet branded MX4300.
But failed to find the firmware file on internet.
anyway, it is beyond the scope of this thread
Thanks! I just wanted to add that I'm noticing that the lan numbers are wrong in luci. For example lan1 (top by USB) shows as lan3.
I found mtd resetbc s_env does not work. It returns Trace/breakpoint trap.
I think the root cause is this
Current implementation only allocated 2048 bytes for the array, but at
It writes bc_offset_increment (should be 4096 on mx4300 if my understanding is correct) number of bytes to the nand causing accessing array out of bounds.
Here is a hex dump of s_env
*
00038000 11 08 11 20 01 00 00 00 12 08 11 20 ff ff ff ff |... ....... ....|
00038010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
00039000 11 08 11 20 02 00 00 00 13 08 11 20 ff ff ff ff |... ....... ....|
00039010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
0003a000 11 08 11 20 00 00 00 00 11 08 11 20 ff ff ff ff |... ....... ....|
0003a010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
0003b000 11 08 11 20 01 00 00 00 12 08 11 20 ff ff ff ff |... ....... ....|
0003b010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
00100000
Here is the fixed mtd that can correctly reset the boot counter.
it can be installed with
opkg install --force-reinstall mtd_26_aarch64_cortex-a53.ipk
After the re-installation is done, please reboot the device and check the boot count log in s_env with
hexdump -C /dev/mtd19ro
You should see something like this at the end of output
0003e000 11 08 11 20 00 00 00 00 11 08 11 20 ff ff ff ff |... ....... ....|
0003e010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
00100000
1 Like
Here is a new build where MAC addresses should be set the same as in the OEM firmware: https://github.com/testuser7/openwrt/releases/tag/qualcommax-00f5047
This has been corrected. For MX4200/5300/8500 the LAN ports are not numbered.
Will you prepare a PR for the main branch?
I've always had that problem with Teams in the main branch and its snapshots. It eventually led me to backport support for MX4200 to 23.05.
I still got a few 'failed to flush' errors but rarely issues with Teams which I could attribute to the router using OpenWrt. In the end, I've reverted back to stock firmware because there are clearly more random issues cropping up when using OpenWrt.
Please post back if you find the culprit of the issue with Teams. I would like to know just out of curiosity.
@ asd111333
"Here is the squashfs-factory.bin with hard-coded boot command booting from mtd22"
i downloaded this file and sucessfully flashed my 'mx4300' variant.
applying a sysupgrade from that initial flash resulted in a soft-brick that required the power cycle to get back to your hard-coded version flash.
could/should i/we change the uboot env boot command to allow subsequent builds to flash?
here is my fw_printenv:
root@OpenWrt:~# fw_printenv
altkern=c180000
auto_recovery=yes
baudrate=115200
boot_part=1
bootargs=console=ttyMSM0,115200n8
bootcmd=if test $auto_recovery = no; then bootipq; elif test $boot_part = 1; then run bootpart1; else run bootpart
2; fi
bootdelay=2
bootpart1=set bootargs $partbootargs && nand read $loadaddr $prikern $kernsize && bootm $loadaddr
bootpart2=set bootargs $partbootargs2 && nand read $loadaddr $altkern $kernsize && bootm $loadaddr
eth1addr=80:69:1a:22:ad:e1
eth2addr=80:69:1a:22:ad:e2
ethaddr=80:69:1a:22:ad:e1
fdt_high=0x4A400000
fdtcontroladdr=4a97db30
flash_type=2
flashimg=tftpboot $loadaddr $image && nand erase $prikern $imgsize && nand write $loadaddr $prikern $filesize
flashimg2=tftpboot $loadaddr $image && nand erase $altkern $imgsize && nand write $loadaddr $altkern $filesize
image=tortuga.img
imgsize=af40000
ipaddr=192.168.1.1
kernsize=800000
loadaddr=44000000
machid=801000d
maxpartialboots=3
mtdids=nand0=nand0
netmask=255.255.255.0
partbootargs=init=/sbin/init rootfstype=squashfs ubi.mtd=22,2048 ubi.block=0,0 root=/dev/ubiblock0_0 rootwait ro
partbootargs2=init=/sbin/init rootfstype=squashfs ubi.mtd=24,2048 ubi.block=0,0 root=/dev/ubiblock0_0 rootwait ro
prikern=1240000
serverip=192.168.1.100
soc_hw_version=200d0200
soc_version_major=2
soc_version_minor=0
stderr=serial@78B3000
stdin=serial@78B3000
stdout=serial@78B3000
root@OpenWrt:~#
Build with applied patch to be able to boot without changing boot args: https://github.com/testuser7/openwrt/releases/tag/qualcommax-7e151ef
I don't know if it will work.
1 Like
I don't think it will work on qualcommax, since it is arm64 not arm.
I think this is where we should apply the patch.
The current sysupgrade does the A-B flashing like the stock firmware. The hard-coded version can only be installed to the kernel partition not alt_kernel, so it won't work when you do a sysupgrade.
Update: I've flashed squashfactory from https://github.com/asd333111/openwrt/releases/tag/qualcommax-492d0c6 and it works. Rookie mistake, use ssh and not telnet.
Rookie mistake:
I've flashed squashfactory from https://github.com/asd333111/openwrt/releases/tag/qualcommax-492d0c6, and can't login. I see blue light going differently at boot (vs. when stock fw boots), and can get IP and ping 192.168.1.1, but can't login to 192.168.1.1, neither with browser nor telnet.
Did powercycle 3x, went back to stock, flashed again - same result. Back to stock after 3 powercycles.
There could be something simple I'm missing - this is the first time I'm flashing openwrt. Anything else I should try? initramfs? I don't have serial access.
P.S. Just in case - this is MX4301 I bought from walmart, not amazon/woot.
Thanks!
Thanks for making me look! Looks like the LN1301 is back in stock at walmart for $20. Progress is looking good here, so I went ahead and ordered 2 more... Now I just need to work on explaining why we suddenly have routers in every room.
https://www.walmart.com/ip/Linksys-LN1301-Triband-AX4200-WiFi-6-Router/5645414143
1 Like
Try with ssh, the web page won't load since luci isn't installed by default.
https://openwrt.org/docs/guide-user/luci/luci.essentials
1 Like
Everybody else has mesh settings in stock FW? - I thought this was sold/advertised as standalone? I don't want to keep stock, just wonder if all models sold are the same.
The Fortinet stuff probably explains the extra RAM and flash over the MX4200 too. Running that probably needed more RAM and Flash. Now they hastily made a new FW version without the Fortinet stuff.
I've seen other similar devices that are a VPN gateway to a corporate network built-in to a router.
I ordered from Amazon and the stock fw (1.0.4.215382 LN13 Series) has mesh settings but they are buried. You have to click the "CA" link hidden down by the privacy policy links, and then under Connectivity, a new tab for "CA Router Setup" will appear (as well as some more granular but still super-basic wifi settings like channel selection).
I looked at the carton the device arrived in and it is indeed still marked as the MX4301 HomeWRK for Business router.
Yes, thanks!