This is a package of OpenWRT 21.02.3 stable builds for targets ath79.

Modifications against default tiny packages:

• removed PPP support
  
• removed OPKG
  
• removed SSL support
  
• removed signature checking, etc.
  
• removed swapoff and long options support from busybox
  
• stripped to bare bones
  
• added LuCI
  
• flashing from LuCI switched off (it causes devices to freeze)
  

This way the builds could fit into squashfs (factory/sysupgrade) compatible builds. Relayd or wpad-basic could not fit in anymore.

Please note there is still upgrading incompatibility against deprecated target ar71xx (OpenWRT version 18.06 or older), please see https://openwrt.org/docs/guide-user/inst...x.to.ath79 for more info.

Backup your configuration via webserver, but flash new upgrades using SSH. Webserver most likely doesn't have enough memory to handle file upload as all my tests resulted in the need to reboot the device entirely.



If you are unable to log into LuCI, you probably have old /etc/config/uhttpd file present and there are attempts to redirect you to HTTPS protocol. Remove it (use rm /etc/config/uhttpd) and re-flash using the guide above.

Builds have not been tested for all devices, but compiling resulted in no errors.


https://openwrt.ashus.net/21.02.3-target...tiny-luci/
For wget in console you can use extra configured non-secure source http://openwrt.ashus.net/21.02.3-targets...tiny-luci/

Hi man, thanks for your firmware build.


I'm a newbie and currently running official openwrt 18.06 on my WA901ND v3. I'm interested to install this firmware on my WA901ND v3, can i immediately install it from my current openwrt 18.06 thru luci? or i need revert to the tp link stock firmware before install this firmware?

(21.1.2022 12:36)sandalswallow Wrote:  Hi man, thanks for your firmware build.


I'm a newbie and currently running official openwrt 18.06 on my WA901ND v3. I'm interested to install this firmware on my WA901ND v3, can i immediately install it from my current openwrt 18.06 thru luci? or i need revert to the tp link stock firmware before install this firmware?

You can use openwrt-ath79-tiny-tplink_tl-wa901nd-v3-squashfs-sysupgrade.bin and flash directly from another OpenWRT via web interface or SSH without keeping data. Then do careful restore each configuration part at a time from your backup. Subsequent flashes to new versions will have to be done via SSH.

(22.1.2022 02:02)Ashus Wrote:  

(21.1.2022 12:36)sandalswallow Wrote:  Hi man, thanks for your firmware build.


I'm a newbie and currently running official openwrt 18.06 on my WA901ND v3. I'm interested to install this firmware on my WA901ND v3, can i immediately install it from my current openwrt 18.06 thru luci? or i need revert to the tp link stock firmware before install this firmware?

You can use openwrt-ath79-tiny-tplink_tl-wa901nd-v3-squashfs-sysupgrade.bin and flash directly from another OpenWRT via web interface or SSH without keeping data. Then do careful restore each configuration part at a time from your backup. Subsequent flashes to new versions will have to be done via SSH.

thanks for confirmation sir. i'm actually almost doing that (according openwrt upgrade instruction) but i'm not really sure if those guide only for official firmware or for another non official firmware as well, so i decided to wait your confirmation for a night lmao.

once again, thank you sir and sorry for my horrible english. cheers

I need openwrt-ath79-tiny-tplink_tl-wr941nd-v6-squashfs-factory.bin have wpad-mesh-openssl  or wpad (full) and remove IPv6 use for full fast roaming multi APs (need 802.11kvr). Please help me! Thank...

(9.3.2022 06:49)vanminh0311@gmail.com Wrote:  I need openwrt-ath79-tiny-tplink_tl-wr941nd-v6-squashfs-factory.bin have wpad-mesh-openssl  or wpad (full) and remove IPv6 use for full fast roaming multi APs (need 802.11kvr). Please help me! Thank...

The same need. I would like to use these device's tiny firmwares with mesh/roaming feature
Please Can you build or give me a hint to build firmwares

You probably need to set up a linux virtual machine and build it yourself. You can use the "config" files I attach to various ROMs - they just need to be renamed to ".config". Then you can do your modifications and try to make them all fit, but I don't have enough time to do this for you.

https://openwrt.org/docs/guide-developer...uild-guide
https://openwrt.org/docs/guide-developer...uildsystem
https://openwrt.org/docs/guide-developer...uildsystem

(10.3.2022 10:44)Ashus Wrote:  You probably need to set up a linux virtual machine and build it yourself. You can use the "config" files I attach to various ROMs - they just need to be renamed to ".config". Then you can do your modifications and try to make them all fit....

Stupid question; how do you know if it fits?

I did something like the following:

• clone openwrt git repo
  
• check out openwrt-21.02 branch
  
• follow usual steps up to menuconfig, then...
  
• download your config and place it as .config
  
• then, in menuconfig:
  
•    selected specific target profile "TP-Link TL-WA901ND v5"
  
•    under Network -> Wireless, selected wpad-basic instead of wpad-mini
  
• proceed with build as usual
  

The build completed successfully, and produced images that look the same size as yours, and it seems to be working (including 802.11r). Is this likely to come back and haunt me later?

I notice that /overrlay is a bit tight, at 232K used of 320K total, but it's just an AP....

I also noticed that some items got disabled in the config (perhaps they are needed by other ath79_tiny target profiles, but not the single one that I care about, and this saved me some space?):

< CONFIG_DEFAULT_ath10k-firmware-qca9888-ct=y
< CONFIG_DEFAULT_kmod-ath10k-ct=y609,611d606
< CONFIG_DEFAULT_kmod-usb-chipidea2=y
< CONFIG_DEFAULT_kmod-usb-ledtrig-usbport=y
< CONFIG_DEFAULT_kmod-usb2=y
< CONFIG_DEFAULT_rssileds=y

Thanks for sharing your work anyway!

(13.8.2022 05:59)Dseven Wrote:  

(10.3.2022 10:44)Ashus Wrote:  You probably need to set up a linux virtual machine and build it yourself. You can use the "config" files I attach to various ROMs - they just need to be renamed to ".config". Then you can do your modifications and try to make them all fit....

Stupid question; how do you know if it fits?

Well if it builds, it fits. If there are problems with stability, try to remove something. I found out, that on some devices, it's better to use 19.07.10, because it's more stable. For a regular AP, older kernel shouldn't be too big of a problem.

(14.8.2022 05:18)Ashus Wrote:  Well if it builds, it fits. If there are problems with stability, try to remove something. I found out, that on some devices, it's better to use 19.07.10, because it's more stable. For a regular AP, older kernel shouldn't be too big of a problem.

OK, thanks. It seems OK so-far, but I couldn't say I've stress-tested it.

Today I was playing around with trying to build 21.02 for the BT Home Hub 3 Type A. I had to strip some stuff out to get the kernel to fit into the allocated 0x200000. I did get an image to build, but I'm not brave enough to try to install it yet - would have to open the case back up if I need to unbrick it