Abyssmal wireless performance within 48 hours or less
Posted: Mon Jan 19, 2015 6:21 pm
I recently purchased TL-WR1043ND v2 hardware. Having had an Engenius that just didn't live up to my expectations (lots of issues with the FW), I was hoping to use open source firmwware and kick the home wireless network up a notch.
I upgraded the TL-WR1043ND to Gargoyle 1.7.0 without a hitch and really like the simple interface and ease of configuration. However within 48 hours - no joy. The wireless network appears to have developed significant latency. Performing a constant ping @ 32bytes avg. ping times were in 1700ms with no traffic transiting the device. Using 1500 byte packets and well forget about it - dial up would be way faster. When I perform a hard boot, it resets the performance until another 24-48 hours.
I was really hoping to hoping to use this firmware but having to reboot my router daily is a deal breaker (even with the Engenius I didnt have to do that except the client's WPA2 key would get corrupted) - I reverted back to the stock FW and no latency issues. Stock FW seems to work ok without some of the features I had hoped to use.
Is this a known issue and is there any work around?
Thanks,
SZ
I upgraded the TL-WR1043ND to Gargoyle 1.7.0 without a hitch and really like the simple interface and ease of configuration. However within 48 hours - no joy. The wireless network appears to have developed significant latency. Performing a constant ping @ 32bytes avg. ping times were in 1700ms with no traffic transiting the device. Using 1500 byte packets and well forget about it - dial up would be way faster. When I perform a hard boot, it resets the performance until another 24-48 hours.
I was really hoping to hoping to use this firmware but having to reboot my router daily is a deal breaker (even with the Engenius I didnt have to do that except the client's WPA2 key would get corrupted) - I reverted back to the stock FW and no latency issues. Stock FW seems to work ok without some of the features I had hoped to use.
Is this a known issue and is there any work around?
Thanks,
SZ