Posted: Thu Jan 20, 2011 4:45 Post subject: WNDR3700 Wireless Disappears every day
After about 24-48 hours, my router's wireless drops off. I have tried a different build every time it happened. 15962, 15778, 14896 and all have been exhibiting the same problem. My whr-hp-gn used to do this as well unless I scheduled router reboots, but it has stabilized running 15962. My wrt160nl has had the wireless vanish as well, usually every 3days-10days and I have yet to resolve the issues on that one. These routers are all Atheros based and all have shown the same issues on DD-WRT that were non-existent on factory firmwares.
Can someone recommend a build that is working correctly on this router for them? Or tell me what I can do to troubleshoot what is happening when the wireless vanishes?
I'm also having this problem on my WNDR3700 running DD-WRT, happens 2-3 times a day. I always have to login to the router, go to wireless settings and press apply then save changes and the wireless will come back. Where should I keep an eye out, should a solution be found?
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Wed Feb 02, 2011 3:26 Post subject:
Ah then thats ok.
As far as the fixes are concerned, i would check the FTP server for builds, and keep informed with watches to the trac timeline to keep up with any huge changes, they will show there.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Feb 02, 2011 8:31 Post subject:
Over the last 2 weeks theres been over 30 Atheros driver commits, lets hope they or at least some are Atheros driver fixups for all routers and not just one.
I am yet to have my wireless disappear on an Atheros router (dying hostapd I had with older builds doesn't count as the router was out of memory and purposely killing something to get it back). _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
I'm running the same build as the one noted in your signature, but do you think reinstalling the firmware will do any good or is this a problem that needs to be updated coding wise?
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Feb 02, 2011 23:23 Post subject:
Sash wrote:
a shitty driver from atheros is causing this.
Is ath9k better than this? I bet this "shitty" driver is whats causing all my routers to reboot when using P2P on WIRELESS ONLY but im blamed for bad settings as always. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Is ath9k better than this? I bet this "shitty" driver is whats causing all my routers to reboot when using P2P on WIRELESS ONLY but im blamed for bad settings as always.
You did have the same problem with a Broadcom based router which is using a different driver... _________________ Kernel panic: Aiee, killing interrupt handler!
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Thu Feb 03, 2011 5:10 Post subject:
LOM wrote:
tatsuya46 wrote:
Sash wrote:
a shitty driver from atheros is causing this.
Is ath9k better than this? I bet this "shitty" driver is whats causing all my routers to reboot when using P2P on WIRELESS ONLY but im blamed for bad settings as always.
You did have the same problem with a Broadcom based router which is using a different driver...
Broadcom isn't madwifi? I thought it was a universal driver for both. I posted my Atheros wireless settings several times, there is nothing wrong with them let alone a setting that would kill the router.. If you want to see my Broadcom settings by all means ask and i'll put a thread there or PM. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Broadcom isn't madwifi? I thought it was a universal driver for both.
Madwifi is:
Multiband Atheros Driver for Wifi
So now you can start to think of why you have the same problem with both Atheros and Broadcom based routers. _________________ Kernel panic: Aiee, killing interrupt handler!
