Tested OpenWRT 25.12.2 on Linksys MR8300 & x2 WHW03 V2(s) with great results!

For Developers
1

Hello developers and community,

I hope this message finds you well. I'm sharing current testing results to help update the Table of Hardware (ToH) pages for a few devices. I've successfully installed and configured OpenWRT 25.12.2 (build r32802-f505120278) on the following hardware.

1. Primary Router:

Linksys MR8300 (x1)

Installation steps performed:

  1. Upgraded stock Linksys firmware to latest (Ver. 2.1.19.215389) via WebUI.
  2. Flashed OpenWrt 22.03.0 factory image via Linksys WebUI: openwrt-22.03.0-ipq40xx-generic-linksys_mr8300-squashfs-factory.bin
  3. Power cycled, SSH'd in, and increased kernel size from 3MB to 5MB (kernsize=500000) to accommodate newer images.
  4. Power cycled again, then flashed OpenWrt 25.12.2 sysupgrade via LuCI: openwrt-25.12.2-ipq40xx-generic-linksys_mr8300-squashfs-sysupgrade.bin
  5. Completed initial setup, updated all packages.
  6. Removed ath10k-ct packages and installed base ath10k packages: ath10k-board-qca4019, ath10k-firmware-qca4019, ath10k-board-qca9888, ath10k-firmware-qca9888, kmod-ath, kmod-ath10k
  7. Installed batman-adv packages: kmod-batman-adv, luci-proto-batman-adv, batctl-full
  8. Configured batman-adv device and mesh interface.

The device is stable and running as the primary router in a batman-adv mesh.

( Side Note : I also enabled the TFTP server, and put the uImage for the KD20 on there in hopes of bringing it back to life, no joy... Yet.
Install OpenWrt on Shuttle OMNINAS KD20 - #116 by konus )

2. Mesh Nodes / APs:

Linksys WHW03 V2 (x2)

Installation steps (per node):

  1. Upgraded stock Linksys firmware to latest (Ver. 2.1.20.216877) via WebUI.
  2. Flashed OpenWrt 25.12.2 factory image directly via Linksys WebUI:
    openwrt-25.12.2-ipq40xx-generic-linksys_whw03v2-squashfs-factory.bin
  3. Power cycled, completed initial setup, updated packages.
  4. Switched from ath10k-ct to base ath10k packages (same list as above).
  5. Installed batman-adv packages (same list as above).
  6. Configured batman-adv mesh interface and connected to the MR8300 primary router.
  7. Set up as AP and tested links (throughput, bandwidth, latency — everything performing well).

The mesh is operational with good real-world performance.

3. NAS:

Shuttle OmniNAS KD20 (oxnas) (x1)

Plans include booting Debian Wheezy rootfs from HDD/USB to update u-boot, then installing 23.05.6 and setting up software RAID. Serial console access (115200 baud) will be key once the adapter arrives.

4. Other:

Linksys SRW2024 24-port managed switch

  • Not currently supported by OpenWRT.
  • Features: 24Ă— 10/100/1000 ports, 2Ă— miniGBIC slots, store-and-forward, 8K MAC table, etc.
  • I've ordered a console cable and will investigate a bit further, but a full OpenWrt port onto this switch would be EPIC! Any insights on feasibility would be welcome.

All devices (except the KD20) are currently running in a live batman-adv mesh setup with the MR8300 as root and the two WHW03 V2 units as mesh APs. WiFi is using the base ath10k firmware after removing the -ct variants.

I'm happy to provide more logs, test specific results, or assist with wiki updates. Let me know the best way to contribute this information officially (ToH edits, device page updates, forum thread, etc.).

Thanks for all the great work on OpenWrt 25.12.2!

Best regards,

Matthew

2

There is no need of power cycling, just reboot while in ssh.

Despite it works, recommanded behavior is to flash a custom image already containing all necessary packages. You may use the firmware selector for this or the image builder. It will be faster and more memory friendly.

Actually the MR8300 would have a 25.12 OpenWrt and a 22.03 on the other partition. Flash again the same 25.12 to get rid of 22.03.

3

"just reboot while in ssh."

Understood, thank you. Good to know. That probably would have saved me some time during this process.

"Despite it works, recommanded behavior is to flash a custom image already containing all necessary packages."

That makes sense. I had followed a "setup guide" on another forum for the batman-adv mesh system, which suggested that the ath10k-ct board, firmware, and kmod files would cause some issues with the mesh itself. <--- That may have been inaccurate, but I figured that I would just follow each step during this setup.

"Actually the MR8300 would have a 25.12 OpenWrt and a 22.03 on the other partition. Flash again the same 25.12 to get rid of 22.03."

Ah! Yes. Good reminder, I will do that.

Thanks for your time and advise @badulesia I sincerely appreciate it.

4

I am interested in learning more about the image builder, I haven't looked into it enough to feel confident, yet... but I will, indeed.

Thanks again @badulesia

5

Select the device, than click on Customize installed packages and/or first boot script
Than feel free to delete and add packages at your convinience. Be cautious not to delete core packages. Any typo error will throw a build error.

Did you also replace wpad-basic-mbedtls with the full wpad-mbedtls?

6

Actually, I replaced wpad-basic-mbedtls with wpad-mesh-wolfssl < - - - I will confirm the package name here shortly... I believe that's what it was called, I will verify. < - - - That was required to enable 802.11s.

7

@badulesia

I just confirmed :

wpad-mesh-wolfssl
version : 2025.08.26~ca266cc2-r1

is installed on the MR8300 and both WHW03 V2's at this time.

8

Good to know. This could save me a lot of time moving forward. I will do some more reading on this topic.

Thank you.

9

The mesh version is not stricly dedicated to mesh, it just add the few functions necessary to mesh that are lacking in wpad-basic. If you plan to use advanced wifi features, better use the full version wpad-wolfssl.

Any particular reason to use wolfssl instead of default mbedtls?

I will be curious to read your wifi settings: I tried once to create a mesh with the MR8300 and never succeeded. I remember trying both ct and non-ct drivers.

10

I see, OK, good to know.

Last night, I spent some time reading more about the 'Image Builder' process. I may very well deploy the recommended wpad-wolfssl ( full package ). Thank you.

No particular reason, other then the aforementioned online forum(s) that provided me with some guidance & recommendations for installing and configuring batman-adv. (Open-Mesh) (Benkay86's Github) (OpenWRT's batman-adv Wiki) ("Installation" section of Wiki)

That having been said, I do see the note on the Wiki page that states :

" As of September 2019, wpad-openssl or wpad-wolfssl are also sufficient for 802.11s use and are the full version of wpad. " <--- I should have gone with the full version of wpad, upon reflection, and you making me aware of this. Thank you.

So I'll start by saying this... I live in British Columbia, Canada ( The west coast ), we live just south of Vancouver, and our ISP delivers fiber into our living room, connected to their Nokia switch, through a Cat6 cable connected directly to one of those LAN ports, I average (985Mbps) download & between (925-950Mbps) upload to the ISPs data center in the city (Vancouver); about 30km / 18.5miles from our townhouse. <--- so that defines what our home is working with at the WAN side of the equation.

The ISP has leased us x1 WiFi 6E router/AP, and I also purchased x3 additional units second hand from Facebook Marketplace. So... I have configured the following :

Downstairs ( front ) = AP1 :
5Ghz LOW CH 36 ( 160Mhz bandwidth )

Downstairs ( rear ) = AP2 :
6Ghz CH 197 ( 160Mhz bandwidth )

Upstairs ( front ) = AP3 :
5Ghz LOW CH 64 ( 160Mhz bandwidth )
5Ghz HIGH CH 149 ( 80Mhz bandwidth ) - - - Guest Network

Upstairs ( rear ) = AP4 :
6Ghz CH 69 ( 160Mhz bandwidth )

We live in an area/complex where all of the 2.4Ghz and 5.8Ghz bands are completely saturated, and the SINR(s) aren't great, that's why I purchased the 6E APs, so that both my girlfriend and I would have excellent throughput, and very low latency's during the workday.

I routinely benchmark our WiFi;

My desktop is currently connected to 5Ghz Low ( upstairs ), and I just got the following results : 794.5 Down / 609.5 Up ( Idle Latency = 6ms, Download Latency = 13ms, Upload Latency = 9ms, Jitter = 2ms ).

My Samsung Galaxy 23-Ultra is connected to the 6Ghz, and I just got these results to the same server : 925 Down / 816 Up ( Idle Latency = 4ms, Download Latency = 11ms, Upload Latency = 8ms, Jitter = 1ms )

I mention all of the above, simply to let you know that our 6E WiFi is totally awesome.

I actually purchased the Linksys MR8300 and the Velop mesh APs primarily to setup OpenWRT, host a TFTP server, and hopefully bring my Shuttle Omninas KD20 back to life... <--- Still working on that, fingers crossed.

The other reason was to build a separate and isolated "guest network" for my girlfriend's adult children ( x2 boys in their twenties ) who sit in their rooms all day playing Xbox ( which I think is ridiculous, but it is what it is... ). My plan for the "Guest Network" was mostly to keep those boys from consuming all the bandwidth during the workday, which was happening when we gave them full access to our main network... My girlfriend and I both do work from home, and so that wasn't sustainable, so I intentionally setup a guest network with limited bandwidth and throughput. As mentioned above, that network is currently being broadcast upstairs on AP3 :
( 5Ghz HIGH CH 149 ( 80Mhz bandwidth ) - - - Guest Network )

So... I know that I'm rambling, and that this has been "long winded", I apologize for that, but we've reached that part of the story, where OpenWRT enters the scene, once again. My girlfriend's boys live in the very front of our townhouse, over our garage/parking area, where the WiFi congestion is especially bad, because their facing our neighbors on all sides, and across the street, etc... So, that having been said, here is how the OpenWRT gear is configured now :

MR8300

  • Radio0 = QCA9886 802.11ac/n ( 5Ghz HIGH )

    • Connected to the Guest network of our main WiFi 6E system.
      Mode: Client
      Encryption: WPA2 PSK (CCMP)
      Channel: 149 (5.745 GHz)
      Tx-Power: 30 dBm
      Signal: -46 dBm | Noise: -101 dBm
      Bitrate: 866.7 Mbit/s | Country: CA

  • Radio1 = IPQ4019 802.11b/g/n ( 2.4Ghz )

    • Broadcasting the Batman-adv mesh out to AP1 & AP2
      Mode: Mesh Point ( 802.11s )
      Encryption: WPA3 SAE (CCMP)
      Channel: 3 (2.422 GHz)
      Tx-Power: 30 dBm
      Signal: -34 dBm | Noise: -101 dBm
      Bitrate: 144.4 Mbit/s | Country: CA

  • Radio2 = IPQ4019 802.11b/g/n ( 5Ghz LOW )

    • Not Used at this time.
      • Obviously the mesh ( backhaul ) should be going out on this radio, but I'm not interested in providing those two "gamers" with any more throughput, and I'm also not adding any unnecessary interference to my primary network by utilizing radio1 ( above ) broadcasting on CH3 of the 2.4Ghz spectrum. <--- so this works for now.

AP1

  • Radio0 = QCA9886 802.11ac/n ( 5Ghz HIGH )

    • Broadcasting the "VideoGames" SSID out to the boys devices in the front of the house. ( 802.11r Fast Transition is enabled )
      Mode: Master | SSID: VideoGames
      Encryption: WPA2 PSK (CCMP)
      Channel: 108 (5.540 GHz)
      Tx-Power: 26 dBm
      Signal: -44 dBm | Noise: -99 dBm
      Bitrate: 866.7 Mbit/s | Country: CA

  • Radio1 = IPQ4019 802.11b/g/n ( 2.4Ghz )

    • Connected to the Batman-adv mesh
      Mode: Mesh Point ( 802.11s )
      Encryption: WPA3 SAE (CCMP)
      Channel: 3 (2.422 GHz)
      Tx-Power: 30 dBm
      Signal: -36 dBm | Noise: -104 dBm
      Bitrate: 137.2 Mbit/s | Country: CA

  • Radio2 = IPQ4019 802.11b/g/n ( 5Ghz LOW )

    • Not Used at this time.

AP2

  • Radio0 = QCA9886 802.11ac/n

    • Broadcasting the "VideoGames" SSID out to the boys devices in the front of the house. ( 802.11r Fast Transition is enabled )
      Mode: Master | SSID: VideoGames
      Encryption: WPA2 PSK (CCMP)
      Channel: 132 (5.660 GHz)
      Tx-Power: 30 dBm
      Signal: -47 dBm | Noise: -97 dBm
      Bitrate: 794.4 Mbit/s | Country: CA

  • Radio1 = IPQ4019 802.11b/g/n ( 2.4Ghz )

    • Connected to the Batman-adv mesh
      Mode: Mesh Point ( 802.11s )
      Encryption: WPA3 SAE (CCMP)
      Channel: 3 (2.422 GHz)
      Tx-Power: 30 dBm
      Signal: -40 dBm | Noise: -99 dBm
      Bitrate: 137.2 Mbit/s | Country: CA

  • Radio2 = IPQ4019 802.11b/g/n ( 5Ghz LOW )

    • Not Used at this time.
11

lol.
I was no asking for the description of the network at home :innocent:. I was refering to the wifi configuration file i.e. /etc/config/wireless. Don't forget to redact private data (SSID, password). Goal is to see what I missed last time I tried. I forgot to mention that I didn't try batman.

12

Understood, sorry about that.

Please see below :

Linksys MR8300 /etc/config/wireless

1
2 config wifi-device 'radio0'
3 option type 'mac80211'
4 option path 'soc/40000000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
5 option band '5g'
6 option channel '132'
7 option htmode 'VHT80'
8 option country 'CA'
9 option cell_density '0'
10
11 config wifi-device 'radio1'
12 option type 'mac80211'
13 option path 'platform/soc/a000000.wifi'
14 option band '2g'
15 option channel '3'
16 option htmode 'HT40'
17 option country 'CA'
18 option cell_density '0'
19
20 config wifi-device 'radio2'
21 option type 'mac80211'
22 option path 'platform/soc/a800000.wifi'
23 option band '5g'
24 option channel '36'
25 option htmode 'VHT40'
26 option country 'CA'
27 option cell_density '0'
28
29 config wifi-iface 'wifinet0'
30 option device 'radio0'
31 option mode 'sta'
32 option network 'wwan'
33 option ssid '00'
34 option bssid '00:00:00:00:00:00'
35 option encryption 'psk2'
36 option key '00'
37 option bridge_isolate '1'
38
39 config wifi-iface 'wifinet1'
40 option device 'radio1'
41 option mode 'mesh'
42 option encryption 'sae'
43 option mesh_id '00'
44 option mesh_fwding '0'
45 option mesh_rssi_threshold '0'
46 option key '00'
47 option network 'batmesh'
48
49 config wifi-iface 'wifinet2'
50 option device 'radio2'
51 option mode 'ap'
52 option ssid '00'
53 option encryption 'psk2'
54 option key '00'
55 option ieee80211r '1'
56 option ft_over_ds '0'
57 option ft_psk_generate_local '1'

Linksys WHW03_V2 "AP1" /etc/config/wireless

1
2 config wifi-device 'radio0'
3 option type 'mac80211'
4 option path 'soc/40000000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
5 option band '5g'
6 option channel '108'
7 option htmode 'VHT80'
8 option country 'CA'
9 option cell_density '0'
10
11 config wifi-device 'radio1'
12 option type 'mac80211'
13 option path 'platform/soc/a000000.wifi'
14 option band '2g'
15 option channel '3'
16 option htmode 'HT40'
17 option country 'CA'
18 option cell_density '0'
19
20 config wifi-device 'radio2'
21 option type 'mac80211'
22 option path 'platform/soc/a800000.wifi'
23 option band '5g'
24 option channel '48'
25 option htmode 'VHT80'
26 option country 'CA'
27 option cell_density '0'
28
29 config wifi-iface 'wifinet0'
30 option device 'radio1'
31 option mode 'mesh'
32 option encryption 'sae'
33 option mesh_id '00'
34 option mesh_fwding '0'
35 option mesh_rssi_threshold '0'
36 option key '00'
37 option network 'batmesh'
38
39 config wifi-iface 'wifinet1'
40 option device 'radio0'
41 option mode 'ap'
42 option ssid '00'
43 option encryption 'psk2'
44 option key '00'
45 option network 'lan'
46 option ieee80211r '1'
47 option ft_over_ds '0'
48 option ft_psk_generate_local '1'

Linksys WHW03_V2 "AP2" /etc/config/wireless

1
2 config wifi-device 'radio0'
3 option type 'mac80211'
4 option path 'soc/40000000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
5 option band '5g'
6 option channel '104'
7 option htmode 'VHT80'
8 option country 'CA'
9 option cell_density '0'
10
11 config wifi-device 'radio1'
12 option type 'mac80211'
13 option path 'platform/soc/a000000.wifi'
14 option band '2g'
15 option channel '3'
16 option htmode 'HT40'
17 option country 'CA'
18 option cell_density '0'
19
20 config wifi-device 'radio2'
21 option type 'mac80211'
22 option path 'platform/soc/a800000.wifi'
23 option band '5g'
24 option channel '36'
25 option htmode 'VHT80'
26
27 config wifi-iface 'wifinet0'
28 option device 'radio0'
29 option mode 'ap'
30 option ssid '00'
31 option encryption 'psk2'
32 option key '00'
33 option network 'lan'
34 option ieee80211r '1'
35 option ft_over_ds '0'
36 option ft_psk_generate_local '1'
37
38 config wifi-iface 'wifinet1'
39 option device 'radio1'
40 option mode 'mesh'
41 option encryption 'sae'
42 option mesh_id '00'
43 option mesh_fwding '0'
44 option mesh_rssi_threshold '0'
45 option key '00'
46 option network 'batmesh'

13

Just in case, here is some additional information on these devices as well :

Linksys MR8300

cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "sbl1"
mtd1: 00100000 00020000 "mibib"
mtd2: 00100000 00020000 "qsee"
mtd3: 00080000 00020000 "cdt"
mtd4: 00080000 00020000 "appsblenv"
mtd5: 00080000 00020000 "ART"
mtd6: 00200000 00020000 "appsbl"
mtd7: 00080000 00020000 "u_env"
mtd8: 00040000 00020000 "s_env"
mtd9: 00040000 00020000 "devinfo"
mtd10: 05800000 00020000 "kernel"
mtd11: 05300000 00020000 "rootfs"
mtd12: 05800000 00020000 "alt_kernel"
mtd13: 05300000 00020000 "alt_rootfs"
mtd14: 00100000 00020000 "sysdiag"
mtd15: 04680000 00020000 "syscfg"

fw_printenv
altkern=5f80000
baudrate=115200
boot_ver=1.3.3
bootcmd=if test $auto_recovery = no; then bootipq; elif test $boot_part = 1; then run bootpart1; else run bootpart2; 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
ethact=eth0
flash_type=2
flashimg=tftp $loadaddr $image && nand erase $prikern $imgsize && nand write $loadaddr $prikern $filesize
flashimg2=tftp $loadaddr $image && nand erase $altkern $imgsize && nand write $loadaddr $altkern $filesize
image=rogue.img
imgsize=5800000
ipaddr=192.168.1.1
loadaddr=84000000
machid=8010006
netmask=255.255.255.0
partbootargs=init=/sbin/init rootfstype=ubifs ubi.mtd=11,2048 root=ubi0:ubifs rootwait rw
partbootargs2=init=/sbin/init rootfstype=ubifs ubi.mtd=13,2048 root=ubi0:ubifs rootwait rw
prikern=780000
serverip=192.168.1.254
stderr=serial
stdin=serial
stdout=serial
boot_part_ready=3
kernsize=500000
boot_part=2
auto_recovery=yes

cat /etc/os-release
NAME="OpenWrt"
VERSION="25.12.2"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt 25.12.2"
VERSION_ID="25.12.2"
HOME_URL="https://openwrt.org/"
BUG_URL="https://bugs.openwrt.org/"
SUPPORT_URL="https://forum.openwrt.org/"
FIRMWARE_URL="https://downloads.openwrt.org/"
BUILD_ID="r32802-f505120278"
OPENWRT_BOARD="ipq40xx/generic"
OPENWRT_ARCH="arm_cortex-a7_neon-vfpv4"
OPENWRT_TAINTS=""
OPENWRT_DEVICE_MANUFACTURER="OpenWrt"
OPENWRT_DEVICE_MANUFACTURER_URL="https://openwrt.org/"
OPENWRT_DEVICE_PRODUCT="Generic"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="OpenWrt 25.12.2 r32802-f505120278"
OPENWRT_BUILD_DATE="1774469393"

Linksys WHW03_V2 "AP1"

cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "SBL1"
mtd1: 00100000 00020000 "MIBIB"
mtd2: 00100000 00020000 "QSEE"
mtd3: 00080000 00020000 "CDT"
mtd4: 00200000 00020000 "APPSBL"
mtd5: 00080000 00020000 "ART"
mtd6: 00080000 00020000 "u_env"
mtd7: 00040000 00020000 "s_env"
mtd8: 00040000 00020000 "devinfo"
mtd9: 0a100000 00020000 "kernel"
mtd10: 09b00000 00020000 "rootfs"
mtd11: 0a100000 00020000 "alt_kernel"
mtd12: 09b00000 00020000 "alt_rootfs"
mtd13: 00200000 00020000 "sysdiag"
mtd14: 0b500000 00020000 "syscfg"

fw_printenv
altkern=a800000
auto_recovery=yes
baudrate=115200
boot_part=1
bootcmd=if test $auto_recovery = no; then bootipq; elif test $boot_part = 1; then run bootpart1; else run bootpart2; 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
fdt_high=87000000
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=nodes_v2.img
imgsize=a100000
ipaddr=192.168.1.11
kernsize=d00000
loadaddr=81000000
maxpartialboots=3
partbootargs=init=/sbin/init rootfstype=ubifs ubi.mtd=rootfs root=ubi0:ubifs rootwait rw
partbootargs2=init=/sbin/init rootfstype=ubifs ubi.mtd=alt_rootfs root=ubi0:ubifs rootwait rw
prikern=700000
serverip=192.168.1.100

cat /etc/os-release
NAME="OpenWrt"
VERSION="25.12.2"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt 25.12.2"
VERSION_ID="25.12.2"
HOME_URL="https://openwrt.org/"
BUG_URL="https://bugs.openwrt.org/"
SUPPORT_URL="https://forum.openwrt.org/"
FIRMWARE_URL="https://downloads.openwrt.org/"
BUILD_ID="r32802-f505120278"
OPENWRT_BOARD="ipq40xx/generic"
OPENWRT_ARCH="arm_cortex-a7_neon-vfpv4"
OPENWRT_TAINTS=""
OPENWRT_DEVICE_MANUFACTURER="OpenWrt"
OPENWRT_DEVICE_MANUFACTURER_URL="https://openwrt.org/"
OPENWRT_DEVICE_PRODUCT="Generic"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="OpenWrt 25.12.2 r32802-f505120278"
OPENWRT_BUILD_DATE="1774469393"

Linksys WHW03_V2 "AP2"

cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "SBL1"
mtd1: 00100000 00020000 "MIBIB"
mtd2: 00100000 00020000 "QSEE"
mtd3: 00080000 00020000 "CDT"
mtd4: 00200000 00020000 "APPSBL"
mtd5: 00080000 00020000 "ART"
mtd6: 00080000 00020000 "u_env"
mtd7: 00040000 00020000 "s_env"
mtd8: 00040000 00020000 "devinfo"
mtd9: 0a100000 00020000 "kernel"
mtd10: 09b00000 00020000 "rootfs"
mtd11: 0a100000 00020000 "alt_kernel"
mtd12: 09b00000 00020000 "alt_rootfs"
mtd13: 00200000 00020000 "sysdiag"
mtd14: 0b500000 00020000 "syscfg"

fw_printenv
altkern=a800000
auto_recovery=yes
baudrate=115200
bootcmd=if test $auto_recovery = no; then bootipq; elif test $boot_part = 1; then run bootpart1; else run bootpart2; 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
fdt_high=87000000
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=nodes_v2.img
imgsize=a100000
ipaddr=192.168.1.11
kernsize=d00000
loadaddr=81000000
machid=8010006
maxpartialboots=3
partbootargs=init=/sbin/init rootfstype=ubifs ubi.mtd=rootfs root=ubi0:ubifs rootwait rw
partbootargs2=init=/sbin/init rootfstype=ubifs ubi.mtd=alt_rootfs root=ubi0:ubifs rootwait rw
prikern=700000
serverip=192.168.1.236
stderr=serial
stdin=serial
stdout=serial
boot_part_ready=3
boot_part=1

cat /etc/os-release
NAME="OpenWrt"
VERSION="25.12.2"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt 25.12.2"
VERSION_ID="25.12.2"
HOME_URL="https://openwrt.org/"
BUG_URL="https://bugs.openwrt.org/"
SUPPORT_URL="https://forum.openwrt.org/"
FIRMWARE_URL="https://downloads.openwrt.org/"
BUILD_ID="r32802-f505120278"
OPENWRT_BOARD="ipq40xx/generic"
OPENWRT_ARCH="arm_cortex-a7_neon-vfpv4"
OPENWRT_TAINTS=""
OPENWRT_DEVICE_MANUFACTURER="OpenWrt"
OPENWRT_DEVICE_MANUFACTURER_URL="https://openwrt.org/"
OPENWRT_DEVICE_PRODUCT="Generic"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="OpenWrt 25.12.2 r32802-f505120278"
OPENWRT_BUILD_DATE="1774469393"

14

In regards to the above ( /etc/config/wireless ) data.

My batman-adv device is called "bat0", and the interface is called "batmesh".

15

Can confirm it works well on the Linksys MR8300, followed the upgrade path instructions and they were precise. Took a bit of ssh & nano effort to get the 2.4g/5g bridged with two different ssids, but it works nicely. Looking forward to what else this setup can do.

16

I have been using the usb3 port of a Linksys 8300 with a WD 5.25 HDD for several years. This host also runs a transmission daemon and nfs server to export the content. I prefered to use a disk that have they own power source to not extract power from the usb port. I also use hdd idle to power off the drive when idle. And twice a day to backup vnstat and collectd stats.

17

I had very bad results with 802.11r, at first sight not because OpenWRT, but caused by bad behaviour in the clients (lots of “FT: Failed to set PTK to the driver” in their wpa_supplicant.log) that made nearly impossible to keep connected to a Zoom meeting, so I ended disabling 802.11r in the wireless config and the connect/reconnect problem was solved.