What's new

[Alpha] Preview builds for Asuswrt-Merlin 380.60

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

Just curious.... what versions of the 380.60 alpha can you flash back? Anybody have any experience? I figure going back to an old alpha build might be a way to go old or alternate firmware in the future.
try with restoration tool...

sent from Kodi 17 Krypton
 
Its not simple .It is more than just " Try the Restoration tool"
Can be downgrade with Asus official or Merlin

Here the steps(tested myself on my 68u):Good luck

https://www.asus.com/support/faq/1000814/


Thanks all haven't made the plunge yet, but was just wondering if there were specific flash back characteristics between alpha builds noted. I guess it might depend on model router also. I got the 68p, so good to know it worked for you on the 68u. I guess they could make it so you couldn't go back to *.60 alpha builds when the normal version comes out, so I guess it's too soon to be asking anyway.
 
Installed Alpha 3 on the AC5300, it was able to bypass the new ASUS lock and works great! Thanks a lot Merlin
 
Hello! . Its the first post for me but iv'e been around for quite awhile. What differs Merlin realeses from Asus original for me is
Merlin =+ 10-15ms in gaming wired Connection.
merlin = slower respons time over gaming in general, online gaming compared to asus original.This is compared with all the latest realeses of both original and merlin.
Try these settings and post back.


Installed Alpha 3 on the AC5300, it was able to bypass the new ASUS lock and works great! Thanks a lot Merlin
Phoenix what do you mean by "it was able to bypass the new Asus lock"??
in regards to the 5300


Merlin,
Are you using the .59 wireless drivers in alpha 2 or 3 for now on the 5300? I know you stated you were for the 3200.
 
Refreshed builds uploaded.

I'm especially interested in feedback from IPv6 users.


What specific IPV6 feedback do you want? Is it just the addressing with anything other than /64 or is there other functionality you'd like to see tested as well?
 
Should i use restauration tool to update to Merlin`s Fw? And after that make a hardware reset or i can just update over my FW and after that make the hardware reset?

Thanks
 
I know Merlin,ages an awesome job with the firmwares, but is there a lot of improvements and speed gain over the official Asus firmwares? Worth the change at 5300 model one?

Thanks
 
Merlin,
Are you using the .59 wireless drivers in alpha 2 or 3 for now on the 5300? I know you stated you were for the 3200.

The RT-AC5300 driver is from GPL 380_3341.
 
What specific IPV6 feedback do you want? Is it just the addressing with anything other than /64 or is there other functionality you'd like to see tested as well?

Some people were having trouble getting any delegated prefix at all with their ISP, which wasn't delegating a /64 but something different. I'm curious as if the fix I applied resolves that issue.

And also to ensure that anyone else who also uses DHCP-PD still can get their prefix properly delegated.
 
I know Merlin,ages an awesome job with the firmwares, but is there a lot of improvements and speed gain over the official Asus firmwares? Worth the change at 5300 model one?

Thanks

Wifi performance will always be identical, since it's the exact same closed source driver as Asus.

For the other improvements, they're all listed on the website.
 
Is this a know bug?

AC68U / 380.60 Alpha 3 / factory reseted.

When trying to specify paths to UPNP Server it wont render the folder structure from my USB disk.

XJum8nQ.png


I`m exactly with the same issue!!! But here at 5300 one Alpha 3 as well

Merlin are you aware about this?

Thanks
 
I get this from my 2.4GHz devices. when this happends.. i get SUPER SLOW connectivity.. until reboot.
5GHZ looks normal.

Jun 14 16:02:31 dnsmasq-dhcp[1367]: DHCPDISCOVER(br0) 255.255.255.255 7c:dd:90:8d:71:c9
Jun 14 16:02:31 dnsmasq-dhcp[1367]: DHCPOFFER(br0) 10.0.0.201 7c:dd:90:8d:71:c9
Jun 14 16:02:32 dnsmasq-dhcp[1367]: DHCPDISCOVER(br0) 255.255.255.255 7c:dd:90:8d:82:2c
Jun 14 16:02:32 dnsmasq-dhcp[1367]: DHCPOFFER(br0) 10.0.0.202 7c:dd:90:8d:82:2c
Jun 14 16:02:38 dnsmasq-dhcp[1367]: DHCPDISCOVER(br0) 255.255.255.255 7c:dd:90:8d:71:c9
Jun 14 16:02:38 dnsmasq-dhcp[1367]: DHCPOFFER(br0) 10.0.0.201 7c:dd:90:8d:71:c9
Jun 14 16:02:39 dnsmasq-dhcp[1367]: DHCPDISCOVER(br0) 255.255.255.255 7c:dd:90:8d:71:c9
Jun 14 16:02:39 dnsmasq-dhcp[1367]: DHCPOFFER(br0) 10.0.0.201 7c:dd:90:8d:71:c9
Jun 14 16:02:39 dnsmasq-dhcp[1367]: DHCPDISCOVER(br0) 255.255.255.255 7c:dd:90:8d:82:2c
Jun 14 16:02:39 dnsmasq-dhcp[1367]: DHCPOFFER(br0) 10.0.0.202 7c:dd:90:8d:82:2c
Jun 14 16:02:41 dnsmasq-dhcp[1367]: DHCPDISCOVER(br0) 255.255.255.255 7c:dd:90:8d:71:c9
Jun 14 16:02:41 dnsmasq-dhcp[1367]: DHCPOFFER(br0) 10.0.0.201 7c:dd:90:8d:71:c9
Jun 14 16:02:42 dnsmasq-dhcp[1367]: DHCPDISCOVER(br0) 255.255.255.255 7c:dd:90:8d:82:2c
Jun 14 16:02:42 dnsmasq-dhcp[1367]: DHCPOFFER(br0) 10.0.0.202 7c:dd:90:8d:82:2c
Jun 14 16:02:44 dnsmasq-dhcp[1367]: DHCPDISCOVER(br0) 255.255.255.255 7c:dd:90:8d:71:c9
Jun 14 16:02:44 dnsmasq-dhcp[1367]: DHCPOFFER(br0) 10.0.0.201 7c:dd:90:8d:71:c9
Jun 14 16:02:44 dnsmasq-dhcp[1367]: DHCPDISCOVER(br0) 255.255.255.255 7c:dd:90:8d:82:2c
Jun 14 16:02:44 dnsmasq-dhcp[1367]: DHCPOFFER(br0) 10.0.0.202 7c:dd:90:8d:82:2c
Jun 14 16:02:45 dnsmasq-dhcp[1367]: DHCPDISCOVER(br0) 255.255.255.255 7c:dd:90:8d:71:c9
Jun 14 16:02:45 dnsmasq-dhcp[1367]: DHCPOFFER(br0) 10.0.0.201 7c:dd:90:8d:71:c9
Jun 14 16:02:46 dnsmasq-dhcp[1367]: DHCPDISCOVER(br0) 255.255.255.255 7c:dd:90:8d:82:2c
Jun 14 16:02:46 dnsmasq-dhcp[1367]: DHCPOFFER(br0) 10.0.0.202 7c:dd:90:8d:82:2c
Jun 14 16:02:47 dnsmasq-dhcp[1367]: DHCPDISCOVER(br0) 255.255.255.255 7c:dd:90:8d:71:c9
Jun 14 16:02:47 dnsmasq-dhcp[1367]: DHCPOFFER(br0) 10.0.0.201 7c:dd:90:8d:71:c9
Jun 14 16:02:48 dnsmasq-dhcp[1367]: DHCPDISCOVER(br0) 255.255.255.255 7c:dd:90:8d:82:2c
Jun 14 16:02:48 dnsmasq-dhcp[1367]: DHCPOFFER(br0) 10.0.0.202 7c:dd:90:8d:82:2c
 
Updated my RT-AC88U to alpha3 no issues with IPv6 and /48 address here.

10/10 on test-ipv6.com
 
Updated my RT-AC88U to alpha3 no issues with IPv6 and /48 address here.

10/10 on test-ipv6.com

Did you previously have issues?
 
Did you previously have issues?
I never got it to work on 380.59. In the log of my ISP they did see that my router didn't grab the prefix. It did work on an earlier asus version though I forgot the version.
 
I never got it to work on 380.59. In the log of my ISP they did see that my router didn't grab the prefix. It did work on an earlier asus version though I forgot the version.

Thanks. That confirms that this prefix delegation code was indeed broken with non-standards prefixes.

I've already forwarded the patch to Asus, hopefully they will integrate it in a future official release.
 
@RMerlin

Would there any reason why my 2.4GHz acting like crazy after updating ?
tried to factory reset. weird and slow 2.4GHz behavior. ( after a while running )
And like i said, reboot fixes it , until next time it happens.
 
Device: AC5300 / Ver: 380.60-a3 / FR after 380.59 / ISP: Comcast (Chicago area)

IPV6 configuration: Connection type native / DHCP-PD enabled / Auto Configuration: Stateless / Connect to DHCP Server: Enabled / Router Advertisement: Enabled

After installing 380.60-a3 my IPV6 address on the router came back with a different prefix, the first time I've had a new prefix in about 6 weeks. My devices received a new IPV6 address using the new prefix, but also retained the old prefix until I reset the interface. The new address assignment was almost immediate whereas in previous versions I had seen this take a couple of minutes.

Typically (previous versions), I see good behavior from IPV6 for about the first 4-6 hours after an upgrade then it seems to stop working -- devices lose their addresses and I have to reboot the router to restore IPV6 functionality. I've also noticed that in the System Logs | IPV6 screen, there are only a couple devices shown when I know more have an IPV6 address (e.g. the laptop I'm typing this on has an IPV6 address but it does not show up on this screen).

One final note on IPV6 -- my Macbook Pro seems to get a different IPV6 address pretty frequently (haven't nailed down the timing on this). I am using Stateless configuration for IPV6.

Unfortunately, the prefix is a /64, so I don't know if this will help you with the different prefix length.

One side note: I did not see the typical sluggishness in the UI immediately after the upgrade.

Brian
 
@RMerlin

Would there any reason why my 2.4GHz acting like crazy after updating ?
tried to factory reset. weird and slow 2.4GHz behavior. ( after a while running )
And like i said, reboot fixes it , until next time it happens.

We'd need to know which router you're talking about, they all use different drivers.
 

Similar threads

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