By the way, I was very surprised to see that after upgrade to Merlin build from stock ASUS build, all my settings were still there (you know, WiFi/etc)
I strive to maintain 100% backward compatibility with Asus's firmware.
By the way, I was very surprised to see that after upgrade to Merlin build from stock ASUS build, all my settings were still there (you know, WiFi/etc)
3.0.0.4.264.22 was released a few days ago, it's still in a early stage of testing. A user reported problems with the JFFS partition, which led to a bricked router. So i advise you to upgrade to 260.21, it's the most stable until now.
- lfbb
That's strange, maybe some incompatibility with the RT-N53 GPL you used for the last build?The JFFS code has been unchanged since 178.15.
Great thing about Merlin's firmware was that the whole process of (Download firmware->Read Instructions->Flash RT-N66U->configure JFFS & custom scripts) took me less than one hour from scratch, and completely glitch-free... I'm afraid to take up on time-consuming Shibby/Toastman configurations (which seem to be for more experienced users, I'm entry level) as I also have to spend time setting up Apache+Subversion+Trac+Postgres on a Mac (there goes my X-mas holidays).
Hope you all have a wonderful X-mas break!
That's strange, maybe some incompatibility with the RT-N53 GPL you used for the last build?
- lfbb
P.S: I'd like to try enabling the JFFS partition, but I'm scared of doing it!![]()
Just updated from stock. My usb hard drives are showing up on the main page , but I can't seem to get the router to rescan the drives. I turn media server off and back on , tried rebooting , and even telneted in to nvram commit after changing to /mnt. I will reboot without the hds connected and try again.
#no go
You guys won't believe it - now that I was successful in loading Merlin build, I got a little more brave... After hearing you and jsmiddleton suggesting Shibby build for setting up multiple-IP, I downloaded Shibby AIO-64k build firmware for my RT-N66U. I also saw in their tutorial in how to setup multiple static IP - WHOAAA - in less than 10 minutes my RT-N66U was up and running with my block of static IP from AT&T Uverse (I don't recommend that AT&T service but currently I have no other choice in my area, it drops a lot).
Merlin - it was extremely simple so perhaps even your build could do it? (just an idea)... All I had to do was:
1. Download/install Shibby's TomatoUSB firmware ending with AIO-64k for RT-N66U
2. Setup my AT&T router for "IP-PASSTHROUGH", and connect RT-N66U router in Router-behind-router config (Internet <--> ATT Router <--> RT-N66U router <--> LAN)
3. Enable JFFS (it goes through formatting JFFS partition)
4. Then in Shibby build, I had to go to Administration->Scripts->Firewall and enter the following lines for each of my static IP (seems that it automatically builds the script file for you):
/usr/sbin/ip addr add 99.XXX.XXX.105/30 dev vlan1
/usr/sbin/iptables -t nat -I PREROUTING -d 99.XXX.XXX.105 -j DNAT --to-destination 192.168.2.20
/usr/sbin/iptables -t nat -I POSTROUTING 1 -p all -s 192.168.2.20 -j SNAT --to 99.XXX.XXX.105
Where 99.XXX.XXX.105 = one of the static IP addressese from the block of 5 static IP assigned by AT&T, and 192.168.2.20 = LAN IP of my computer to which I wanted the traffic routed. I then repeated above three lines for three more static IP's and left one free (assigned to RT-N66U router so that all other computers can go through that)
After a reboot, it worked like a charm! I haven't tried adding such custom script to your build under /jffs/scripts/nat-start but perhaps someone who wants to experiment could try to see if that would work!
Anyway guys, I'm very happy that I can use my RT-N66U router for multiple static IP from AT&T. Hope this helps others who are looking for a solution too! Thanks to you all for such amazing one-on-one support.![]()
Make sure you don't have any custom firewall rules applied through a script that would disrupt iptables.
Enabling traffic monitoring merely insert one single rule into the FORWARD table.
My firewall is disabled.
Some feedback from a RT-N16 user and 3.0.0.4.264.22.
I upgraded the FW and went to input my ebtable filter and the router responded back with the following:
The kernel doesn't support a certain ebtables extension, consider recompiling your kernel or insmod the extension.
I have since downgraded to 260.21 with no issue.
Regards
Which module were you trying to use?
I downloaded and used the RT-N16_3.0.0.4_264.22.zip from mediafire links that were provided in the first post of this thread.
Regards
We use essential cookies to make this site work, and optional cookies to enhance your experience.