I've never seen it mentioned by my 16N, every couple of weeks, sometimes months, stop working and upon reboot go back to default settings. Never seen anyone comment on it, and I reset NVRAM once and ultimately was facing the same problem, so nowadays I just reflash the same nvram.bin file every time it does it...
I use build 14537...at the time I last was on the forums it was teh bleeding edge yet "unproblematic" build, don't think future builds will fix my issue.
Joined: 31 Jul 2009 Posts: 492 Location: Toronto, ON, CA
Posted: Thu May 12, 2011 16:08 Post subject:
Transfer rates will depend on other factors such as write and read speeds of hard drives on the two systems. For example, copying from my slow NAS hard drives to my fast desktop hard drive; I can average 75 Megabytes per second transfer speed. If I transfer from a faster data source such as a SSD system to another SSD system, speeds are even faster.
Could someone with an Asus RT-n16 router test the sustained transfer rate between two wired clients (who both have gigabit capable NICs) ?
_________________ Asus RT-N16 [Build King Kong 18050M NEWD-2 K2.6 + Optware + My Page]
thought i would share a simple solution for people to cool their rt-n16. i just purchased mine a couple days ago and had this small netbook cooler sitting around and put it under my router. its powered by usb so plugging it into the back of the router worked perfectly.
Anyone else having issues with the router's WAN connection crapping out when there's lots of simultaneous connections (ie, BitTorrent)? I was losing my WAN IP address for hours at a time randomly when I ran BT. I had to drop the "Max connections per torrent" to 20 and "max connections globally" to 30 to stop getting dropouts. Now I can use BT continuously, but it's pretty slow.
Using Vuze on OS X. DD-WRT v24-sp2 (12/24/10) big
(SVN revision 15962)
I think I may have found a solution to this, for anyone else that's having the same issue. Under Administration -> Management, I changed the TCP congestion control to cubic, dropped the maximum ports to 3072, and dropped the TCP timeout to 120. Haven't had the router lose it's WAN IP address yet.
This turned out to be false. I ended up trying the stock firmware as a last resort, and guess what? It worked perfectly. Much better sustained transfer rates now too. The stock firmware has a crappy interface, but feature-wise it's actually quite good, even supporting WDS. So, moral of the story: if you don't need a specific feature within DD-WRT, it might be better to just use the stock firmware.
I know no one else posted about this, but I wanted to post my solution in case anyone else gets into the same issue down the road.
I just picked up my N16 yesterday, flashed to build 16994 without issue. Seems stable over the first 12+ hours.
I returned a DIR-825 for the N16 to see if it would yield better signal and connections speeds and by default it does.
My question of the day; I have only 2x 8dBi (TP-Link TL-ANT2408C) right now. Also have 1x 5dBi off an old wireless PCI card. Would I be messing up the signal/connection by having an oddball antenna? I know its easy enough to try but I thought I'd ask here too. Thanks!
***edit: Just tested it myself, these TP-Link 8bDi antenna seem to not improve a single router. I've tried them on a TP-Link 1043ND (their top model, only a slight increase, not worthy of buying them), a D-Link DIR-825 and now the Asus RT-N16 (made the signal worse on both). I tried the default TX Power of 17 and 20 and nothing made a difference on that front either.
I'm not disappointed in the router, its a definite improvement over the DIR-825 I returned. No point to have dual-band for me anyway, nothing I have takes advantage of it and nothing will in the foreseeable future.
I just wanted to add my two cents here. Anything past build 16454 on my N16 has had lower signal issues in areas in my house I never had issues before, strange signal reporting on the main DDWRT page and clients dropping off the wireless. I went back to 16454 and all is well.
Running on 16994, used 16785 before but had to switch since ovpn was broken on 16785.
40 MHz N-only did not run stable for me on either 16785 or 16994. Initially i got 300 Mbps and could pull at 9 MB/s from my NAS (extra NAS plugged into N16) which was great. After a while (couple of hours I guess) speed dropped down to 11 Mbps (at least that was what Windoze 7 reported). Switched to NG-Mode then, seemed to run more stable, Windoze 7 reporting 144 Mbps. Was able to pull with about 4 MB/s from my NAS, guess that confirms the 144 Mbps. Status page on router is reporting 78 Mbps. Not sure what to trust - Win7 or DDWRT status page?
Will try 16454 soon, hope ovpn works on that and speeds on 40 Mhz stay stable.
Other than that:
Great work guys, amazing what you guys pulled together. Very powerful firmware. Know how hard it is to keep something big like that with all these configurations up and running, used to work in R&D for TITECH GmbH (www.titech.com). Keep up the good work!!!