TP-Link TL-WR1043ND wireless issues

[SmokiestGrunl]

Wireless on my TL-WR1043ND stops working after a couple of hours, wired stays connected and works fine how ever wireless goes down.

It doesn't appear on the PS3 or on Windows.

[SmokiestGrunl]

Bump

[yager86]

Hi!

Which version are you using? What are your wireless settings?
Did you install anything else besides gargoyle (bittorrent, dlna, etc)?
Do other services stop too?

[nikil511]

I also have problems with Gargoyle Version:1.4.2 and TL-WR1043ND
I had no problems with 1.3.x
I ve upgraded to v1.4.2 about a week now, and I get wifi-problems randomly every few hours/minutes on my laptop & tablet, while at the sametime desktop is fine (over ethernet)

The symptom is that Wifi is not working for a few minutes, without reporting any disconnetion though! If I turn WIFI off/on from laptop/tablet, it reconnects and everything is fine.

My setup is the following:
Configure Device As: Gateway
Internet / WAN Connect Via: Disabled
Router IP: 192.168.2.100
Subnet Mask:255.255.255.0
Gateway: 192.168.2.1 (my ADSL modem)
Allow Alternate DNS:allow
Custom DNS Servers: my adsl provider's dns

Wireless Mode:AP
Operation mode: N+G+B
channel widgh: 40Mhz(2nd above)
power:max
mac filter: disabled
channel:7
encryption WPA PSK
Ssid prodcast
isolation: disabled

ALL OTHER SETTINGS ARE DEFAULT

Btw, congrats on the excellent work!
If problem can not be solved, I will happily return to v1.3

[stormlabs]

I also have a TP-Link WR1043ND and gargoyle 1.4.2 and am having intermittent wireless problems.

Sometimes the wireless just stops transmitting data (but appears to be connected) and when i try to reconnect, Windows can't get a response from DHCP and gives me the default 169.*.*.* IP. However, if i connect through wired ethernet all services are working ...

[stormlabs]

Follow-up to my post.

I have to reboot the router to regain wireless access. Will try downgrading to 1.3 and see if it cures it.

EDIT:
Apparently not, after an unknown amount of time and a reconnect it can get DHCP again.

[stormlabs]

I'm now running 1.4.0 and had the same problems.
The problems can be fixed by SSHing into the router and doing:

/etc/init.d/network reload

... while connected through wired ethernet obviously. So, some daemon is dying or getting stuck.

[sc0tty]

Same issue. Running 1.4.3 on a RSPro with a TL-WN861N mini pci, V2.

[stormlabs]

I've since found that doing:

wifi

... at the router command line works to fix this. It basically disables and enables again the wireless interface.

[Markuz Nightwind]

I'm having exactly the same problem with any 1.4.x version of gargoyle on a router v1.8. We need to figure out what setting is causing this to have this fixed ;(