Netgear WNDR3800
Up 31 days straight, still working perfectly. This is arguably the best, most stable build for this router, hands down. _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
A few of you mentioned wifi that just stops working over time until you reboot the router.
Any settings to workaround that? I'm seeing it with 2.4Ghz, but I know someone mentioned 5Ghz, too.
First thing I try is change wifi channel. Interference can pop a wifi, my home network will pop on channel 6; a bluetooth keyboard and mouse are suspected. That wifi network now lives happily on channel 10.
You can schedule automatic reboots under [administration > keep alive] i have not experienced wifi quitting, only decreased free ram (and increased remote lag times) with uptime. I think it may be the dnsmasq cache that slowly builds up and eats away at my ram but that's just a guess, those would be the settings I would try changing. But I am content with nightly reboots and haven't hunted for it. This issue is on my home router, which has a main and a guest wifi, firewalled, with QOS running, and between 8 and 15 wireless clients on average connected at any time. So it is fairly busy for a home network. _________________ My Routers:
You can schedule automatic reboots under [administration > keep alive] i have not experienced wifi quitting, only decreased free ram (and increased remote lag times) with uptime. I think it may be the dnsmasq cache that slowly builds up and eats away at my ram but that's just a guess, those would be the settings I would try changing. But I am content with nightly reboots and haven't hunted for it. This issue is on my home router, which has a main and a guest wifi, firewalled, with QOS running, and between 8 and 15 wireless clients on average connected at any time. So it is fairly busy for a home network.
Yes, nightly reboots are a good idea as an attempt at a preventative measure, and I've long done that, but it's not enough anymore to prevent the problem here.
(Interestingly, just "applying settings" is sufficient to get wifi going again, but that's almost as disruptive as a reboot. So even if there were a way to frequently schedule whatever applying settings actually does when there are no settings changes--probably restarts various processes--it wouldn't be practical.)
I'm starting to look into tweaking some advanced wifi settings that others have recommended in the past, but it's a real scatter-shot approach.
I saw it happen yesterday only a few hours after a reboot, and there was only one wifi client using it (doing almost nothing), but I'm going to keep RAM/cache etc in mind anyway.
I am new to the DD-WRT router usage. Getting some strange issues.
TP-Link WR1043NDv3. Flashed with r27506. Router-behind-Router. Want to use IPVanish. Placed new router WAN port into DMZ on old router. Can get PPTP to work, but not OpenVPN client.
IPVanish provides a reasonably good tutorial regarding setup. To keep things simple ... the key ERROR I see in "/var/log/messages" is as follows:
Quote:
Jan 1 00:00:08 DD-WRT daemon.warn openvpn[906]: DEPRECATED OPTION: --tls-remote, please update your configuration
Jan 1 00:00:08 DD-WRT daemon.notice openvpn[906]: Options error: --auth-user-pass fails with '/tmp/auth.conf': No such file or directory
Jan 1 00:00:08 DD-WRT daemon.err openvpn[906]: Options error: Please correct these errors.
Jan 1 00:00:08 DD-WRT daemon.warn openvpn[906]: Use --help for more information.
I tried to debug the complaint about missing "/tmp/auth.conf" file. The file is created in the STARTUP script and DOES exist with proper contents -- verified within a few minutes after reboot. HOWEVER ... two strange issues ...
1. If I use Administration/COMMANDS to manually create a file in "/tmp" and then do an "ls -l" of that file, it does not exist. If I "ls" the entire directory it turns out there appears to be a "?" as last character in the file name.
2. Since the above is *NOT* true of the "/tmp/auth.conf" filename created via STARTUP, and yet I get the error recorded in "/var/log/messages" -- I am wondering if there is a TIMING issue ? Does the set of STARTUP COMMANDS get executed too late ? ( A hint why I suspect this may be the case: IPVanish has an alternate full-script-based method ... within which the same file is created, together with all the other config/startup, and not "auth" error results. (It still ends up not working. )
