[Preview] 380.57 alpha test builds for all models

[RMerlin]

rmerlin, is this alpha 3 different than the alpha 3 one you release last week?

Yes, quite a few changes. Dig in the commit log to determine which exact change - that series of semi-random numbers and letters in the version string are the start of the commit ID from which the firmware was compiled.

 

[jmantn]

I have an RT-AC87R and the following connected as a wired bridge to that router: RT-N66U & RT-AC68U.

I've enabled Multi-User MIMO Beta and DNSSEC support on the AC87R.

I have multiple iPhone 6s Plus's, iPad Air 2's, and two 4th Generation Apple TV's (one hard wired the other uses WiFi from the 68U). Beam forming is in fact set to enable when you install this firmware and I've left that as is for now. I typically don't change anything except to assign the following: IP's, Wireless Channels, and I do enable all IGMP options (Apple TV at least in the past worked better with those set to enable). I'm not a power user per say when it comes to tricking out router options but wanted to share what I've changed and the devices that will be using the network. Lastly my network sees heavy usage every day both professionally and personally so definitely looking forward to all included optimizations.

So far everything seems to working fine but just finished installing, factory reset, and reconfiguring all devices and manually assigning IP's.

Just wanted to check in with my config and will post if there's any unordinary issues that arise.

 

[lilstone87]

Yes, quite a few changes. Dig in the commit log to determine which exact change - that series of semi-random numbers and letters in the version string are the start of the commit ID from which the firmware was compiled.

Merlin I upgraded to last night's alpha3 build for the AC3100. I didn't do no kind of reset as I don't think it's need from switching from the other alpha3 build. I see you submitted a commit last night for the port ordering, but I'm guessing that isn't in last nights build is it? As I just checked, and the ordering of ports is still like you mentioned yesterday, which is bottom to top.

 

[Veky]

I've updated my RT-N66U from 378.56_2 to this one.

I know Merlin will probably beat me to death for writing about this again, but the issue with the network map and client list is back again. Every time I click on one of those, the page freezes or logs me out. Same thing happened after upgrade from 378.55 to 378.56_2. Factory reset resolves it.

 

[eddiez]

Just installed on RT68U, coming from 378.56_2. Flawless installation and no issues so far. The network list does show some garbled entries in the device name, but that also occurred in the previous firmware (not in 378.55 though).

 

[RMerlin]

Merlin I upgraded to last night's alpha3 build for the AC3100. I didn't do no kind of reset as I don't think it's need from switching from the other alpha3 build. I see you submitted a commit last night for the port ordering, but I'm guessing that isn't in last nights build is it? As I just checked, and the ordering of ports is still like you mentioned yesterday, which is bottom to top.

That's correct, the fix was committed after those builds were generated, and is therefore not included.

 

[gffmac]

I've updated my RT-N66U from 378.56_2 to this one.

I know Merlin will probably beat me to death for writing about this again, but the issue with the network map and client list is back again. Every time I click on one of those, the page freezes or logs me out. Same thing happened after upgrade from 378.55 to 378.56_2. Factory reset resolves it.

I get the same on N66U, will do a wipe tomorrow when I get time.

 

[Deleted member 22229]

Yes, quite a few changes. Dig in the commit log to determine which exact change - that series of semi-random numbers and letters in the version string are the start of the commit ID from which the firmware was compiled.

Thanks was wondering this myself. I will flash the new 57 alpha3.

EDIT: Firmware flashed up and running.

 

[JohnNerd]

RTAC87U is rock solid with this release. Thank you Merlin!

AC66U however was highly unstable in media bridge mode both on 2G and 5G. Wifi drops every 10-20 seconds. I tried factory reset several times. No luck. Revert to previuos version it's stable again.

 

[Rajveer]

A factory default reset is not required if coming from 378.56_2

Sorry for the question but...I'm guessing it's also ok to not do a factory default reset if coming from 378.56 Beta 2 (since I think 378.56 Beta 2 -> 378.56_2 was ok I think)?

 

[Naifu]

RT3200 up and running for 12+ hours without any problems at all.

Cheers
N.

 

[jerry6]

could not get it to run media bridge on AC 66 , would shut down and restart , tried 4 times

Hi everyone,

I don't know when I'll be able to wrap up an actual release (probably won't until some time in December), so I decided for the time being to upload test builds on Mediafire.

https://www.mediafire.com/folder/bj94sbhrh7e49//Test Builds

While I won't be answering most of the reports posted in the thread, I will be reading every one of them. I'm mostly interested in reading feedback about the new DNSSec support, what might have been fixed (or broken) in Asus's 378_858 code.

A factory default reset is not required if coming from 378.56_2. If you run into any odd issue, then do go ahead and proceed with a factory default reset, in case you might be carrying on some old issues.

Note that these builds have received NO extended testing so far, aside from the RT-AC88U build. Also, the changelog isn't complete yet, you might need to check the Github commit for the details of what was changed (those builds were generated on November 23rd):

https://github.com/RMerl/asuswrt-merlin/commits/master


Thanks.

RTAC87U is rock solid with this release. Thank you Merlin!

AC66U however was highly unstable in media bridge mode both on 2G and 5G. Wifi drops every 10-20 seconds. I tried factory reset several times. No luck. Revert to previuos version it's stable again.

 

[gffmac]

Sorry for the question but...I'm guessing it's also ok to not do a factory default reset if coming from 378.56 Beta 2 (since I think 378.56 Beta 2 -> 378.56_2 was ok I think)?

Unless you have an issue yes

 

[cmillar6]

Upgraded to 380.57 Alpha 3 and now I am seeing "Bits has encountered an error communicating with an Internet Gateway Device" is my Windows 10 event viewer.

 

[RMerlin]

Sorry for the question but...I'm guessing it's also ok to not do a factory default reset if coming from 378.56 Beta 2 (since I think 378.56 Beta 2 -> 378.56_2 was ok I think)?

Should be close enough.

 

[elorimer]

I get the same on N66U, will do a wipe tomorrow when I get time.

Not having this issue on my N66U.

The client list for me is kinda funky, but then so is my network. Across a RT-N10+ working as a bridge, I have a static IP address assigned to the MAC for a Tivo. The Tivo pulls the right IP address, but shows up in the list as 'NETBOOK'. If I click on the MAC and try and change the icon, when I click "Apply", the MAC/IP binding toggles, and the "already in the list" dialog shows up. I don't know that this is specific to alpha 3 though.

 

[Tom Ames]

I've updated my RT-N66U from 378.56_2 to this one.

I know Merlin will probably beat me to death for writing about this again, but the issue with the network map and client list is back again. Every time I click on one of those, the page freezes or logs me out. Same thing happened after upgrade from 378.55 to 378.56_2. Factory reset resolves it.

I have had a similar issue on my RT-N66Us (one is an AP) using Edge. Using Chrome or Firefox, I have had no problems.

 

[eddiez]

Upgraded to 380.57 Alpha 3 and now I am seeing "Bits has encountered an error communicating with an Internet Gateway Device" is my Windows 10 event viewer.

Same here. No RC found yet. The service (Background Intelligent Transfer Service) starts automatically and needs an manual start. Link found to the router, apparently some UPnP issue in the router.

 

[Lost Dog]

Does this use the same version of dropbear that was causing the ssh tunnel issues in 378.56?

 

[RMerlin]

Does this use the same version of dropbear that was causing the ssh tunnel issues in 378.56?

Yes. I patched one potential issue on it, but I don't know if it was related or not. I want to wait for the author to possibly update it before I'm ready for a final release - if by then he hasn't updated it, I will downgrade it to an earlier version.