Release Asus AC86U New Firmware - 3.0.0.4.386_40451-g30f1b6c

[Lord_Vader]

It states under "new features" on the third bold line "System factory default and reboot"

"1. AiMesh 2.0
- System optimization: one click in AiMesh to optimize the topology
- System Ethernet backhaul mode, all nodes will only connect by ethernet, all bands will be released for wireless clients.
- System factory default and reboot."

Does it mean that a factory reset will be done, or is required after upgrading?
I'm waiting for my nodes RT-AC 88U and RT-AC 68U to get .386 first before doing anything stupid.

 

[alan6854321]

Hi there,

New user here - I've had my RT-AC86U just over a week.

I manually updated it to 3.0.0.4_384_82072 as soon as I got it and everything's been running fine. This morning it flagged an update so it let it go ahead and it updated to 3.0.0.4.386_40451.

Everything seemed to be OK but I'm getting huge numbers of messages in my syslog daemon. Not just the "not mesh client, can't update it's ip" mentioned by others but many of these ....


kernel: protocol 0800 is buggy, dev eth6
kernel: protocol 0800 is buggy, dev eth6
kernel: protocol 0800 is buggy, dev eth6

conn_diag[1492]: CONNDIAG: <SYS2>C>192.168.1.1>24:4B:FE:E6:32:80>-1>136900>-1>-1>-1
CONNDIAG: Built the SQL file of conn_diag.
<STAINFO>C>192.168.1.1>24:4B:FE:E6:32:80>40:B8:37:B2:A8:1E>2G>-61>1>65>72.2>4259.7>1128.8>-1>-1
CONNDIAG: Built the SQL file of conn_diag.
<WLCEVENT>C>192.168.1.1>24:4B:FE:E6:32:80>24:18:1D:FE:FA:0E>5G>2>0>0>1>0>0

I rolled back to 3.0.0.4_384_82072 and it's all gone quiet again.
Any advice, should I just run the new s/w with all the messages, or wait for another update?

Thanks,
Alan T.

 

[bbunge]

Hi there,

New user here - I've had my RT-AC68U just over a week.

I manually updated it to 3.0.0.4_384_82072 as soon as I got it and everything's been running fine. This morning it flagged an update so it let it go ahead and it updated to 3.0.0.4.386_40451.

Everything seemed to be OK but I'm getting huge numbers of messages in my syslog daemon. Not just the "not mesh client, can't update it's ip" mentioned by others but many of these ....


kernel: protocol 0800 is buggy, dev eth6
kernel: protocol 0800 is buggy, dev eth6
kernel: protocol 0800 is buggy, dev eth6

conn_diag[1492]: CONNDIAG: <SYS2>C>192.168.1.1>24:4B:FE:E6:32:80>-1>136900>-1>-1>-1
CONNDIAG: Built the SQL file of conn_diag.
<STAINFO>C>192.168.1.1>24:4B:FE:E6:32:80>40:B8:37:B2:A8:1E>2G>-61>1>65>72.2>4259.7>1128.8>-1>-1
CONNDIAG: Built the SQL file of conn_diag.
<WLCEVENT>C>192.168.1.1>24:4B:FE:E6:32:80>24:18:1D:FE:FA:0E>5G>2>0>0>1>0>0

I rolled back to 3.0.0.4_384_82072 and it's all gone quiet again.
Any advice, should I just run the new s/w with all the messages, or wait for another update?

Thanks,
Alan T.

You mean AC86U?
Ignore the error messages. New firmware works well!

 

[alan6854321]

You mean AC86U?
Ignore the error messages. New firmware works well!

Sorry, yeah 86, not 68.
Ok, just alarmed by the continuous stream of what look like error messages.

 

[OzarkEdge]

It states under "new features" on the third bold line "System factory default and reboot"

"1. AiMesh 2.0
- System optimization: one click in AiMesh to optimize the topology
- System Ethernet backhaul mode, all nodes will only connect by ethernet, all bands will be released for wireless clients.
- System factory default and reboot."

Does it mean that a factory reset will be done, or is required after upgrading?
I'm waiting for my nodes RT-AC 88U and RT-AC 68U to get .386 first before doing anything stupid.

It's listing a new firmware feature, not an instruction for upgrading firmware. If there are special upgrade instructions in the release notes, they will be called out clear enough as such.

OE

 

[Jbennett360]

Might hold out on updating this.

 

[ablatt]

Might hold out on updating this.

How do you hold off? I manually rolled back 40451 to 81992 on my AC86U and it auto-updated back to 40451. It's actually the first time I can remember my AC86U ever auto updating. Before installing 40451, I sat on 81992 and 82072 for quite a while without either updating. Something changed recently for me in terms of auto update.

 

[QuikSilver]

How do you hold off? I manually rolled back 40451 to 81992 on my AC86U and it auto-updated back to 40451. It's actually the first time I can remember my AC86U ever auto updating. Before installing 40451, I sat on 81992 and 82072 for quite a while without either updating. Something changed recently for me in terms of auto update.

There has been some talk regarding auto updating on the 86u model in this thread. Looks like that is the way Asus is headed but thankfully Merlin won't be.

Asus Auto Update Experiences

As suggested, this thread is to document Asus Auto Update successes and failures. Please include the router model and firmware version.

www.snbforums.com

 

[Jbennett360]

How do you hold off? I manually rolled back 40451 to 81992 on my AC86U and it auto-updated back to 40451. It's actually the first time I can remember my AC86U ever auto updating. Before installing 40451, I sat on 81992 and 82072 for quite a while without either updating. Something changed recently for me in terms of auto update.

I've not manually updated to this FW and it hasn't auto updated either.

 

[GunnarH]

Ookla speedtest stuck in the uploading test phase .

It remains stuck in the testing state even after rebooting.

 

[bbunge]

There has been some talk regarding auto updating on the 86u model in this thread. Looks like that is the way Asus is headed but thankfully Merlin won't be.

Asus Auto Update Experiences

As suggested, this thread is to document Asus Auto Update successes and failures. Please include the router model and firmware version.

www.snbforums.com

Actually, all manufacturers of home/small office routers will be going to auto update/upgrade if they want to sell their product in markets where auto upgrade is or will be required. And for 99% of the people with home networks who don't care about security it will be a good thing.
As for me, I'm finding I really don't miss the Merlin features and can feel good that if something happens to me the Asus router will keep on working well for my family.

 

[GunnarH]

Ookla speedtest stuck in the uploading test phase .

It remains stuck in the testing state even after rebooting.

Deleting the test history fixes the hanging testing state..

 

[OzarkEdge]

Actually, all manufacturers of home/small office routers will be going to auto update/upgrade if they want to sell their product in markets where auto upgrade is or will be required. And for 99% of the people with home networks who don't care about security it will be a good thing.
As for me, I'm finding I really don't miss the Merlin features and can feel good that if something happens to me the Asus router will keep on working well for my family.

I appreciate your point, but I think you overstate it (keep on working well) just a little.

OE

 

[GunnarH]

Web server unresponsive a couple of times.

gunnar@RT-AC86U-8730:/# netstat -a |grep CLOSE
tcp 674 0 RT-AC86U-8730.:www 192.168.1.99:55426 CLOSE_WAIT
tcp 674 0 RT-AC86U-8730.:www 192.168.1.99:55680 CLOSE_WAIT
tcp 674 0 RT-AC86U-8730.:www 192.168.1.99:55659 CLOSE_WAIT
tcp 674 0 RT-AC86U-8730.:www 192.168.1.99:64340 CLOSE_WAIT
tcp 731 0 RT-AC86U-8730.:www 192.168.1.99:64264 CLOSE_WAIT
gunnar@RT-AC86U-8730:/#

Recv-Q not decremented and state remains in CLOSE_WAIT .

syslog attached

 

[keefrto]

What's with the release of Aimesh firmware well? I do use aimesh so do I download this and the aimesh firmware?

 

[OzarkEdge]

What's with the release of Aimesh firmware well? I do use aimesh so do I download this and the aimesh firmware?

Your post is confusing... AiMesh is a feature of some Asus router firmware... it's in the router firmware, like what you are already using on your network.

OE

 

[ATLga]

Your post is confusing... AiMesh is a feature of some Asus router firmware... it's in the router firmware, like what you are already using on your network.

OE

I think he's referring too this OLD thread: https://www.snbforums.com/threads/o...4-384-20308-for-all-supported-products.44375/
That's had a couple comments in yesterday.

 

[follower]

Thank god. I've not installed yet.

 

[keefrto]

I think he's referring too this OLD thread: https://www.snbforums.com/threads/o...4-384-20308-for-all-supported-products.44375/
That's had a couple comments in yesterday.

Yup, note to self read the post before commenting, thanks

 

[JWoo]

Actually, all manufacturers of home/small office routers will be going to auto update/upgrade if they want to sell their product in markets where auto upgrade is or will be required. And for 99% of the people with home networks who don't care about security it will be a good thing.
As for me, I'm finding I really don't miss the Merlin features and can feel good that if something happens to me the Asus router will keep on working well for my family.

Auto upgrade is a contentious feature (think of Windows 10 as a simple negative example) as it pits the user's right to determine which software version they use versus the manufacturer who would like to reduce maintenance costs by having all users on the same version. Risk averse users in fact would like to delay upgrades until they are well proven, and auto upgrade if forced prevents that. Different countries see SW in very different ways (look at the Free Software Foundation Europe FSFE and their fight against ISPs). I would also say that I disagree completely with you as I depend on the @RMerlin features and only bought the RT-AX58U because it ran a Broadcom chipset and I thought Merlin might support it, which wound up happening. I would not run a router without DoT as one example, and the implementation of DoT from @john9527 and @RMerlin is very well done using Stubby. DoT, enhanced logging, SSH and scripting are examples of features that are essential from my perspective. I haven't run a router on OEM firmware for probably 10+ years (all Merlin or Tomato) with uptime and security that the OEM cannot match.