Asuswrt-Merlin 3.0.0.4.372.30_2

[RMerlin]

Well, in my book, jumping from 2-3ms to 20-30ms... that's 10x slower

It adds 2-5ms, it does not add 20-30ms. So 20ms becomes 25ms.

 

[Igb]

Hi,

As you are posting into the Merlin-Thread:
Which version of .372 firmware have installed? The Merlin one or the one from Asus directly?

With kind regards
Joe

Hi,

Many thanks for your interest, I tested both merlin .372 and Asus .372, same results. Whatever is causing the problem was introduced in Asus first .354 beta release (I stayed in merlin 270.26b until now for that reason). At the moment I am using Asus .372, It is probably a tad more stable, but I cannot confirm that for sure, probably only my impression.

I know is merlin firmware thread, but to be honest I think i wont find anybody with deeper knowledge of this router's firmware than here, my apologies if it is disturbing but this random resets are anoying me like hell, and even more now i am seeing them in a (theoretically) stable release

I should have probably opened a new thread, too late now

 

[silvercloud]

just curiosity. i couldnt find the change log for rtn66u.372.30_3. could you shed a light merlin

 

[janosek]

http://forums.smallnetbuilder.com/showthread.php?t=11851

just curiosity. i couldnt find the change log for rtn66u.372.30_3. could you shed a light merlin

 

[silvercloud]

thanks. i guess i forgot that part.

 

[dominatorstang]

Looks pretty much the same settings as for me, except I don't enable "Client to Client". Also, I would specify the actual algorithm used instead of leaving it on Default, just to be sure that both the client and server use the same one.

Also make sure you don't have any firewall or security suite on your PC blocking traffic from the VPN client. Some security suite might not like the traffic coming from the 10.8.0.0 subnet.

I never tested the Android client, so it could also be a problem. I only use the Win32 client from work.

Thanks for the pointers. Looks like a few small things had changed on my android client software after I had the 100% success on the RT-AC66U. Things are going in the right direction again now.

 

[RMerlin]

Thanks for the pointers. Looks like a few small things had changed on my android client software after I had the 100% success on the RT-AC66U. Things are going in the right direction again now.

Excellent!

Would you mind at some point making a post on how you got it configured both on the router and (especially) the Android phone, for others who might be interested?

 

[geko53]

WIFI-Troubles with new stock FW

Just gave the new ASUS stock firmware (FW_RT_N66U_3004372.trx) a try but reverted to 3.0.0.4.372.30_3 Merlin soon as I had severe troubles with wireless 5 GH performance. Although I started with "clean" NVRAM 5G wireless was oscillating the whole time making it impossible build up a stable connection (with android devices as well as with Intel devices).

When reverting to Merlin's FW everything ran as stable as usuable when using Merlin FW

No idea what ASUS really has implemented with the new "improved" WIFI drivers...

Ciao

 

[RMerlin]

Just gave the new ASUS stock firmware (FW_RT_N66U_3004372.trx) a try but reverted to 3.0.0.4.372.30_3 Merlin soon as I had severe troubles with wireless 5 GH performance. Although I started with "clean" NVRAM 5G wireless was oscillating the whole time making it impossible build up a stable connection (with android devices as well as with Intel devices).

When reverting to Merlin's FW everything ran as stable as usuable when using Merlin FW

No idea what ASUS really has implemented with the new "improved" WIFI drivers...

Ciao

I suspect it was just a copy/paste error since that whole line refers to the RT-AC66U (beamforming).

In any case, Asus should have a new version with a fixed driver out real soon.

 

[geko53]

In any case, Asus should have a new version with a fixed driver out real soon.

I don't feel an urgent demand to use a new stock FW any longer regarding the fact that your builds are working much better than the original builds...

Ciao
Gerald

 

[Milkman]

Was the ASUS cloud vulnerability solved with this last patch???

 

[cmillar6]

Was the ASUS cloud vulnerability solved with this last patch???

yes, it's in the release notes

 

[redpants]

Has anyone gone from 3.0.0.4.270.26 to 3.0.0.4.372.30_2 without reverting?

 

[jerry6]

Found the answer , forget it

 

[ScottW]

Client List Not Working

Based on the error message, it sounds like this function gets called while one of these lists is empty.

Thanks, this gives me a starting point to look into it.

The most common invalid names that I see are names that contain quotes, or non latin characters (i.e. people using cyrillic in device names). This also applies to the DHCP reservation page of the router. I doubt that's what is causing your issue in this case, but you can check that page too if you had manually entered device names there.

I have this same issue -- the client list never populates, and the IE9 console contains this error:
SCRIPT5007: Unable to get property 'length' of undefined or null reference nameresolv.js, line 64 character 17

I never had this problem on 270.26b, and I don't have any devices with hostnames that contain anything other than alphabetic characters and hyphens. I also have quite a few static reservations, and none of them contain any odd characters either.

I tried clearing NVRAM -- no help, client list still "hangs" and won't populate.
I tried deleting all the static reservations -- no help, same problem.

I reverted to 270.26b, and the client list works fine again.

RMerlin - If there is any data or test results I can provide that may help chase down this issue, let me know and I will be happy to help!

 

[VinceV]

Has anyone gone from 3.0.0.4.270.26 to 3.0.0.4.372.30_2 without reverting?

I have.

I actually went from 3.0.0.4.270.26b to 3.0.0.4.372.30_3, but close enough. I'm using an RT-N66U.

 

[RogerSC]

Has anyone gone from 3.0.0.4.270.26 to 3.0.0.4.372.30_2 without reverting?

Yes, been on 372.30_2 for a couple of weeks now, and it has worked very well. Came from 270.26b, which I had to revert to from every version following it until 372.30 came out. Since the wireless driver in 372.30 was reverted to the previous working one from 270.26b because of 5GHz. band problems in firmware releases following 270.26b, those using 372.30 can use the new 3xx features and still be running 5GHz. band at full throughput.

Enjoying using 372.30_2 on my rt-n66u.

 

[Zebodog]

Has anyone gone from 3.0.0.4.270.26 to 3.0.0.4.372.30_2 without reverting?

I'm using 3.0.0.4.372.30.2 having migrated from 3.0.0.4.270.26b

I'm having no issues,and all 5GHz clients are connecting at full throughput and staying connected. The living room is about 30 feet away from the router and down one floor which is where the wife spends most of her time with her iPad. Since upgrading the iPad has remained locked to the 5GHz channel whereas prior releases it would constantly default to the 2.4GHz channel.

While using 270.26b, I increased 5GHz transmission power to 125mw and left 2.4GHz at 100mw. Now on 372.30.2, I've noticed that 5GHz has the stronger signal over the 2.4GHz band at 30 feet and one floor down. Out on the deck which is about 50 feet and one floor down from the router, the 5GHz band still has the stronger signal.

I really like 3.0.0.4.372.30.2

 

[DrTeeth]

@ Zebodog

Both the 270.26b and 3.0.0.4.372.30.2 have the same wireless driver.

 

[cmillar6]

@ Zebodog

Both the 270.26b and 3.0.0.4.372.30.2 have the same wireless driver.

That depends which router, the AC66u had a driver upgrade moving from .270 to .354 The 5Ghz signal has been rock solid ever since.