Posted: Tue Feb 28, 2012 3:30 Post subject: WNDR3700V2
OK this is getting ridiculous. I have to reset ath0 way too many times. The band-aid cron job doesn't always work. Is anyone from DD-WRT developers going to try and fix the fw for this unit? PLease? I would hate to go back to stock. Which dual band router is meant for DD-wrt? E3000? Oh well anyone else out there owning a wndr3700V2 please share your thoughts.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Feb 28, 2012 3:51 Post subject:
It would help to explain the problem.. instead of just "i have to constantly reset ath0", as some say, WNDR3700v2 is an embarrassment to Netgear, their WNDR3700v1 is much better which I do have and can speak for it but I don't have a v2 (or v3). _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
The problem is the only stable fw (r17201) for this unit and also v1s have issues where 2.4ghz radio will die after so long. You didn't know that. It's posted all over this forum. There is a fix to run a cron job to tail a log and restart radio once it fails. I'm asking for a fix for this. I guess you're not aware of this issue. Just don't blame Netgear and call it junk as a way to say this isn't fixable.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Feb 28, 2012 8:12 Post subject:
Actually im well aware of the issues.... half of them are from improper flashes or waiting 10 seconds after flashing then brick it.. and dying radio units are faulty units as it happens to those same units on stock firmware as well. Most do not have the issue. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Hmmm Ok so when I put stock FW back on the unit no issues at all. Can you explain that? Not a faulty router.! It's the driver used by this dd-wrt build. You're just going to go out and say it's the way I flashed the unit or it's a faulty unit.Wow. Maybe I will continue to troubleshoot the madwifi driver issue.
@bcmalloy - Thanks for the info. Can I remove the FW and revert back to stock if needed?
I have a V2 with 17201, it is sad that we do not have an update. But my router has been up for 36 days and have not had any problems with dropped connections or radio locking up and no i'm not using w/e cron job you are referring to. Only reason it's at 36 days is because i had isp issues and had to reboot everything otherwise it would have been 80+ days.
Maybe it is a faulty unit or bad flash?
The only problem i see with this FW is the wifi range which is suppose to be fixed with 17201+ but has other issues. Like one of my laptops shows a signal quality of 1% which is horrible but on the actual laptop it has 3 bars and has no noticeable slow downs when browsing or downloading which says to me the webui is just not reporting the correct values.
Overall i'm actually very happy with 17201 and gives me no network issues that would impact the stability of my network.
Don't use that firmware... Unless you don't care about loosing the wireless functionality... The last stable firmware for the Netgear WNDR3700v2 is r17201...
No firmware versions after r17201 have a wireless tab for WNDR3700v2...
I totally agree with Viking123... It would be really nice if we got a working version of the dd-wrt firmware that was slightly newer that r17201...
Please can someone have a look at resolving the Wireless tab issue for the WNDR3700v2 firmware for all the releases after r17201.
Please can someone have a look at resolving the Wireless tab issue for the WNDR3700v2 firmware for all the releases after r17201.
The bug is fixed so next release, whenever that is, will have working wifi.
There is nothing that can be done with releases between 17201 and 18024, they will not be rebuilt. _________________ Kernel panic: Aiee, killing interrupt handler!
Ok I have been running stock firmware for 2 days now no issues. I'm using AES for security which is supposedly the culprit behind the stuck beacon issue. Multiple N devices connected. What I want to know is difference between what stock FW is using vs. what open source dd-wrt is using. Is it that ath9k driver is being used instead of madwifi. Oh well. Getting ready to switch back to dd-wrt. Ready to try a different router with dd-wrt.
Try the new version of gargoyle just came out everything works perfectly and it has some awesome new QOS fuction, best firmware I've used on my wndr3700v2