Yes, TL-WR841N/ND revisions 5,7,8,9,10,11,12. You should use images marked factory for flashing from stock.
1 Like
Past releases (19.07.x, 18.06.x, 17.01.x) are done and dusted, neither of them will accept new device additions (and 18.06.x, 17.01.x are out of support, not accepting any changes at all). Once a release has been made (after e.g. 19.07.0 or 21.02.0), only bug- and security fixes are accepted, new devices or features have to be merged to master and wait there for the next release branch.
1 Like
I cant find anywhere the information about exploit used to flash OWRT. Got a link?
There is no exploit needed to flash, just rename the file before uploading it.
Huh, neat. Thanks!
Any info on what's included into FACTORY image by default here:
https://openwrt.ashus.net/19.07.7-targets-ath79-tiny-luci/
== Update ==
Throughput data for the TP-Link TL-WR720n v4 router:
LAN client to WAN server over NAT iperf3: 90Mbits/s
LAN client to WAN server over WG tunnel (between router and server) 40Mbits/s
==
I flashed your build to my Tplink WR-720nV4
Default NAT access to Internet is working fine.
root@100mbps:/etc# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 3.0M 3.0M 0 100% /rom
tmpfs 13.6M 80.0K 13.5M 1% /tmp
/dev/mtdblock4 448.0K 228.0K 220.0K 51% /overlay
overlayfs:/overlay 448.0K 228.0K 220.0K 51% /
tmpfs 512.0K 0 512.0K 0% /dev
I will try do some through put test and report back.
Once again, thank you very much for your help!
1 Like
Does anyone know if it is possible to use TP-Link TL-WR841ND as Access Point with other router (non WRT) after flashing OWRT?
1 Like
Yes, it is possible. I recommend using OpenWRT or pfSense or something else secure and regularly updated as router. Any other device could be used as AP, with or without OpenWRT; just disable DNS/DHCP server and use LAN port.
You mean disable on the device that is AP, right?
Yes on APs, the router needs to have those enabled.
One of my devices seems to get its wifi in a tangle in a similar way. Rather then reboot I can press the hardware wifi disable / enable button, or if I'm on a device with a wired connection to it I can ssh and run the command wifi (which on its own also does a stop / start). Despite this suggesting it was some kind of software issue I wasn't able to find a cause in the logs, by looking at memory use, etc. Maybe some other resouce type is being exhausted?
Great compilation! I looked at the packages and saw ipt-offload but again I must ask, do those images have SFE software nat offloading feature? Asking for my WR740N v4.
Sorry, but I don't really know. Also even if it is shown in LuCI, some hardware may not support offloading, try it on and off and if there's a difference, choose the faster/more stable alternative.
1 Like
I tried your image and its working, not the hardware offload though its for another chipset. but yes software offload is working.
1 Like
Nowadays those 4/32MB routers are best for just extending signal range.
Yes, this is what I am using this for 
For IPTV, though, I seem to require igmpproxy (see IGMPv3 (igmpproxy) / Telekom MagentaTV / TP-Link Archer C2600), which has 16 kB and no dependencies apart from libc (which the image should have for luci). Any chance to fit this into the next build? I am using a TP-Link TL-WR841N/ND v9.
Edit: I was able to compile myself on WSL, which works great. Here's short instructions for anyone wanting to try this themselves:
git clone https://git.openwrt.org/openwrt/openwrt.git
cd openwrt
git checkout v19.07.7
./scripts/feeds update -a && ./scripts/feeds install -a
wget https://openwrt.ashus.net/19.07.7-targets-ath79-tiny-luci/config -O .config
make menuconfig # select TP-Link TL-WR841N/ND v9, add igmpproxy, save, exit
make -j4 # build with 4 cores
2 Likes
Hi, Apologies for any ignorance on the chipsets used as this might be why the TL-WA901ND V3 isn't listed but I have two V3 device that I would like to bring back into service as dumb AP's but am not able to compile the sources. Any chance these can be added to the target list?
I am happy to test firmware for these and understand the risks involved in bricking them etc.
Thanks
Newbs
Not sure of the implications of this, but the title of this thread is "... ath79...". In "make menuconfig", the "Atheros ATH79" target system does not include the TL-WA901ND V3 (only V1, V2, V4, V5), so it's kind of expected you don't see it here.
By contrast, V3 can be found in the "Atheros AR7xxx/9xxx" target system (in line with V3 using Atheros AR9341 according to https://openwrt.org/toh/tp-link/tl-wa901nd). In fact, "Atheros AR7xxx/9xxx" includes V1 through V5. But I understand (e.g., from https://www.reddit.com/r/openwrt/comments/c9x2ip/) that that target system is rather non-modern.
Edit: On the other hand, I see V3 being listed here: https://openwrt.org/docs/techref/targets/ath79?datasrt=model
thanks @bers, I wonder if @Ashus can comment. I am not particularly familiar with these ranges of SoC's etc and so a bit lost in what gest ath79 support and what doesnt.
Thanks - Newbs
Okay, I did some digging about the TL-WA901ND v3. Do not try to flash v2 or v4 as their hardware is different and it wouldn't work. It's support has been ported from ar71xx to ath79 on master branch after 19.07 branch was separated. That means new OpenWRT 21.02 will support it when it's finally out.
In the meantime, this git commit https://github.com/openwrt/openwrt/commit/372529d3117ef8cd6dc37d61d405e24ccba3584a adds support, but it can't be cherry-picked without modifications to 19.07.7 stable tag as structure has changed a bit.
I can't guarantee anything and you could brick your devices, but you could try to flash this: https://openwrt.ashus.net/19.07.7-targets-ath79-tiny-luci-tl-wa901-v3/ . Changes in custom-changes.patch correspond to the commit mentioned above.