I'd like to see this supported too. I'm wanting it to be a WiFi client and AP so I can route traffic from all my devices over my VPN on hotel WiFi.
According to this ticket for openwrt, it's the same chipset as TL-WR841N(D) v9 which is supported.
I'd look at doing it myself, but honestly.. the build system is just a giant mess with no documentation. I'd probably be better off with OpenWrt for my use, at least they use buildroot and I've built new devices on it before.
I've modified the header of the DD-WRT 29218 factory-to-ddwrt build intended for TL-WR841ND v9, so that it will flash on a TL-WR802N v1 or v2 running stock TP-Link firmware.
If the attached build works for you, it can be further updated with any newer-than-29218 webflash build for TL-WR841ND v9.
Disclaimer: I haven't tested the attached builds myself, so I'm not responsible in any way if you brick your router.
Please only flash this build if you know how to unbrick it.
Note: You must be logged in to be able to download the attachment. Don't forget to unpack the zip archive. _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
Last edited by KrypteX on Wed Mar 16, 2016 12:33; edited 6 times in total
I successfully flashed that version also. Unfortunately I ws not able to configure DD-WRT for my needs (AP mode für multiple client and also acting as wifi client to another AP with NAT for internet connection). Now I want to go back to the original firmware but there is no webrevert binary for this router. Is there a way to go back?
@lazytrip How has DD-WRT been running for you on the tl-wr802n? Do any of the builds you have tried support a VPN client? I've read comments that the router doesn't have enough memory for VPN but this post suggests VPN can run on the sister router TL-WR841N: http://www.dd-wrt.com/phpBB2/viewtopic.php?p=905380#905382
This is a long shot, but the OpenWRT forum says the latest factory firmware for the WR841ND doesn't accept non-factory firmware name. Maybe the same thing is happening with the WR802N? Did you try to upgrade from the previous factory firmware, or change the DD-WRT filename?
https://wiki.openwrt.org/toh/tp-link/tl-wr841nd#installation
I'm not in a position to try myself today, but should be able to try tomorrow.
This is a long shot, but the OpenWRT forum says the latest factory firmware for the WR841ND doesn't accept non-factory firmware name. Maybe the same thing is happening with the WR802N? Did you try to upgrade from the previous factory firmware, or change the DD-WRT filename?
https://wiki.openwrt.org/toh/tp-link/tl-wr841nd#installation
Thanks for this information!
Last edited by GreyDoc on Sat Mar 19, 2016 13:09; edited 1 time in total
Posted: Sat Jan 30, 2016 6:06 Post subject: how my TP WR802n(CHhines version) upgrade this firmware
KrypteX wrote:
I've modified the header of the DD-WRT 27506 factory-to-ddwrt build intended for TL-WR841ND v9, so that it will flash on a TL-WR802N v1 running stock TP-Link firmware.
If the attached build works for you, it can be further updated with any newer-than-27506 webflash build for TL-WR841ND v9.
Disclaimer: I haven't tested the attached build myself, so I'm not responsible in any way if you brick your router.
Please only flash this build if you know how to unbrick it.
Because the web gui will check RSA instead of MD5,Thanks
No guarantees as I am a noob. But I think that I came across a solution for you in the process of bricking and unbricking WR802Nv1.
1. Follow youtube video: https://www.youtube.com/watch?v=0k1sxwX5pMk
2. Download Firmware version: http://www.tp-link.us/res/down/soft/TL-WR802N_V1_150717.zip (Other firmware versions have the upgrade error that you mentioned)
3. As in video use IP 192.168.0.66 to TFTP.
4. Rename the firmware to "wr802nv1_tp_recovery.bin"
5. Plug the router into the ethernet and push in reset button for 3-4 seconds. (Make sure firewalls and antivirus turned off)
This is my one and only idea. I hope it helps. If not, I am out of ideas.