What's new

Asuswrt-Merlin 3.0.0.4.354.27 Beta 1

  • 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!

Hi,

In my case things work well, but System Log / DHCP leases is empty.

Anyone else have the same phenomenon?

With kind regards
Joe :cool:

I had a similar experience to this one time, and clearing my browser's cache fixed it (Chrome). You might try that. If you already have, just ignore this *smile*.
 
Updated (270.25b -> 354.27 Beta 1) and did the Factory reset.
Re-entered all my settings from scratch.

Seems fine so far.
Only wireless throughput seems a bit slower on both bands.
I'll do some more testing on this.

Thx!
 
I have RT-N16 router
270.26b version works great, but newest beta 354.27 wont even boot. Cant connect via lan or wifi, only 2 leds enabled(1 PC and Power led)
No response.

Reverted back to 270 via recovery utility, but I hope u will find a way to make it work on Asus RT-N16
Anyone else can confirm that it doesn't boot on their RT-N16? Could be a compatibility issue with the RT-N16, I don't think Asus has released a 354 build for the RT-N16.
Hi,

I have to confirm the problem: Merlin_RT-N16_3.0.0.4_354.27-BETA1 bricks the RT-N16 router!
  1. Loaded it over the web interface (coming form the orginal ASUS .354 version for the RT-N16) and it bricked the router.
  2. Using the Firmware Restoration tool (with router in recovery mode) had the same result.

I had to go back to the ASUS .354 version (via Firmware Restoration tool) to bring the router back to life!

Something major is wrong with the Merlin build for the RT-N16... :confused:

With kind regards
Joe :cool:
 
Last edited:
Hi, RMerlin!
On your 27 beta I have same issue with link rate as on official beta .354...
Maximum link rate on 5Ghz is 108 mbps only and real upload speed is ~50 mbps.
But with the same settings on router and client on previous FW i got 300 mbps link rate and real upload speed ~75-80 mbps.
With the same settings on 2,4GHz band a get 300 mbps link rate on both FW (26b and 27 beta).

P.S. I`m alone on 5Ghz band with no neighbour wi-fi AP, except my N66 router :)
I cleared nvram, router was reseted to factory dafaults, channel was set manually to 36, 40, 44, 50 with no link rate and upload speed changes.
Settings wasn`t changed on client between upgrading FW on router.
Client is Broadcom 43224AGN 802.11a/b/g/n 2x2 Wi-Fi adapter. Driver version on client is 5.100.82.143

its on 27 beta
and its on 26b

I can confirm this observation. It's 150MBit on 5Ghz and 300Mbit on 2.4Ghz when it should be 300Mbit on both. Only difference is that I have a Intel Centrino 6300 in my laptop.
I guess it hasn't been seen much so far because a lot of laptops and wifi sticks only come with single link support.
 
Merlin
I tried the command and recieved an unknown host error. I also have tried several different time servers with the same results.


Code:
ntpclient -s -h time.nrc.ca

Code:
setup_receive:: bind...
time.nrc.ca: Unknown host

The is the message in the sys log if I try setting the time from the system page
Code:
Jan  1 01:35:34 rc_service: httpd 483:notify_rc restart_time;restart_httpd;restart_upnp


Thanks for all your work.
Steve

Try running this command over telnet/ssh or the Run Cmd page:

Code:
ntpclient -s -h time.nrc.ca

If it works, try creating a services-start script with this:

Code:
#!/bin/sh
sleep 30
ntpclient -s -h time.nrc.ca

That should set it automatically at boot time. There is a 30 seconds delay just to ensure the router has time to get a working connection upstream first - you might be able to reduce that value if it's an issue for you.
 
Last edited:
I'm generally finding this release is good, but Daylight Savings Time is broken. I think this is an Asus bug.

I'm in GMT, and during GMT, the system clock is one hour fast. I switched to manual setup, and got the correct time during GMT.

However, British Summer Time has just started, and instead of the clock going forwards one hour, it went back an hour (making it two hours wrong). I had to enable automatic DST and now it's the correct time under BST.

So it seems under automatic settings you only get BST regardless of the BST/GMT staus, and under manual settings, you get the correct time under GMT, and two hours slow under BST.

It would be nice if a straightforward thing like timezones worked correctly.
 
Last edited:
Flash my RT-N66 yesterday..

Everything fine today. Speeds seem a tad quicker but hard to tell really...probably got a dozen devices hanging off it now on 2.4 and 5Ghz.

Xbox happier now.

For those that might want to know:

1. Unzipped firmware update
2. Uploaded .trx file via web interface
3. On reboot I restored to factory defaults
4. Spent 10 minutes setting up again.


BTW MS & RALink[Mediatek] Linked fluffed up a Windows drivers update which turns off 5Ghz on RT2860 based wifi adapters (mines a Linksys WMP600N). Had to restore a driver from last year to get 5Ghz running.


RMerlin, thank you very much for doing this.

~Steph
 
Last edited:
If I apply this firmware update as follows, will it be the same as resetting to factory defaults without having to manually re-enter my settings?

RT-N66U
1. Boot router
2. Update firmware
3. Check that settings were maintained
4. Save settings/config via Administration->Restore/Save/Upload
5. Reset to factory
6. Boot router
7. Restore settings saved in step 4

Or, do I have no choice but to manually re-enter everything? Fine if so, but I have a lot of ports forwarded and a few reserved ip's.

Reloading your saved settings will completely reverse the benefit of resetting back to factory defaults, since you end up reloading the exact same settings you started with. You have to manually reconfigure your settings.
 
Could the HW NAT acceleration be disabled because ipv6 doesn't technically need it? (ipv6 will make NAT obsolete as each device will have its own external ip etc)

Note: I am not an expert on ipv6, that is just my understanding of it

No, because with a tunnel, you still have IPv4 traffic going on anyway.
 
Hi,

In my case things work well, but System Log / DHCP leases is empty.

Anyone else have the same phenomenon?

With kind regards
Joe :cool:

All my leases are showing up here. Try restarting a client, maybe your client simply didn't renew their existing leases yet.
 
Something major is wrong with the Merlin build for the RT-N16... :confused:

With kind regards
Joe :cool:

What doesn't really make much sense at this point is that some people have no problem at all flashing their router with it.

So unless someone with an RT-N16 and a serial cable can provide any log from the serial output, I will have to simply discontinue RT-N16 builds, as I have no way to figure out why it would only work for some and not for others.
 
I can confirm this observation. It's 150MBit on 5Ghz and 300Mbit on 2.4Ghz when it should be 300Mbit on both. Only difference is that I have a Intel Centrino 6300 in my laptop.
I guess it hasn't been seen much so far because a lot of laptops and wifi sticks only come with single link support.

I have a Centrino 6230 myself in my laptop, and had no issue connecting at 300 Mbits on the 5 GHz band with my RT-AC66U. Even had a Lanbench test showing a download speed of up to 160 Mbits with my desktop.

What router do you have?
 
Merlin
I tried the command and recieved an unknown host error. I also have tried several different time servers with the same results.


Code:
ntpclient -s -h time.nrc.ca

Code:
setup_receive:: bind...
time.nrc.ca: Unknown host

The is the message in the sys log if I try setting the time from the system page
Code:
Jan  1 01:35:34 rc_service: httpd 483:notify_rc restart_time;restart_httpd;restart_upnp


Thanks for all your work.
Steve

If you run as an AP, then you probably don't have working DNS resolution. Try using the IP instead of the hostname (132.246.11.227)
 
Regarding the RT-N16 issues: I'll try doing a clean rebuild of the firmware, just in case something went wrong at build time. Check in an hour or two for a BETA 1b version on Mediafire (I will remove the older Beta 1).

This will only be for RT-N16.
 
I'm generally finding this release is good, but Daylight Savings Time is broken. I think this is an Asus bug.

I'm in GMT, and during GMT, the system clock is one hour fast. I switched to manual setup, and got the correct time during GMT.

However, British Summer Time has just started, and instead of the clock going forwards one hour, it went back an hour (making it two hours wrong). I had to enable automatic DST and now it's the correct time under BST.

So it seems under automatic settings you only get BST regardless of the BST/GMT staus, and under manual settings, you get the correct time under GMT, and two hours slow under BST.

It would be nice if a straightforward thing like timezones worked correctly.
Hi,

Yes, this due to wrong DST (daylight saving time) implementaion in the firmware.
Go for manual daylight saving time!
Code:
Manual daylight saving time settings for 2013 (in Europe):
DST start time: M3 month / 5 week / 0 weekday / 2 hour
DST end time: M10 / 4 week / 0 weekday / 2 hour
These settings switched today like a charm to DST... :)

With kind regards
Joe :cool:
 
All my leases are showing up here. Try restarting a client, maybe your client simply didn't renew their existing leases yet.
I had a similar experience to this one time, and clearing my browser's cache fixed it (Chrome). You might try that. If you already have, just ignore this *smile*.
Hi Merlin,

It was the browser cache: I emptied the Firefox cache and now it show the leases again.

With kind regards
Joe :cool:
 
What doesn't really make much sense at this point is that some people have no problem at all flashing their router with it.

So unless someone with an RT-N16 and a serial cable can provide any log from the serial output, I will have to simply discontinue RT-N16 builds, as I have no way to figure out why it would only work for some and not for others.
Regarding the RT-N16 issues: I'll try doing a clean rebuild of the firmware, just in case something went wrong at build time. Check in an hour or two for a BETA 1b version on Mediafire (I will remove the older Beta 1).

This will only be for RT-N16.
Hi Merlin,

Well, I do not have the serial output connection, but I will retry the flashing - maybe a rest to defaults before the flash helps... :rolleyes:

Update:
I have just flashed the Beta1b over the Asus original .354 version and IT WORKED!
THANK YOU MERLIN!
Now I can start testing the Beta firmware on the RT-N16... :)

With kind regards
Joe :cool:
 
Last edited:

Latest threads

Sign Up For SNBForums Daily Digest

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