Equipment Hangs
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Equipment Hangs
Region : Others
Model : TL-WR941ND
Hardware Version : V3
Firmware Version : 3.13.9 Build 120201 Rel.54965n
ISP :
Hello all.
We are trying to use a TL-WR941ND purchased about a month ago, but it keeps hanging, usually within a day or so of operation.
To be clear: by "hanging" I mean the device stops providing wireless services (its SSID is no longer visible in WiFi clients) and becomes nonresponsive to pings or control access attempts (via settings web page) from the internal network connections.
The device is used in a very simple scenario, where it's being employed as a simple access point, not as a router. As such, the device's configuration is as follows:
* WAN interface is configured with a dummy static IP (10.10.10.10/24) with gateway and DNS set to the internal IP address of the actual routing device connected to the external world.
* LAN interface is configured with an IP address inside the actual internal IP subnet (192.168.1.0/24).
* DHCP is also disabled as this service is already provided.
* Wireless settings: radio enabled, SSID broadcast enabled, WDS disabled, 11bgn mixed mode, auto channel width, max TX rate, channel 7 (manually set). Using WPA-PSK security.
Rest of the settings are unchanged from their default values, as the device isn't being used as an IP router by any client - just as a WiFi/Ethernet layer 2 bridge. We're using what appears to be TP-Link's latest stock firmware for the device.
The settings described above appear to provide the connectivity required by the WiFi clients. However, the device continuously hangs within a day or so of operation, requiring someone to physically attend to the device and cold-restarting it (disconnecting it from power and reconnecting it) to regain an operational state.
After performing a cold restart, the system log shows nothing beyond the startup entries: "System started" entry followed by security info entries regarding enabled protocols. Then the device appears to work well for a while, until it hangs again, forcing again someone to attend to the device, etc.
If anyone has any insights about this behaviour, why this happens or how can this be solved, I'd appreciate the input.
Thanks,
Sagie.
Model : TL-WR941ND
Hardware Version : V3
Firmware Version : 3.13.9 Build 120201 Rel.54965n
ISP :
Hello all.
We are trying to use a TL-WR941ND purchased about a month ago, but it keeps hanging, usually within a day or so of operation.
To be clear: by "hanging" I mean the device stops providing wireless services (its SSID is no longer visible in WiFi clients) and becomes nonresponsive to pings or control access attempts (via settings web page) from the internal network connections.
The device is used in a very simple scenario, where it's being employed as a simple access point, not as a router. As such, the device's configuration is as follows:
* WAN interface is configured with a dummy static IP (10.10.10.10/24) with gateway and DNS set to the internal IP address of the actual routing device connected to the external world.
* LAN interface is configured with an IP address inside the actual internal IP subnet (192.168.1.0/24).
* DHCP is also disabled as this service is already provided.
* Wireless settings: radio enabled, SSID broadcast enabled, WDS disabled, 11bgn mixed mode, auto channel width, max TX rate, channel 7 (manually set). Using WPA-PSK security.
Rest of the settings are unchanged from their default values, as the device isn't being used as an IP router by any client - just as a WiFi/Ethernet layer 2 bridge. We're using what appears to be TP-Link's latest stock firmware for the device.
The settings described above appear to provide the connectivity required by the WiFi clients. However, the device continuously hangs within a day or so of operation, requiring someone to physically attend to the device and cold-restarting it (disconnecting it from power and reconnecting it) to regain an operational state.
After performing a cold restart, the system log shows nothing beyond the startup entries: "System started" entry followed by security info entries regarding enabled protocols. Then the device appears to work well for a while, until it hangs again, forcing again someone to attend to the device, etc.
If anyone has any insights about this behaviour, why this happens or how can this be solved, I'd appreciate the input.
Thanks,
Sagie.