What's new

Not going to be using Merlin for a while...

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

theirongiant

Regular Contributor
Hi gang,

I have been lurking for a long time (hence my low post count) but have been using Merlin's firmware since I bought my RT-N66U almost a year ago. I have gone back to TomatoUSB after much toil and sweat, because I have reached the almost certain conclusion that while ASUS' hardware is excellent, the software is deeply flawed. There are some bugs in the software that cause wireless hiccups and daily modem reboots, all of which has completely disappeared with TomatoUSB.

Not long after I bought this router, I was experiencing random dropped packets and latency over Wi-Fi, and the cable modem would unexpectedly reboot itself 2-3x a day. I thought the device was defective, so I exchanged it at Fry's. The issues continued, so I started troubleshooting elsewhere: I replaced all my Ethernet cables with Cat5e. I upgraded from a Motorola SB5120 to a Motorola SB6121. I have Charter Cable, so I called them to see if there were issues with my line. Nothing.

We moved to a new apartment nearby (still in a Charter area) and the issues persisted. Then I discovered Merlin's firmware. This was back at ASUS Firmware 2.x (revision 260, IIRC), before the WAN DHCP setting was implemented in later revisions. I still liked the feature set enough to keep using it, but random wireless hiccups and cable modem reboots persisted, according to the modem logs anyway.

Frustrated with the lost IP addresses and having to reboot the modem every month, I sought alternatives and found TomatoUSB. After using it a couple of weeks, I noticed that the wireless was a lot more stable. Unfortunately, the cable modem was still dropping the IP address every few weeks. This was baffling, of course, until I learned of the WAN lease issue that is very specific to Charter and some other ISPs. Merlin implemented the "Normal/Aggressive" option at the time, and I did not know if there was any way to fix this in TomatoUSB, I switched back to Asus/Merlin because of the WAN DHCP issue.

I put up with the wireless hiccups, but I also cheked the modem logs and found that the cable modem was still rebooting several times a day. I called Charter on two separate occasions to check my equipment and the lines, both inside and out, and only found an unnecessary splitter on the outside box (my signals were well within spec, even with the splitter). However, the modem would continue to reboot at random times throughout the day.

Some time later, I discovered numerous posts on the Internet about setting the following options for the udhcpc daemon in TomatoUSB. These options tell the router to try the WAN DHCP query 3 times every 5 seconds, then wait for 310 seconds (5m5s) between these attempts:
Code:
--retries=2 --timeout=5 --tryagain=310
With that, I switched back to TomatoUSB. That was January 16th. The modem hasn't logged a single reboot, and the wireless performance has never been better.

I have seen other threads about random wireless issues with these devices. These are not the work of Merlin (The Magician). I applaud his efforts, and the features he's adding are terrific. ASUS makes a great product, but they still have some work to do on their software.
 
Last edited:
By any chance did you try the 374.38_2-em build? It has a new wireless driver on the N66U, and so far resolved performance issues for the vast majority of users according to the posted feedback.
 
By any chance did you try the 374.38_2-em build? It has a new wireless driver on the N66U, and so far resolved performance issues for the vast majority of users according to the posted feedback.

I was using a 3.0.0.374.36 beta version, and then tried 3.0.0.374.38_1-em which so unusable (router admin page stopped responding shortly after boot, Internet inaccessible) that I had to use recovery flash to go back to the .36 beta.

As for 3.0.0.374.38_2-em, I have had choir rehearsals every day for the last 6 days straight, plus work from 9-6, so no time for computer things. I just know that it has been working 100% since I switched to TomatoUSB last Thursday, and I needed peace of mind for the time being.

Would you mind linking to your post about 38_2-em?
 
Last edited:
By any chance did you try the 374.38_2-em build? It has a new wireless driver on the N66U, and so far resolved performance issues for the vast majority of users according to the posted feedback.


RMerlin,

theirongiant reminded me of an issue (can't recall if I've mentioned it on the forums?) with my RT-N66U and the _2-em build.

The modem, not the router would seem 'stuck' anywhere between 4 to 24 hours and there was no internet service (VDSL line). Rebooting the router would not fix the issue. The modem needed to be rebooted.

Just as I was going to test this further - I noticed that my ISP was indicating trouble with their network (weather related, I'm sure) so I paid it no thought.

The symptoms continued for 2 or 3 days though, but then I checked and the ISP showed no problems for the last 24 hours or so.

This is around the time when I discovered Asus beta v.2239 and started playing with that instead. What had escaped me (till now) was that the modem/internet issues I had disappeared right after I flashed v.2239 beta on the RT-N66U.


I would suggest to theirongiant to properly test the latest beta from Asus - it may give him the stability and the Asus features in one package.
 
I was using a 3.0.0.374.36 beta version, and then tried 3.0.0.374.38_1-em which so unusable (router admin page stopped responding shortly after boot, Internet inaccessible) that I had to use recovery flash to go back to the .36 beta.

As for 3.0.0.374.38_2-em, I have had choir rehearsals every day for the last 6 days straight, plus work from 9-6, so no time for computer things. I just know that it has been working 100% since I switched to TomatoUSB last Thursday, and I needed peace of mind for the time being.

Would you mind linking to your post about 38_2-em?

If you were using the 374_36 version (not the specific SDK5) then yes, wireless issues were to be expected. Those are resolved in 374_38.

Check the dedicated thread here on the forums about 374.38, all details are there.
 
RMerlin,

theirongiant reminded me of an issue (can't recall if I've mentioned it on the forums?) with my RT-N66U and the _2-em build.

The modem, not the router would seem 'stuck' anywhere between 4 to 24 hours and there was no internet service (VDSL line). Rebooting the router would not fix the issue. The modem needed to be rebooted.

The router firmware has no incidence on the modem. It merely routes Ethernet traffic to and from it. Especially if a modem reboot was what would resolve the issue.
 
Thanks RMerlin, I didn't think they were connected; but wanted to report this for completeness.

Must have been the ISP still having issues, and the changing of the firmware simply coincidence.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top