I have two TP-LINK WR1043ND v1 routers, both with 3.13.4 build110429 rel 36959n. One is used as my main internet gateway (and access point) on a 40Mbps fiber being used very much. The other is just used as an access point. The first is rock stable. The one used as access point only hangs very often.

I wonder if all these hangs might just be because of faulty / low quality hardware?

Rgds,
Vidar

vidarak,

I suggest that you switch the two routers around (make the one that serves as a gateway become an access point only & vice versa). This should help you determine if it's an hardware issue or a firmware issue. Please let the forum know the results. I personally believe that it is a firmware issue but don't have the time (and resources) to find out. My experience is that if the router radio is disabled it continue to work forever. When radio switch is on it crashed after around 40 hours (even if no wireless connection was made through the whole operating period). To overcome this problem I switch the radio off when I go to sleep and on again when I access my wired PC in the morning. It's easier than doing a physical power-cycle.

I wonder if, when the WR1043ND is crashed, it will not be caused by the poor functioning of the firewall:
(blocking DOS)
I have put in place of the WR1043ND Router one N450R Airlive.
As you will see below.it detected many DOS attacks
The WR1043ND not detect such attacks

Jan 30 19:25:29 mailtool: Send Mail Success
Jan 30 19:31:22 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:31:29 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:31:37 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:31:44 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:31:50 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:31:57 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:32:12 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:34:18 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:34:35 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:34:42 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:34:49 kernel: Blocked DoS Attack type :Synflood.

Jan 30 19:31:22 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:31:29 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:31:37 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:31:44 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:31:50 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:31:57 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:32:12 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:34:18 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:34:35 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:34:42 kernel: Blocked DoS Attack type :Synflood.
Jan 30 19:34:49 kernel: Blocked DoS Attack type :Synflood.

Jan 15 19:39:06 kernel: Blocked DoS Attack type :Pingflood.
Jan 15 17:15:10 kernel: Blocked DoS Attack type :Pingflood.
Jan 15 17:38:20 kernel: Blocked DoS Attack type :Pingflood.
Jan 15 17:41:28 kernel: Blocked DoS Attack type :Pingflood.
Jan 15 17:49:09 kernel: Blocked DoS Attack type :Pingflood.
Jan 15 16:55:38 kernel: Blocked DoS Attack type :Pingflood.
Jan 15 17:08:19 kernel: Blocked DoS Attack type :Pingflood.
Jan 15 15:36:44 kernel: Blocked DoS Attack type :Pingflood.
Jan 15 13:16:36 kernel: Blocked DoS Attack type :Pingflood.
Jan 15 14:02:52 kernel: Blocked DoS Attack type :Pingflood.
Jan 15 12:47:12 kernel: Blocked DoS Attack type :Pingflood.
Jan 15 12:58:03 kernel: Blocked DoS Attack type :Pingflood.
Jan 15 13:09:15 kernel: Blocked DoS Attack type :Pingflood.
Jan 14 10:32:39 kernel: Blocked DoS Attack type :Fraggle.
Jan 13 18:19:17 kernel: Blocked DoS Attack type :Fraggle.
Jan 13 16:19:16 kernel: Blocked DoS Attack type :Fraggle.
Jan 13 16:57:38 kernel: Blocked DoS Attack type :Fraggle.
Jan 13 15:19:17 kernel: Blocked DoS Attack type :Fraggle.

Web interface dies with less than 1 day operation:mad:. can still access internet. just cannot access the 1043 web admin

Region : Hong Kong
Model : TL-WR1043ND
Hardware Version : v1.8
Wireless: on
UPnp: Enabled
Load: 2 client LAN - 1 Gbps, 5 clients WiFi
firmware Version : 3.13.12 Build 121210 Rel.73912n (Beta) ----- upgrade from Build 120405
ISP : Netvigator (PPPoE) 6 Mb/s

I have the same problem with my 1043ND in Canada. I lose wifi and web interface and wired internet access. I have to power-cycle the router regularly, can be a week or an hour. Just now it did it after 10 minutes... I have a 18Mb/1Mb connection.

Hardware Version: WR1043ND v1 00000000

Web interface dies after 12 days operation. Can still access internet (with some clients)

Region : Bulgaria
Model : TL-WR1043ND
Hardware Version : v1.8
Wireless: on
UPnP: Enabled
Load: 1 client (Desktop PC) - LAN - 1 Gbps, 6 clients (Notebook, Tablet, 2 Android Phones, PS3, Smart TV) - WiFi
firmware Version : 3.13.12 Build 121210 Rel.73912n (Beta) ----- upgrade from Build 120405
ISP : Megalan, static IP, 50 mbps

Best uptime - 12 days

web interface still dies, not like before, but dies :(

syntaxerr0r wrote

I have the same problem with my 1043ND in Canada. I lose wifi and web interface and wired internet access. I have to power-cycle the router regularly, can be a week or an hour. Just now it did it after 10 minutes... I have a 18Mb/1Mb connection.

Hardware Version: WR1043ND v1 00000000

Experiencing the same issues as you are, but in the US. Time Warner Cable. Lose wifi, web interface & wired internet access. A VOIP device connected to the router also loses connectivity. Powering off the router is the only thing that fixes it. Have tried all firmware available for the WR1043ND V1 router, up to and including the Beta version 121210.

Does not appear to be a time based issue, as it occurs at random times. Has occurred while streaming video, and also while not streaming video. The router eventually will re-appear to devices, but prompts for a password to connect to this network (when the password is already saved on the device). Once the power has been cycled, connectivity resumes normally with no prompt. Not doing any torrents, iTunes or anything, mostly web surfing on my cell phone or laptop when I happen to notice it. Also, when power has been cycled, all settings in the router have been retained with no apparent issue, so it isn't like it is losing its settings (or passwords).

An extremely aggravating issue!

steve_o wrote

Experiencing the same issues as you are, but in the US. Time Warner Cable. Lose wifi, web interface & wired internet access. A VOIP device connected to the router also loses connectivity. Powering off the router is the only thing that fixes it. Have tried all firmware available for the WR1043ND V1 router, up to and including the Beta version 121210.

Does not appear to be a time based issue, as it occurs at random times. Has occurred while streaming video, and also while not streaming video. The router eventually will re-appear to devices, but prompts for a password to connect to this network (when the password is already saved on the device). Once the power has been cycled, connectivity resumes normally with no prompt. Not doing any torrents, iTunes or anything, mostly web surfing on my cell phone or laptop when I happen to notice it. Also, when power has been cycled, all settings in the router have been retained with no apparent issue, so it isn't like it is losing its settings (or passwords).

An extremely aggravating issue!

I'm going to see if it does the same thing with the latest DD-WRT firmware. Last time I tried it on this router the LAN performance was awful. If I can't find a solution, I'll have to buy another router - not from TPLINK this time.

syntaxerr0r wrote

I'm going to see if it does the same thing with the latest DD-WRT firmware. Last time I tried it on this router the LAN performance was awful. If I can't find a solution, I'll have to buy another router - not from TPLINK this time.

Other posts here leave me wondering if some of the problems I have been experiencing on my main system are related to this driver issue also. I had seen other posts where a router error had caused a BSOD on someone's PC.

I have gotten a zillion of those on my PC, and up until reading that post had been willing to chalk it up to an extremely crappy OS (Windows Vista - an OS I would not wish on my worst enemy). My issues had been getting BSOD's a lot on it, and no settings I ever tried would write an error log. But, when I would see the actual screen, more often than not, the error was:

" DRIVER_IRQL_NOT_LESS_OR_EQUAL"

0xd1 or 7f with netio.sys

Have been thru countless phone calls, forum posts & emails with the MB Manufacturer, who finally asked me add another NIC card to replace the on-board one (did not do that). However, since I installed the Beta version of the firmware, I do not believe I have gotten another BSOD (knock on wood). But, the system had thrown countless ones previously that I would witness to be the overwhelming majority with the netio.sys issue.

Since I am still getting the wireless droupout and the router not being visible to wired or wireless devices (and the power-off & on resolution), I had not connected the lack of BSOD's to the Beta firmware - to me, it was just one less problem. However, in checking the date of when I installed the Beta firmware, with the last BSOD I logged, I find that they are in synch with each other. Given the frequency of BSOD's previously (nearly daily), I don't believe it's coincidental.

Please follow up on your experience with DD-WRT, I have considered using Gargoyle (which I think is a different UI over the same DD-WRT firmware).

Region : Germany
Model : TL-WR1043ND
Hardware Version : v1.1
Wireless: on
UPnp: activated
Load: 1 client Gbit-LAN, 2 Wifi Clients (1 Notebook, 1 Galaxy Nexus)
Current firmware Version : 3.13.12 Build 121210 Rel.73912n (Beta)
ISP : German university ISP

---

The connection drops out randomly, mostly when idle, at least once a day. Full load (up to 100 Mbit down and hundreds of connections (Bittorrent)) doesn't seem to bother the router at all. Casual browsing will suddenly stop and a few minutes later the network connection icon of Windows will change to the yellow triangle of dread and misery. The LEDs on the router seem fine. Only a power cycle will make the router work again.

Never had this problem with DD-WRT but with EVERY original firmware since release and even this beta. I really really would like to have a stable manufacturers firmware since the WiFi performance of the original firmwares is always the best (tested with my late Thinkpad T61 [Intel 4965 AGN] and my recent T410 [Intel 6200 AGN].