Previous Thread
Hi,
Flashed from r17940.
There is some bug, because I can't upgrade with FF8: it cames with unsuccessful upgrade error.
More: after doing it with IE8, the power led never goes on. I have to do a power cycle several minutes ahead of firmware submit.
Now it's running with the same configs of r17940 without any new unreported issues.
Wiviz isn't working at least since r17940.
It may be a good suggestion to put an option on wireless advanced settings to activate the "interference mode 2", instead inserting commands on startup script (more nvram usage).
Best regards.
New with this release (from the change log) Build r18010:
New:
Wireless core updated to 5.100.138.9 (stabalize signals on 2.4Ghz units)
Add opkg to all builds
Select the correct build for your router (see readme file)
Once you make your selection and know which is "The ONE"
Download from here ( http://www.desipro.de/ddwrt/ ).
Thanks for all your work Kong.
December 17, 2011 7:33 AM
updated: December 17, 2011 7:35 AM
December 17, 2011 7:55 AM
updated: December 17, 2011 7:58 AM
ReDaLeRt said: Hi, Flashed from r17940. There is some bug, because I can't upgrade with FF8: it cames with unsuccessful upgrade error. More: after doing it with IE8, the power led never goes on. I have to do a power cycle several minutes ahead of firmware submit. Now it's running with the same configs of r17940 without any new unreported issues. Wiviz isn't working at least since r17940. It may be a good suggestion to put an option on wireless advanced settings to activate the "interference mode 2", instead inserting commands on startup script (more nvram usage). Best regards.
In read me file:
!!!Attention: Always clear your browser cache before flashing!!!
December 17, 2011 8:19 AM
updated: December 17, 2011 8:19 AM
Hi,
I did that through CCleaner. Isn't enought?
Best regards,
December 17, 2011 8:23 AM
updated: December 17, 2011 8:24 AM
Hi,
OPKG is broken?
# opkg update
Collected errors:
* opkg_conf_load: Could not create lock file /jffs/lib/opkg/lock: No such file or directory.
Kingkong version.
Best regards,
Member
- member since: 02/28/2010
- rank: 5 of 28504
- 1 articles authored
- 27 forum threads started
- 1023 comments
December 17, 2011 10:04 AM
Hi ReDaLeRt,
just run:
mkdir -p /jffs/lib/opkg
I normally do this when automounting, so I guess you don't have a drive with jffs attached. I also flashed (via network cable) from r17940 with FF8 and didn't have a problem.
December 17, 2011 10:14 AM
Hi,
Thanks Kong. Why it is necessary to run JFFS for OPKG? Can't it be on /opt drive?
Best regards,
December 17, 2011 4:29 PM
I have loaded DD-WRT v24-sp2 (12/16/11) vpnkong - build 18010M (nv60k) on a spare E3000 to update a family members vpnkong 17940 with low wireless speeds. This unit is set-up with QoS, SSH & Privoxy.
The issue I see so far, is that QoS is not throttling to the Uplink/Downlink (kbps) settings. QoS port is WAN and Packet Scheduler is HTB.
Does anyone else have this problem with vpnkong build 18010?
TIA!
December 18, 2011 7:50 AM
AWESOME.... Have constant signal second day after reboot. Kong you da man...
Will begin to test USB drive mounting but the reason I got the RT-16N (Wireless) is finally working on newer builds of dd-wrt
December 18, 2011 2:10 PM
Hi,
I flashed the new build(kingkong) to my ASUS RT-N16. PPoE, OpenVPN, DLNA, Samba and Wireless work. The Wireless connection to my Wireless Repeater Bridge works good as well. After 24 h no downgrade of wireless speed (so far) !
Thanks Kong !
December 18, 2011 2:16 PM
updated: December 18, 2011 2:17 PM
Hi,
After almost 36 hours of uptime:
I'm going to flash 15508M once again. No more upgrades on next months. God-damn it!
Thanks.
December 18, 2011 11:23 PM
Ok guys... this is kind of crappy.
After running stable for two days, I just took a look and my router is sitting at 6.5Mps.
Don't know what the heck is going on but it is really starting to make me feel like RedAlert feels. I have tolerance for the new driver testing and debugging but it comes a point where you just have to step back and let Broadcom make their driver work with the latest kernel in a way which at least resembles the old drivers, although the last time I check "new" drivers should bring "improvement" after the initial and expected tweaking to stabilize them.
I don't know if there is a feedback loop back to Broadcom on the crappy performance of these new drivers. I certainly hope there is one through BS/Eko or someone else.
Anyhow.. that was my frustrated rant. BTW - Did I tell you guys that this pisses me off? :)
December 19, 2011 1:41 AM
@zoomlink
Here is something Toastman wrote about wireless, reed if you want !
http://www.linksysinfo.org/index.php?threads/toastman-releases-up-to-1-28-749...
December 19, 2011 9:17 AM
updated: December 19, 2011 9:21 AM
@kt_haddock
Thanks for the link. I get what Toastman is talking about, but still cannot understand how previous builds like 15508 and 15962 give you rock solid wireless performance and newer builds have terrible performance.
On the other hand, I hate to loose all the good work that has been put into automount, having opkg, etc.
Kong: is there a way you can release your next build as you did before with OLD DRIVERS and NEW DRIVERS for those that still want them?
December 19, 2011 9:40 AM
Another thought....
How about rebooting the interface every 24hrs with a cron job like this?
30 3 * * * root /opt/etc/init.d/wlrefresh.sh
code for: wlrefresh.sh
wl -i eth1 down
sleep 2
wl -i eth1 up
sleep 2
wl -i eth1 interference 2
December 19, 2011 10:25 AM
updated: December 19, 2011 11:15 AM
zoomlink said: @kt_haddock Thanks for the link. I get what Toastman is talking about, but still cannot understand how previous builds like 15508 and 15962 give you rock solid wireless performance and newer builds have terrible performance. On the other hand, I hate to loose all the good work that has been put into automount, having opkg, etc. Kong: is there a way you can release your next build as you did before with OLD DRIVERS and NEW DRIVERS for those that still want them?
I have to mention, I have been using Toastmans build RT-N for months with "latest" 5.100.138.9 wifi driver with one Atheros, Ralink, Android and Htc with no issue.
Working as is shuould on my RT-N16 router.
December 19, 2011 1:03 PM
updated: December 19, 2011 1:08 PM
zoomlink said: Another thought.... How about rebooting the interface every 24hrs with a cron job like this? 30 3 * * * root /opt/etc/init.d/wlrefresh.sh code for: wlrefresh.sh wl -i eth1 down sleep 2 wl -i eth1 up sleep 2 wl -i eth1 interference 2
This is a good idea but non-sense.
In the case of routers or any other IT system you need 99.9999% of uptime. Rebooting to overcome bigger system issues is not the solution.
Like my people say: "Penso eu de que..." ;-)
Another thing:
Why do we apply "wl intereference 2", when the majoraty of intereference on 2.4GHz band is from devices sharing this same spectrum? Microwares, cordless phones, bluetooth, just-name-it... Makes more sense to apply "wl intereference 1" or any other fitting better our needs.
Until the end of the year I intent to have an Ubiquiti AirView2-EXT to make some tests both on RT-N16 wireless performance and interference nearby.
Best regards,
December 19, 2011 2:12 PM
Hey Red... to finish what your people say... "Penso eu de que e uma bosta"
December 19, 2011 2:22 PM
zoomlink said: Hey Red... to finish what your people say... "Penso eu de que e uma bosta"
lol I don't know if you speak portuguese, but there is a diference between "e" and "é". "Esclarece-nos." :-)
Best regards,
December 19, 2011 2:54 PM
updated: December 19, 2011 2:56 PM
Mesmo asím, penso que ainda é uma grande e crocante bosta! lol Esclarecido? Falo um poquinho sim. :) Anyway, just a little fun with our Portuguese.
P.S. I don't get along well with the text editor on this forum.
December 19, 2011 2:55 PM
updated: December 19, 2011 2:58 PM
Ok figured out to use the advanced editor to fix the accents.
Member
- member since: 02/28/2010
- rank: 5 of 28504
- 1 articles authored
- 27 forum threads started
- 1023 comments
December 20, 2011 6:46 AM
Nope the 3800 has an Atheros chipset and I don't have any Atheros yet.
The 3800 has wonderful specs and you can use a uptodate kernel with oss drivers, which allows fixing bugs like you see in the broadcom drivers.
My wireless connection at home is still running perfectly, so I'm still waiting for the signals to drop:-) Once they drop I'll switch back to an older driver for the single radio units. Probably using even an older wireless driver pre 16000.
But to be honest, I'm sick of these broadcom units. The new routers require new drivers and the new drivers don't work well with old units.
December 20, 2011 8:43 AM
@Kong
Can you share what your setup is? Also what kind of clients do you have?
I have an Intel client, an Atheros client, a samsung android, an LG android and two Nook colors.
When I have only the droid phones connected, the router reports between 52-58.5 Mbps.
When I have only the Nooks connected, router reports 72 Mbps
When I have the Nooks and the droid phones connected, router reports 39 - 54 Mbps
When I have the Nooks, the droid phones and my laptops connected, router reports 216 Mbps.
Keep in mind this is with 8 hrs up-time since the last reboot.
My last drop to 6.5 Mbps occurred after about 36 hours of up-time.
Add Your Reply
Sponsored Links
Copyright © 2012
Capable Networks LLC.. All Rights Reserved.
RSS |
Privacy Policy |
Advertise With Us |
Terms of Use |
About Us |
Contact Us |
Site Map
Our Capable Community Network:
DVR playground |
Explore3DTV |
MediaSmart Home |
MotoDash |
My Open Router |
Pogoplugged |
DijitCommunity |
Robo Community |
Sansa Community |
TechLore |
TiVo Community |
TouchSmartDevZone
MyOpenRouter.com is not affiliated with NETGEAR®. NETGEAR is a registered trademark of NETGEAR, Inc. in the United States and/or other countries. Other brand names mentioned herein are for identification purposes only and may be trademarks of their respective holder(s). © 2011 NETGEAR, Inc. All rights reserved.
Here is my initial feedback:
Router:
ASUS RT-N16 with 2 USB external drives (First 40G 2.5, Second 2TB 3.5)
Firmware flash:
Uneventful - did a reset from the GUI, my OTRW autoconfigure script kicked in as expected, all my OTRW security scripts are running as expected.
Automount is working as expected based on UUID based mount points.
Wireless Stability:
After settling down from all the FW upgrade activity, the signal was steady but still choppy on the inSSIDer graph. I checked to see the Interference setting and WLAN Interference was off. So I went ahead and did `wl -i eth1 interference 2`. After that, the graph shows a slight improvement in RSSI and a VERY nice almost flat signal line on the graph.
My WLAN config:
Type: AP / Mode: Mixed / Channel: Auto, 40Mhz, lower / Ack:2000, No SSID bcast. / WiFi Security: WPA2 Personal-AES Encryption / TxPWR: 20 dBM / Beacon: 101.
General Performance:
SAMBA - Working stable as expected, did a 2GB Video transfer from my Laptop to the Drive on the router and the transfer speed fluctuated between 6MB/s and 8MB/s - I'm happy with that. The only known dislike here is that CPU utilization goes to 100% while the big transfer is in progress.
MiniDLNA - Hoggs up CPU and takes it to 100% when it is doing its refresh of the media files.
MyPage - All pages up and running, some, like the Live Traffic and BW Monitor take the CPU over the edge for a couple of minutes and then show up and work.
Concerns from limited testing time:
WiViz - Seems to not be working still, but I may just have to give it more time.