You Have to use the Recovery mods to apply firmware if you are on one of the lastes original firmware . i Also give a try and after the flash i get the same issue ..
These locked firmwares have been applied by TP-Links for a while back in 2016 on several of their routers, but then they've changed their minds.
Anyway, find a way to TFTP to a non-locked variant - it may not be as smooth as you'd think.
Here are some step-by-step tutorials for other TP-Link routers that I've noted down over time (don't have time to figure out how this would work for your model specifially, but it should be something similar:
1. Download firmware from TP-Link
1b. Make a new folder and extract .bin file
2. Rename the Bin file to wr841nv11_tp_recovery.bin (or replace v11 with whatever version you're using)
3. Disable all network adapters you don't have plugged into the router
3b. Set the IP address of the PC to 192.168.0.66, default subnet mask, and NO OTHER SETTINGS.
4. Install TFTP software http://tftpd32.jounin.net/tftpd32_download.html
4b. Run TFTP Software
4c. Within TFTP, browse to new directory.
4d. Ensure within 'interfaces' you see the above IP 192.168.0.66
5. Hold WPS/Reset button while router is cycling, the 'lock' light should stay illuminated.
6. Router should grab the Bin file and restore automatically.
7. Thank the good TP-Link Devs for including this feature.
------------------------------------------------
1.) Install Wireshark to snoop Ethernet traffic;
2.) Run Wireshark listening on your Ethernet port;
3.) Connect cable from Ethernet port to LAN port on router;
4.) Use "recovery method," that is, power on while holding reset button, etc.
-- check dd-wrt or OpenWRT device pages or search for TFTP recovery instructions for your model/version router -- to boot router into TFTP recovery mode;
5.) You should see traffic from the router in Wireshark;
6.) Set the IP address of your Ethernet port to the address (192.168.0.66 or 192.168.0.33) that the router is looking for by sending out ARP requests;
7.) You may need to power cycle the router to get it booted into TFTP recovery mode again;
8.) When the router finds that special, correct IP address, look in Wireshark to see what the exact filename is that the router wants to upload;
9.) Rename your stock firmware -- a stripped (non "_boot") firmware -- or the factory-to-ddwrt(-us).bin file to the exact filename the router is looking for.
Then start tftp32d (tftp64d) with this renamed file in the correct folder for tftp32d to find for upload, then reboot the router into TFTP recovery mode.
PATIENCE IS A VIRTUE. I can't stress this strongly enough. Your patience will be rewarded if things are correctly configured.
If the upload window only lasts a second or so, connect both the workstation Ethernet port and the router LAN port to an already-powered-on switch (NOT a hub).
-------------------------------------------------------------------------------------------------------------------------------
I personally prefer how Netgear and others do it where you "tftp" the firmware to the router after putting it in recovery mode.
But TP-Link force the user to run a TFTP Server (tftpd) on their computer, and the router initiates the "tftp" client on its end,
after you rename the firmware to "wr1043nv1_tp_recovery.bin" or some other "****_tp_recovery.bin".
The IP address you set for you computer running the tftpd is 192.168.0.66, but sometimes it is 192.168.1.66... Can be confusing...
Report: The 08-29-2017-r33257 build still has the wan port & LED issues to me.
After I plug the WAN cable to LAN1 port, everything back to normal except that the 4 LAN LEDs can't light up but the wifi router function is ok. I will use it for a few days and see whether it is stable.
Report: The 08-29-2017-r33257 build still has the wan port & LED issues to me.
After I plug the WAN cable to LAN1 port, everything back to normal except that the 4 LAN LEDs can't light up but the wifi router function is ok. I will use it for a few days and see whether it is stable.
My router is WR940Nv3 (international version)
After a few days observation, I found that only the wireless is ok. Other LAN ports can't be used by other devices properly as they can't get the correct NAT IP address (e.g. 192.168.x.x). Instead, the connected device obtain another IP from the WAN..
Thank you KrypteX! This worked. One note for my TL-WR940N v3 (CA) is that the recover file is wr941ndv6_tp_recovery.bin. I also had to increase the ftp timeout to 30 seconds because the server kept giving up on the client.
These locked firmwares have been applied by TP-Links for a while back in 2016 on several of their routers, but then they've changed their minds.
Anyway, find a way to TFTP to a non-locked variant - it may not be as smooth as you'd think.
Here are some step-by-step tutorials for other TP-Link routers that I've noted down over time (don't have time to figure out how this would work for your model specifially, but it should be something similar:
1. Download firmware from TP-Link
1b. Make a new folder and extract .bin file
2. Rename the Bin file to wr841nv11_tp_recovery.bin (or replace v11 with whatever version you're using)
3. Disable all network adapters you don't have plugged into the router
3b. Set the IP address of the PC to 192.168.0.66, default subnet mask, and NO OTHER SETTINGS.
4. Install TFTP software http://tftpd32.jounin.net/tftpd32_download.html
4b. Run TFTP Software
4c. Within TFTP, browse to new directory.
4d. Ensure within 'interfaces' you see the above IP 192.168.0.66
5. Hold WPS/Reset button while router is cycling, the 'lock' light should stay illuminated.
6. Router should grab the Bin file and restore automatically.
7. Thank the good TP-Link Devs for including this feature.
------------------------------------------------
1.) Install Wireshark to snoop Ethernet traffic;
2.) Run Wireshark listening on your Ethernet port;
3.) Connect cable from Ethernet port to LAN port on router;
4.) Use "recovery method," that is, power on while holding reset button, etc.
-- check dd-wrt or OpenWRT device pages or search for TFTP recovery instructions for your model/version router -- to boot router into TFTP recovery mode;
5.) You should see traffic from the router in Wireshark;
6.) Set the IP address of your Ethernet port to the address (192.168.0.66 or 192.168.0.33) that the router is looking for by sending out ARP requests;
7.) You may need to power cycle the router to get it booted into TFTP recovery mode again;
8.) When the router finds that special, correct IP address, look in Wireshark to see what the exact filename is that the router wants to upload;
9.) Rename your stock firmware -- a stripped (non "_boot") firmware -- or the factory-to-ddwrt(-us).bin file to the exact filename the router is looking for.
Then start tftp32d (tftp64d) with this renamed file in the correct folder for tftp32d to find for upload, then reboot the router into TFTP recovery mode.
PATIENCE IS A VIRTUE. I can't stress this strongly enough. Your patience will be rewarded if things are correctly configured.
If the upload window only lasts a second or so, connect both the workstation Ethernet port and the router LAN port to an already-powered-on switch (NOT a hub).
-------------------------------------------------------------------------------------------------------------------------------
I personally prefer how Netgear and others do it where you "tftp" the firmware to the router after putting it in recovery mode.
But TP-Link force the user to run a TFTP Server (tftpd) on their computer, and the router initiates the "tftp" client on its end,
after you rename the firmware to "wr1043nv1_tp_recovery.bin" or some other "****_tp_recovery.bin".
The IP address you set for you computer running the tftpd is 192.168.0.66, but sometimes it is 192.168.1.66... Can be confusing...
Posted: Fri Mar 30, 2018 21:48 Post subject: Lan Not Working WR940N V3 (CA)
Hey guys,
I don't know if it is worth mentioning but I ran into the issue of the lan ports not working and found if I upload the factory-to-ddwrt.bin using Tftp then upload the tl-wr940ndv3-webflash.bin afterwards again using Tftp, the router seems to function normally. Not quite sure what the difference would be as when I uploaded tl-wr940ndv3-webflash.bin through the firmware upgrade option in DD-WRT, I ran into the same issue with the lan not working.
