Here is a thought. Read the stickies and announcements at the top of this forum. Look for info on the router database. _________________ I am far from a guru, I'm barely a novice.
Here is a thought. Read the stickies and announcements at the top of this forum. Look for info on the router database.
Do you mean the four announcements at the top from 2009?
Yes, I did have a look at those quickly before posting - however, the only place I see the router database mentioned is in the "It's complicated" post from Murrkf, where he says the builds recommended in the router database are wrong...
However, this was from 2009, so I wasn't sure if this was still true.
Is this the announcement you're referring to?
Do you mean that the router database at www.dd-wrt.com is completely wrong? That seems a bit...counterintuitive.
Look, I'm not asking to hand hold me every step, but a simple, "Oh yes, the router database is currently broken", or "Oh, you should go to this URL" would be very helpful...
That smallnetbuilder's post is the one I applied several times also. But if I don't need to do that anymore would be good. Messing with CFE is not very safe xD.
Anyway k3 builds are still experimental so I keep on patching CFE until it's not so experimental.
The latest cfe update from smallnetbuilder is simple. You telnet in, copy and paste what he has on there and it does it or you. It's automated. Not like it was the first time.
It literally takes a few minutes.
You only need to do it once. That's it.
1. Download and unpack update script
Get access to the RT-N66U console via Telnet/SSH/Serial and type:
Quote:
# wget http://files.ryzhov-al.ru/Routers/asus-rt-n66u-cfe-1.0.1.3/cfe_n66u-1.0.1.3-4.tgz
# tar -xzf ./cfe_n66u-1.0.1.3-4.tgz
2a. Update current CFE
If you did not update before, then type:
Quote:
# ./cfe_update.sh /dev/mtd0ro
and watch the progress of the update. The script will ask your final decision before update. Please, proceed if only two differencies will shown between old and new versions of CFE:
Quote:
--- nvram_orig.txt 2012-12-04 13:49:51.000000000 +0400
+++ nvram_updated.txt 2012-12-04 13:49:51.000000000 +0400
@@ -1 +1 @@
-bl_version=1.0.1.2
+bl_version=1.0.1.3
@@ -16,0 +17 @@
+odmpid=ASUS _________________ I am far from a guru, I'm barely a novice.
Not sure if you are still having issues, but i had similar problem of the page being blank. I think this is just an oversite/error on the webpage when all the post-heartbleed stuff went up, cause it WAS there before that. However, I have found the relevant files on the FTP server under this link, ftp://ftp.dd-wrt.com/betas/2014/05-27-2014-r24160/broadcom_K3X/
U can see it seems they are just in the general broadcom_k3x/ folder.
I had tried to do this update with the CFE issue on an earlier version of the N66u (mine is R, cause i bought it best buy, but the firmware actually is U) It failed/bricked that was about 18 months ago. I was able to get bestbuy to just replace it. That router was put in place at co-working space using stock firmware with no issues.
In December 2013, I bought a new RT-N66U (R again from Best). This has the most recent CFE and no cumbersome process invovled at all. I just flashed the .trx, rebooted flashed the bin. no problems at all. I have since flashed shimby tomatoUSB, because dd-wrt, didnt support new requirements on OPENVPN client to my VPN provider.
This all post-heartbleed, several vpn providers made updates and my vpn (airvpn.org) made significant changes to the encryption system required to routers to connect.
Post-Heartblood Merlin broke openwpn client completly and no ETA on a fix. I used DD-WRT which had issues as well. shibbys worked great and i have been very happy since.
