Asuswrt-Merlin 374.43 is out

[diyguy]

will I need to do a clean factory reset from 39_0-em ?

Is the procedure

reset
reboot
upgrade
reboot

 

[thinklad]

Such a drastic drop would indicate that HW acceleration is currently disabled. Check the Tools -> Sysinfo page to determine which functionality has forced it to be disabled.

Just checked, and HW acceleration is still shown as 'Enabled'.

 

[Jettubby]

Installed .43 over a clean install of .41 (BTW: .42 was horrible for some reason and went back to a fresh install of .41) on my N66U. .43 working stupendously so far. Thanks Merlin!

 

[DrTeeth]

will I need to do a clean factory reset from 39_0-em ?

IIRC, no.

Is the procedure

reset
reboot
upgrade
reboot

No. It is upgrade, reset, reboot.

 

[RMerlin]

Just checked, and HW acceleration is still shown as 'Enabled'.

I have no experience with FTTH setups, sorry. Only thing I could think of would be to do a reset of your device standing in front of the router in case that, like cable modems, these might need to be reset when switching router/computers on its LAN interface.

Also make sure QoS isn't enabled, just in case.

 

[test011]

After upgrading from .42, Media Server Path setting had been wiped out, I had to reconfigure it. (upgraded with no reset)

And consistent with previous versions, if set ON, 'iTunes Server' (mt-daapd) is started with -m option, disabling its built-in mDNS function. Since Asuswrt-merlin's separate mDNS daemon does not start automatically for unknown reason, "iTunes Server" does not work out of box. This has been commented before. (A simple workaround is to install entware version of mt-daapd(firefly) and start it without -m option. Probably nobody is using iTunes Server(=mt-dappd=firefly) function though. But it's there and it's not working, so I report it anyway.)

AC66U

 

[matthew_eli]

Hi Merlin,

firstly I checked and 43 fw version did the trick with the traffic manager in PPOE connection scenario for RT-AC68U; BTW I've to report a strange behaviour for 24H graph: if I try to access it with my laptop inside the LAN, I only saw 1 hour time period in the graph; instead, if I try to access it from WAN, I see the graph as it is supposed to be, rather displaying all past 24H.

What could it be?

I reply to myself: I tried also checking the traffic manager by my PC on LAN (wired) and it shows the 24H graph normally. Could the issue be related to the monitor resolution (my laptop has a 1366x758, my PC on LAN 1920x1080 and also my PC on WAN), or could it be related to wireless/wired connection?

For further tests, tomorrow I'll try to connect my laptop on LAN and I'll see what happen

 

[thinklad]

I have no experience with FTTH setups, sorry. Only thing I could think of would be to do a reset of your device standing in front of the router in case that, like cable modems, these might need to be reset when switching router/computers on its LAN interface.

Also make sure QoS isn't enabled, just in case.

I'm still getting the same results.
Is it safe for me to install the latest stock Asus release to see if there are any differences?

 

[RMerlin]

After upgrading from .42, Media Server Path setting had been wiped out, I had to reconfigure it. (upgraded with no reset)

Asus recently redesigned the Media Server page, and changed the way the database location was handled. They were making further changes with every recent firmware releases, so rather than having to constantly re-implement my code to accommodate their changes, I decided for now to remove the path location field, and let Asus stabilize that page. Once it stops changing, I will take a look at possibly re-implementing the path location field.

For now, Asus's new logic is used - the router will automatically use the disk that has the most space available to put its database, unless it can find one that already exists.

 

[RMerlin]

And consistent with previous versions, if set ON, 'iTunes Server' (mt-daapd) is started with -m option, disabling its built-in mDNS function. Since Asuswrt-merlin's separate mDNS daemon does not start automatically for unknown reason, "iTunes Server" does not work out of box. This has been commented before. (A simple workaround is to install entware version of mt-daapd(firefly) and start it without -m option. Probably nobody is using iTunes Server(=mt-dappd=firefly) function though. But it's there and it's not working, so I report it anyway.)

This is something I will probably look at eventually, but it's not a high priority for now since mt-daapd is a pretty antique piece of code (I'm surprised it still works with recent iTunes releases), and people will get more reliable results by using the more open DLNA protocol.

I suspect things might have broke around the time Asus added Time Machine support to the ARM devices, breaking Bonjour/mDNS support for MIPS devices along the way.

 

[RMerlin]

I reply to myself: I tried also checking the traffic manager by my PC on LAN (wired) and it shows the 24H graph normally. Could the issue be related to the monitor resolution (my laptop has a 1366x758, my PC on LAN 1920x1080 and also my PC on WAN), or could it be related to wireless/wired connection?

For further tests, tomorrow I'll try to connect my laptop on LAN and I'll see what happen

It could be a browser issue too. Check if there's any Javascript error if you do reproduce the display issue.

 

[RMerlin]

I'm still getting the same results.
Is it safe for me to install the latest stock Asus release to see if there are any differences?

Should be fine to test. I recommend you do a backup of your settings first, so if you switch back to my firmware, you can reapply that backup. There's a few settings with stock firmware that can conflict with mine, such as the way Asus encodes OpenVPN key/certs.

 

[4Leaf]

Just realized that my router is a b1 version but its a rt-n66r. thats very confusing. Becuz of the way asus has these utilities listed

 

[4Leaf]

Does this mean i should have been installing the asus stock firmware for the b1 instead of the ones that are under rt-n66r

 

[mtlam]

Does this mean i should have been installing the asus stock firmware for the b1 instead of the ones that are under rt-n66r

There should be no difference between the two at all.

 

[thinklad]

Should be fine to test. I recommend you do a backup of your settings first, so if you switch back to my firmware, you can reapply that backup. There's a few settings with stock firmware that can conflict with mine, such as the way Asus encodes OpenVPN key/certs.

Tested with the latest stock Asus FW, no visible change (except perhaps a slight improvement on the UL, but hard to say if this is linked to the FW or to the different time of the test). Hmmm.

 

[matthew_eli]

It could be a browser issue too. Check if there's any Javascript error if you do reproduce the display issue.

It's definetely a browser issue: I tried with IE and the graph is shown correctly, insted with Firefox the problem persists, at least on my laptop. My PC and my WAN PC show the 24H graph normally, both from Firefox and IE

 

[4Leaf]

...Just kind throwing this one out there.

I know most routers have an option to enable and disable wmm.
Why is the only option on to enable or disable wmm and apsd together.
I get that its usually an add on.

I guess I'm trying ask... is wmm still enabled with wmm apsd option disabled

...and since dtim is for devices using power save. Does dtim interval still matter with wmm apsd disabled?

 

[4Leaf]

Also, is ack suppression only effective in use with wmm apsd enabled or does it work well without that being enabled with it at the same time.

and what is a good situation to need to use ack suppression?

Like for online gaming maybe?

 

[Alfsu]

.43 - three days without a hitch on AC66R

Wanted to thank Merlin once again for his invaluable work... my hat off to you!

My report:
Updated my RT-AC66R to 374.43 dirty flash over .42, and its been working for the last 3 days without a hitch (Dirty flashing since .38).
Running VPN client to StrongVPN, with custom selective routing script and selective DNS (DNS Filtering), solid connection with 128 bit encrypt; all thanks to this highly supporting community.