Switched from Merlin's latest to latest Asus, stopped issues...

[coffee_boxer]

Hi Merlin

I wanted to say thank you for your build - I ran it on my NT66U for about 8 months and donated a few months ago.

Recently [edit: last 5 weeks] I was having issue where overnight my router would crap out, requiring a reboot, or things would slow to a crawl and I'd have to reboot. I recently switched *back* to the newest firmware (which appears to be newer than yours) and the issues have stopped. Can you speak to why that may be, and if I should try again with a newer one?

The other issue that complicated for me was whether I could set up a guest network with limited bandwidth; that doesn't seem possible with your firmware but I thought the QoS on the normal one could do it. I'm confused about that one too.

Thanks again for the firmware and taking the time to read.

 

[MarkyPancake]

The other issue that complicated for me was whether I could set up a guest network with limited bandwidth; that doesn't seem possible with your firmware but I thought the QoS on the normal one could do it. I'm confused about that one too.

From what I've read in various threads, I don't think you can limit bandwidth on the guest networks, because neither Asus' nor Merlin's firmware has this functionality. It's either all, QoS enabled, or nothing, QoS disabled.

 

[rlcronin]

If there was a factory reset (or similar) involved when you reverted to stock, perhaps that cleared up whatever the issue was (i.e. it was a side effect of switching firmware, not something related to the firmware per se)?
--
bc

 

[coffee_boxer]

I had no Factory Reset (it kept all settings, SSIDs, etc). I simply navigated to the Upgrade page (from within Merlin FW) and selected the TRX I downloaded from Asus.

 

[Builder71]

I had no Factory Reset (it kept all settings, SSIDs, etc). I simply navigated to the Upgrade page (from within Merlin FW) and selected the TRX I downloaded from Asus.

Do as you like, but if you spend some time reading around here, you know it's mandatory to do a factory reset after the flash.
Especially if you switch Asus <-> RMerlin.

 

[coffee_boxer]

Do as you like, but if you spend some time reading around here, you know it's mandatory to do a factory reset after the flash.
Especially if you switch Asus <-> RMerlin.

Huh, I did not think of that to be honest. And then reset everything, huh?

 

[RMerlin]

With the RT-N66U, a factory default reset after flashing is mandatory, since the driver I was using in recent versions is different from Asus's.

The next release will see the RT-N66U return to the same driver version as used by Asus since 376_1071.

 

[coffee_boxer]

With the RT-N66U, a factory default reset after flashing is mandatory, since the driver I was using in recent versions is different from Asus's.

The next release will see the RT-N66U return to the same driver version as used by Asus since 376_1071.

Thanks Merlin - so at this point when things are "just working", should the best practical path be to wait until you release your next, then flash it (your version), then factory reset?

 

[KevTech]

I erase nvram every time I do an upgrade/downgrade of firmware then re-enter all options manually.

Some options can be saved and safely re-entered through nano or putty (example is dhcp_staticlist).

You have to remember that anytime there is a new version of firmware be it stock or Merlin there has been something changed from what you are running now. If there was nothing changed there would not be a new firmware. If the change is great enough your current config can/will clash with the changes.

Best to clear the nvram (reset to defaults).

Uploading a saved config after a firmware upgrade/downgrade can also get you into conflicts.

 

[MarkyPancake]

The next release will see the RT-N66U return to the same driver version as used by Asus since 376_1071.

I've just moved from Merlin 374.43 to Asus 3.0.0.4.376_1071 on my RT-N66U, where the Tx power adjustment is now a percentage, and the wireless range is awful compared to Merlin's build.

One room away from the router now sees my phone's 5 GHz Wi-Fi signal strength at one bar, whereas on Merlin it was three, and 2.4 GHz is now at one/two bars, whereas it was full bars before.

There were rooms in the house where I struggled to pick up the 5 GHz signal and the 2.4 GHz was weak with Merlin's build, I now reckon I won't be able to pick up either in these locations.

Since Asus moved away from the SDK5 driver, the wireless performance seems to have gotten worse with each release turning a great router into a not as useful router. Despite all the security updates since, I am seriously considering rolling back to the last SDK5 firmware.

 

[RMerlin]

Thanks Merlin - so at this point when things are "just working", should the best practical path be to wait until you release your next, then flash it (your version), then factory reset?

Up to you. Depends on how important the features unique to my firmware are for you.

 

[Deleted member 27741]

With the RT-N66U, a factory default reset after flashing is mandatory, since the driver I was using in recent versions is different from Asus's.

The next release will see the RT-N66U return to the same driver version as used by Asus since 376_1071.

I realize this question is obtuse- but what is the difference between the driver on the current firmware (43) and the driver that will be on the next firmware?

 

[RMerlin]

Newer. Beyond that I don't know since it's closed source.

Sent from my Nexus 4 using Tapatalk

 

[jim769]

Newer. Beyond that I don't know since it's closed source.

Sent from my Nexus 4 using Tapatalk

If the new driver has less signal then your EM driver you have been using for the N66 there will be a lot of unhappy N66 owners.

 

[KevTech]

I ended up having to go back to 3.0.0.4.374.35_4-sdk5 to solve disconnect issues on the 5GHZ band.

My TV has a Panasonic DY-WL10 LAN adapter which has a Broadcom BCM4323 chipset.

The Netgear wnda3100v2 has the same chipset in it.

On the sdk6 driver the LAN adapter will sometimes not even see the router and when it does the RSSI will be around -60.

With the sdk5 driver I never have disconnects and the RSSI is always around -40 or lower.

Took me a few firmware versions to finally figure out the LAN adapter does not like the sdk6 driver which is strange since both the adapter and router chipset are broadcom.

 

[RMerlin]

If the new driver has less signal then your EM driver you have been using for the N66 there will be a lot of unhappy N66 owners.

I recently discovered that the EM driver hasn't been included in the last couple of firmware releases. It never got properly committed to Github, so at some point in the past few months it got overwritten by an older, regular RT-N66U driver. That would explain why some people reported a range drop in recent releases.

So since it never got saved to Github, it means I no longer have a copy that driver, and I can't get it from the original provider either.

 

[jlake]

I ended up having to go back to 3.0.0.4.374.35_4-sdk5 to solve disconnect issues on the 5GHZ band.

My TV has a Panasonic DY-WL10 LAN adapter which has a Broadcom BCM4323 chipset.

The Netgear wnda3100v2 has the same chipset in it.

On the sdk6 driver the LAN adapter will sometimes not even see the router and when it does the RSSI will be around -60.

With the sdk5 driver I never have disconnects and the RSSI is always around -40 or lower.

Took me a few firmware versions to finally figure out the LAN adapter does not like the sdk6 driver which is strange since both the adapter and router chipset are broadcom.

Here's a brief synopsis of the recent history of the RT-N66U wireless driver. Maybe that will help. It appears that Merlin's firmware has been using the old Broadcom sdk6 driver which had reduced range and possibly other issues.


Pre-march 2013: everyone is using sdk5 driver. Outstanding range. Probably has the best range of any consumer router. Most reviews rave about the range.

March 2013: ASUS releases beta firmware with new sdk and updated sdk 5 driver. 5.1 The driver has compatibility problems with numerous wireless adapters on 5ghz including InteL, Broadcom, Ralink, etc.

July 2013: netgear sues asus (search forum for article and reason)

August 2013: ASUS releases SDK6 for N66U (in other words, they basically slapped the firmware for the AC66U on the N66U) 2.4 ghz range was terrible. 5 ghz range was not as good.

January 2014: ASUS updates firmware and driver. Range is pretty good, but not as good as SDK5. Range is similar to other vendors.

January 2014: while under no obligation, ASUS gives Merlin a special driver that is in Engineering Mode. Excellent range that is similiar to sdk5 driver. The driver comes with a few quirks that can easily be fixed with workarounds. The EM driver appears to working well for most people. If ASUS or somebody starts tweaking it, it could open up a can of worms.

July 2014: The EM driver wasn't committed properly to Github and is lost. According to Merlin, the ASUS/Broadcom sdk6 wireless driver from circa 12/2013 was used in the most recent Merlin firmware releases (instead of EM), although I don't remember too many reported problems at the time of release with that sdk6 driver (other than reduced range). I can confirm that driver is problematic with certain Atheros wireless cards @40 MHz on 5ghz and there have been an increased number of reported issues with various adapters.

 

[RMerlin]

July 2014: The EM driver wasn't committed properly to Github and is lost. It appears that the March of 2013 SDK 5.1 wireless driver was used in the most recent Merlin firmware releases as numerous people reported drops and reduced range. SDK 5.1 was plagued by incompatibility on 5 ghz with some Atheros, Intel, Ralink, and Broadcom wireless adapters and this driver's incompatibility trend continues in Merlin .43 et al.

Actually, the driver that has been used in these recent builds is SDK6, from the December release from Asus.

 

[jlake]

Actually, the driver that has been used in these recent builds is SDK6, from the December release from Asus.

Ok thanks. I'll edit my post. I've been using my new windows 8.1 computer with builtin Atheros 2x2 wireless card with latest driver......so I was guessing based on observed adverse behavior.

 

[4Leaf]

Actually, the driver that has been used in these recent builds is SDK6, from the December release from Asus.

So which of ur builds is the last firmware that you know for sure has the em driver? the 374.39-em build in experimental folder?

Please find it!

...or put your wand to work and re-create the driver with your router guru magic!