What's new

Beta Asuswrt-Merlin 386.1 Beta is now available

Status
Not open for further replies.
Any ideas why what was likely an implicit default in the stock was not showing up in the explicit MTU field in the beta?

Asus started work on adding that MTU setting on their firmware, but it seems they haven't finished it yet. When moving to my firmware (which already had support for it), the router incorrectly ends up with no MTU value at all, which doesn't get properly handled. I changed the default value to 1500 in beta 1 (which is why alpha users must either fix it or do a factory default reset), however it's possible that the MTU configuration code I merged from Asus doesn't properly deal with blank values that get inherited when moving from one of their beta firmware (or my alpha firmware) with the issue.

So, looks like the issue can also be introduced by running their beta firmware, and then switching to my firmware without doing a factory default reset.

I'll see if I can make the router use a more sensible value of 1500 if that value is completely blank.
 
Been using this for years.....Merlin gave the hint :)
Thanks @john9527 and @RMerlin , great thread. Since we are sticky averse, the above thread is in my browsers Bookmarks.
 
Asus started work on adding that MTU setting on their firmware, but it seems they haven't finished it yet. When moving to my firmware (which already had support for it), the router incorrectly ends up with no MTU value at all, which doesn't get properly handled. I changed the default value to 1500 in beta 1 (which is why alpha users must either fix it or do a factory default reset), however it's possible that the MTU configuration code I merged from Asus doesn't properly deal with blank values that get inherited when moving from one of their beta firmware (or my alpha firmware) with the issue.

So, looks like the issue can also be introduced by running their beta firmware, and then switching to my firmware without doing a factory default reset.

I'll see if I can make the router use a more sensible value of 1500 if that value is completely blank.

Thanks. Just to be clear, when I moved to their non-beta 386 version of the firmware for the AX88u, I did do a factory reset. Then when I moved back to the beta 3, I encountered the issue, which went away again when I went back to the stock firmware. I repeated the cycle 3-4 times.

I did not, however, move from the ASUS stock firmware to the beta and then do a new factory reset.
 
Dirty flashed from beta 2 to beta 3. At first, I didn't notice any difference at all, but then I saw that TENX had a great day on the NASDAQ, the fire in the fireplace was extra warm, and my glass of silver had turned to reposado, so yeah, this is a solid upgrade.

Thank you, RMerlin!
 
Dirty upgrade from Beta2 to 3. All working ok for everyone. Thanks @RMerlin for all your time & energy on this project!!
View attachment 28910


The marketing aim of AIMesh for ASUS was very obviously to sell more routers. And now some people have 6 routers in AiMesh config for a single house. Amazing - ASUS bean counters must be very happy
 
Last edited:
Updated to Beta 3, AX58U working fine no issues so far. As stated there is no speed test visible. CPU temp 49c. Same as always.
 
Last edited by a moderator:
Love the metaphor.
 
Is it only the RT-AC86U's that have seen a temp bump?
 
18 hours with Beta 3 on AX86U. Temps are 2.4 GHz: 50°C - 5 GHz: 53°C - CPU: 78°C with ambient temps of 27-32C now. Still having rolling kernal alarms when scribe installed (disappears when uninstalled):
kernel: _blog_emit, blogp = 0x6
kernel: _blog_emit, blogp = 0x4
kernel: _blog_emit, blogp = 0x2240
kernel: _blog_emit, blogp = 0x1a68
kernel: _blog_emit, blogp = 0x2

Will ignore the LE stuck at Authorizing as suggested by Merlin.
 
Is it only the RT-AC86U's that have seen a temp bump?

FWIW my AC86U has not experienced a significant bump in temp.

I have an audiable notification set up in HA when the temp hits 77C, and it has - but it doesn't seem to be a long term thing that the fan cannot easily mitigate.

Dunno if this helps, but I am happy to provide any relevant historical data.
 
Beta 3 Issue - Guest WiFi not connecting to Internet when VPN client is running.

Steps:
1. Connect client to Guest WiFi. VPN client running.
2. Guest WiFi not connecting to Internet. Regular WiFi connecting.
3. Set VPN client Service State to "off". Guest WiFi and regular WiFi connecting to Internet.
4. Set VPN client Service State to "on". Guest WiFi not connecting to Internet. Regular WiFi connecting.
5. Set VPN client Service State to "off". Guest WiFi and regular WiFi connecting to Internet.

Router is RT-AC86U.
Hard factory reset done and settings entered from scratch.
Connection to Internet tested by streaming using ABC iView app and YouTube app.
Devices tested were Apple iPhone and Android mobile.
Devices connected to Guest WiFi never disconnected during testing.
No errors or unexpected messages seen in system log.
VPN client public Internet address checked as a VPN Server address.
Issue observed on 386.1 Beta 1, 3 & 3. Not seen on 384.19
 
Updated from Beta2 to Beta3...…..running for few hours and so far so good on both units. Thanks @RMerlin
 
FWIW my AC86U has not experienced a significant bump in temp.

I have an audiable notification set up in HA when the temp hits 77C, and it has - but it doesn't seem to be a long term thing that the fan cannot easily mitigate.

Dunno if this helps, but I am happy to provide any relevant historical data.
You have active cooling on yours? Nice. I'm not concerned about the temps - still well below the limits. I likely would not have even noticed had it not been mentioned by others.
 
Hmm...maybe the temperature bump on RT-AC86U routers (@RMerlin mentioned that Asus sometimes tweaks the CPU power saving measures) is related to them trying to resolve the long-standing warm reboot issues this router suffers from. Pure speculation on my part, just a guess.

Edit: I'm not sure this is a great tradeoff, even if it was the intention. My RT-AC86U router's CPU went from averaging about 74C on previous firmwares (in an ambient room temp of 20-21C), to now running about 87C on this 386.1 B3 firmware (with the same 21C ambient room temp). Wow, what happens in the summer, when ambient room temps might be 10C degrees higher?? (BTW, no, I don't have A/C) That potentially puts the CPU really close to that 100C throttling temperature. Ugly IMHO, I hope Asus reverts this change by then.
 
Last edited:
You have active cooling on yours? Nice. I'm not concerned about the temps - still well below the limits. I likely would not have even noticed had it not been mentioned by others.

Yes, I put this fan

https://www.amazon.com/gp/product/B07XDGXWC3/?tag=snbforums-20

on it and set up an automation in Home Assistant that uses SSH to grab the temp (and many other metrics) from my various routers, and take action on them. One of the few audio actions is that it announces "Router temp has hit 77C..." and it has, but this is not real unusual, it does so once or twice a week, even with the fan on low speed.

It was originally set up to announce a lot of cool data, but it was bothering my wife to hear Suricata report "So and so attempted CVS xyz from an IP address in Russia" eight times a day. Personally I thought it was cool...
 
FWIW my AC86U has not experienced a significant bump in temp.

I have an audiable notification set up in HA when the temp hits 77C, and it has - but it doesn't seem to be a long term thing that the fan cannot easily mitigate.

Dunno if this helps, but I am happy to provide any relevant historical data.
Uhhh, what fan? there's one in the AC86?
 
Status
Not open for further replies.

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

Members online

Back
Top