I've been following your thread and work for a little while Kong. Just wanted to say a big thank you (even though I'm not yet using your firmware)!
I've recently purchase an R7000 (cos it offers superior hardware to the AC68u) and am looking at updating to your "K3-23550" firmware instead of my currently installed Netgear beta (V1.0.3.24_1.1.20).
I figured that buying the most powerful hardware, coupled with your excellent firmware, would result in a win-win situation
I've not been terribly impressed with the Netgear firmware (for the 48 hours I've had this router) - occasional high (wifi-N) pings to the router (5-10ms, 100ms) and my HP wifi printer often seems to drop off the w-lan . (The HP never dropped out on my old Billion 7700n).
My main needs for this router are internet gaming (low latency+Qos), p2p (Qos), net surfing and rock solid reliability (not dropping packets/connections).
In search for those features I basically ended up here, and becoming a fan of your work
</long winded thank you note>
In my travels, I noticed the work these guys were doing on 'buffer bloat' and low latency, "CeroWRT"
http://www.bufferbloat.net/projects/cerowrt
Just wondering what your thoughts were in terms of whether your firmware performs/provides a similar thing when it comes to gaming and low latency performance and/or whether anything from that code might be useful/make its way into your work (but only if not already there)?
Joined: 21 Nov 2010 Posts: 278 Location: North America
Posted: Mon Feb 17, 2014 5:12 Post subject:
Setting the DDR memory clock to 933MHz is illegal and results in decreased router performance.
Here's why:
Set the DDR memory clock to 933MHz and reboot:
root@NetR7000RT1:~# nvram set clkfreq=1400,933
root@NetR7000RT1:~# nvram commit && reboot
Excerpt from PuTTY serial console log during boot-up:
CFE for Foxconn Router R7000 version: v1.0.21
Build Date: Wed Aug 7 19:11:17 CST 2013
Init Arena
Init Devs.
Boot up from NAND flash...
Bootcode Boot partition size = 524288(0x80000)
DDR Clock: 400 MHz Info: DDR frequency set from clkfreq=1400,*933* Warning: invalid DDR setting of 933 MHz ignored. DDR frequency will be set to 400 MHz.
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.37.15.1 (r407936)
CPU type 0x0: 1400MHz
Tot mem: 262144 KBytes
Examine CPU performance:
root@NetR7000RT1:~# cat /proc/cpuinfo
model name : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 2786.91 <== CPU0 clk = 1400 MHz, DDR memory clk = 400MHz
Features : swp half thumb fastmult edsp tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc09
CPU revision : 0
model name : ARMv7 Processor rev 0 (v7l)
processor : 1
BogoMIPS : 2786.91 <== CPU1 clk = 1400 MHz, DDR memory clk = 400MHz
Features : swp half thumb fastmult edsp tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc09
CPU revision : 0
Hardware : Northstar Prototype
Revision : 0000
Serial : 0000000000000000
Examine clkfreq and set the DDR memory clock to 800MHz and reboot:
root@NetR7000RT1:~# nvram get clkfreq
1400,933
root@NetR7000RT1:~# nvram set clkfreq=1400,800
root@NetR7000RT1:~# nvram commit && reboot
Excerpt from PuTTY serial console log during boot-up:
CFE for Foxconn Router R7000 version: v1.0.21
Build Date: Wed Aug 7 19:11:17 CST 2013
Init Arena
Init Devs.
Boot up from NAND flash...
Bootcode Boot partition size = 524288(0x80000)
DDR Clock: 800 MHz Info: DDR frequency set from clkfreq=1400,*800*
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.37.15.1 (r407936)
CPU type 0x0: 1400MHz
Tot mem: 262144 KBytes
Examine CPU performance:
root@NetR7000RT1:~# cat /proc/cpuinfo
model name : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 2793.47 <== CPU0 clk = 1400 MHz, DDR memory clk = 800MHz
Features : swp half thumb fastmult edsp tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc09
CPU revision : 0
model name : ARMv7 Processor rev 0 (v7l)
processor : 1
BogoMIPS : 2793.47 <== CPU1 clk = 1400 MHz, DDR memory clk = 800MHz
Features : swp half thumb fastmult edsp tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc09
CPU revision : 0
Hardware : Northstar Prototype
Revision : 0000
Serial : 0000000000000000
DDR memory clock settings greater than 800MHz are ignored and default to 400MHz.
I have 2 routers, r7000 (primary), rt-ac68u (wired AP). The problem is my wifi device don't roam on 5GHz. That is I'll be very near the slave router, but the client (galaxy s4) is still connected to the master router and vice versa. If I disable/reenable wifi on the device it does connect to the closest AP.
Both routers are set to different channels, though I did try same channel with same results. The routers are separated by a number of walls and ~50ft apart.
My guess is that is just not enough distance between the two to hit whatever threshold the s4 wants before seeking a stronger connection.
I'm open to any suggestions.
Thanks!
That can be a problem from S4 itself. I got the same problem on my Samsung Galaxy S3 and it was reported as :http://gs3.wonderhowto.com/how-to/fix-wi-fi-roaming-bug-your-samsung-galaxy-s3-0140840/
I've been following your thread and work for a little while Kong. Just wanted to say a big thank you (even though I'm not yet using your firmware)!
I've recently purchase an R7000 (cos it offers superior hardware to the AC68u) and am looking at updating to your "K3-23550" firmware instead of my currently installed Netgear beta (V1.0.3.24_1.1.20).
I figured that buying the most powerful hardware, coupled with your excellent firmware, would result in a win-win situation
I've not been terribly impressed with the Netgear firmware (for the 48 hours I've had this router) - occasional high (wifi-N) pings to the router (5-10ms, 100ms) and my HP wifi printer often seems to drop off the w-lan . (The HP never dropped out on my old Billion 7700n).
My main needs for this router are internet gaming (low latency+Qos), p2p (Qos), net surfing and rock solid reliability (not dropping packets/connections).
In search for those features I basically ended up here, and becoming a fan of your work
</long winded thank you note>
In my travels, I noticed the work these guys were doing on 'buffer bloat' and low latency, "CeroWRT"
http://www.bufferbloat.net/projects/cerowrt
Just wondering what your thoughts were in terms of whether your firmware performs/provides a similar thing when it comes to gaming and low latency performance and/or whether anything from that code might be useful/make its way into your work (but only if not already there)?
Since we are on K3.10 or newer we already include codel fq_codel
Awesome!
Definitely puts my mind at rest.
I appreciate your prompt response Kong.
I just DLed and installed (what I thought was) the latest firmware. I got it from the MyOpenRouter 'Downloads' section, and (after double checking) it's clearly not the latest version (it is 23430M). My fault for not checking your signature until now.
Is anyone having trouble with the DD-WRT GUI becoming inaccessible after a few (5-10) rapid refreshes/page loads?
If I use the back button on my browser(I know shouldn't) to skip back a few (5-10) screens, the GUI often becomes no longer available. Internet, wifi and LAN all still work, but I have to reboot the R7000 in order to be able to get access via the GUI again.
Is anyone having trouble with the DD-WRT GUI becoming inaccessible after a few (5-10) rapid refreshes/page loads?
If I use the back button on my browser(I know shouldn't) to skip back a few (5-10) screens, the GUI often becomes no longer available. Internet, wifi and LAN all still work, but I have to reboot the R7000 in order to be able to get access via the GUI again.
Perhaps a bug?
On some pages there is a lot of background work like starting stopping services writing nvram etc. . When appyling any changes it is always good to wait a few 5-10s before appyling new changes. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
On some pages there is a lot of background work like starting stopping services writing nvram etc. . When appyling any changes it is always good to wait a few 5-10s before appyling new changes.
Noted. It's happened to me a few times, but I might have just been unlucky with which pages I was on when refreshing. I'll simply be more careful next time .
Edited the following files, changing /dev/usb/lp0 to /dev/lp0:
/jffs/etc/config/p910nd
/jffs/watchprinter
The printer wasn't auto-detected and I had to select the model for drivers to be installed in Windows 7.
Is there a better/easier way to set this up?
---
The next thing I'd like to setup is a nfs server (should I use nfs-kernel-server?) and a tftp server (can I use the already installed dnsmasq or do I need to install tftp-hpa or atftp?)
I would really like to know as well if there is an easier way to do this?? Its almost plug and play in the stock firmware, and honestly, it kind of sucks that you have to play around with a lot of code 2014 to get a printer to work!
Well I got couple question's regarding QoS, and don't know what exactly i should pick between a couple option's within QoS.
1. Packet Scheduler - Should I just use the default selected HTB?
2. Queueing Discipline - Should I use the default SFQ?
Here is my setup, which includes multiple gaming consoles, some torrenting, streaming over samba, and the normal usage of web browsing with multiple device's. I would like to keep gaming at it's best, so i want to prioritize it, keep latency, and such at a minimum. So I would appreciate any suggestions from you guy's who use, and know QoS on DD WRT.
Hi Guys, I'm planning on upgrading from r23550 to r23550-R01. Is it ok to backup my settings, upgrade to the new version with a factory reset, and then restore my settings? I know in general restoring settings from a different firmware versions may cause problems, but are these versions close enough that it is ok?
Hi Guys, I'm planning on upgrading from r23550 to r23550-R01. Is it ok to backup my settings, upgrade to the new version with a factory reset, and then restore my settings? I know in general restoring settings from a different firmware versions may cause problems, but are these versions close enough that it is ok?