Release Asuswrt-Merlin 386.2 is now available

[sbsnb]

Dirty flash 386.2_2 over 386.1_2. Been up for 3 days. Only issue I noticed is that all of my bandwidth data prior to this month was wiped out. It could have happened with the update to 386.1_2 and I didn't notice until now.

 

[Sicario]

Are yours also connected wirelessly? This combination of routers and AiMesh2.0 setup seems problematic by several reports

Wireless backhaul, with "Great" connection quality.

I have the exact same setup, but haven't had any issues. It appears to be very stable. Are you using Smart Connect and one single SSID, or do you have Smart Connect disabled and 2 SSID's for the separate bands (I have the latter setup)?

It didn't happen before with 386.2, it happens only after I install 386.2_2. Haven't had any issue since last time I tried power cycle. Smart Connect disabled, I have 2 SSIDs.

 

[jpthsd]

How far can your AX/AC (specially 86U) go without reset/rebooting the router while on 386.2_2? I am little hesitate to up Merlin 386.2_2 since my AX86U AsusWRT firmware currently let it run like 25 days without a single reboot...without any buffering of the AiMesh Node AC86U ....

by reading around, 386.2_2's still having some sort of troubles..(the last merlin fw being used with 386.1 & 386.1_2 caused the buffering all around)...which makes me hesitate to go dark side

 

[John Adler]

Dirty flash 386.2_2 over 386.1_2.
All fine so far.

 

[RMerlin]

How far can your AX/AC (specially 86U) go without reset/rebooting the router while on 386.2_2? I am little hesitate to up Merlin 386.2_2 since my AX86U AsusWRT firmware currently let it run like 25 days without a single reboot...without any buffering of the AiMesh Node AC86U ....

by reading around, 386.2_2's still having some sort of troubles..(the last merlin fw being used with 386.1 & 386.1_2 caused the buffering all around)...which makes me hesitate to go dark side

My own RT-AX88U hasn't been rebooted for 19 days. My Roomba has been connected to wifi without getting disconnected for 468 hours now, which means since that reboot 19 days ago.

 

[Clark Griswald]

Curious if Tim will add Roomba connectivity to his wifi testing analysis

PS: Zero complaints from The Family, since upgrade to RMerlin's latest fw!

Stay Safe Everyone

 

[banger]

Just noticed a Wifi disconnect on my node. Around the same time in the log is this

Apr 21 18:34:53 rc_service: watchdog 801:notify_rc start_cfgsync
Apr 21 18:34:56 rc_service: cfg_server 25258:notify_rc update_sta_binding
Apr 21 18:34:58 rc_service: cfg_server 25291:notify_rc update_sta_binding

So either cfgsync or sta_binding interrupts node wifi. Who to let know to fix?

 

[Sicario]

So either cfgsync or sta_binding interrupts node wifi.

related to my previous post, I haven't had any node disconnection since I unbinded my chromecast. this might be it.

 

[banger]

I have a Speaker bound to the node, but main router signal is weak where the speaker is that is why I bound the node. Hmmm.

 

[dazedandlost]

Here to report (as an observation only) that I am unable, after a double digit number of attempts, to upgrade (dirty) to 386.2_2 from the gui. I have paid attention during this thread to reports and suggestions re similar difficulties. I tried pretty much every one of them and also what has worked for me in the past.

Short summary: nothing works – the browser (any of them) just hangs. Sometimes there’s a reboot reported, sometimes not. Anyway, I have another router on the way because chip shortage, I can’t see anything in the u/g I really need, what I have is working and summertime chores.

So the factory reset/clean upgrade, read the logs, try other things, and like that will wait, perhaps until winter.

No matter, thanks to all for the good work you are doing and making available.

 

[bbunge]

This release is rather boring. Outside of the quick test of AiMesh with an AC86U I have made almost no settings changes! I did bump the 5 GHz up to 160 MHz and left it there. BRAVO! Oh, I did turn on Guest 1 on 2.4 GHZ.

 

[DJones]

Unfortunately been getting a lot of issues with certain lan devices on 386.2_2 not really sure what’s going on.

Logs show a lot of this:
“[Mac Address] not mesh client, can't update it's ip”

I’m not using a mesh network at all. Clearly a issue some suggested disabling manual assignments but I need manual assignments on. Other threads suggest disabling AiProtection… any solution besides these?

Solved: Discovered the issue to be Enable Fast Leave was on (set by me), turned it off and it solved the issue.

***Update: Issue still persists, changing settings in router must have kicked that device off the network so the logs looked clean. But the issue with “[Mac Address] not mesh client, can't update it's ip” remains. Fast leave disabled did get another device back online through (tv).

 

[m0rF1uS]

Unfortunately been getting a lot of issues with certain lan devices on 386.2_2 not really sure what’s going on.

Logs show a lot of this:
“[Mac Address] not mesh client, can't update it's ip”

I’m not using a mesh network at all. Clearly a issue some suggested disabling manual assignments but I need manual assignments on. Other threads suggest disabling AiProtection… any solution besides these?

Solved: Discovered the issue to be Enable Fast Leave was on (set by me), turned it off and it solved the issue.
View attachment 33360

I’m experiencing the same thing but with wireless and especially Apple TV. Same log message and the Apple TV report every 5-10 mins that it’s not connected to the network. This started after upgrading my AX88U to 386.2
I’ve experienced it before last year at one point with the previous tree firmware.... not sure of the exact firmware version though.




Apr 21 20:00:55 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:00 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:05 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:10 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:14 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:34 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:40 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:45 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:50 kernel: C80:83:E0:633 not mesh client, can't update it's ip

 

[slidermike]

Solved: Discovered the issue to be Enable Fast Leave was on (set by me), turned it off and it solved the issue.
View attachment 33360

Where is this setting on the gui? I do not see it on my ax86u.

Each time I update to 386.x I have 1 client that absolutely will not connect to my router but has no issues on 386.1
I am willing to try this setting for my situation if it is supported in my device.

**UPDATE**
I found it. Google is your friend.
It is located under LAN/IPTV and becomes available when you enable multicast routing.

Since mine is disabled I doubt it will be my cure.

 

[DJones]

I’m experiencing the same thing but with wireless and especially Apple TV. Same log message and the Apple TV report every 5-10 mins that it’s not connected to the network. This started after upgrading my AX88U to 386.2
I’ve experienced it before last year at one point with the previous tree firmware.... not sure of the exact firmware version though.




Apr 21 20:00:55 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:00 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:05 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:10 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:14 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:34 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:40 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:45 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:50 kernel: C80:83:E0:633 not mesh client, can't update it's ip

Fast leave was affecting dhcp in general for me for both wireless and wired. Some devices would momentarily connect others wouldn’t allow for a dhcp assignment, others would work IF I assigned a dhcp manually on both sides. It was a mess.

 

[DJones]

Where is this setting on the gui? I do not see it on my ax86u.

Each time I update to 386.x I have 1 client that absolutely will not connect to my router but has no issues on 386.1
I am willing to try this setting for my situation if it is supported in my device.

It’s located under LAN IPTV special applications .

 

[m0rF1uS]

Where is this setting on the gui? I do not see it on my ax86u.


It’s located under LAN IPTV special applications .View attachment 33361

That setting is disabled for me and I have multicasting disabled as well... I think that’s the default

 

[DJones]

That setting is disabled for me and I have multicasting disabled as well... I think that’s the default

Update: Issue still persists. I think changing setting in the router kicked that device off the network for a bit which is why the logs looked clean. But one device is still spamming “[Mac Address] not mesh client, can't update it's ip”.

And correct it’s not default to be on. Still persists with all of those settings off.

Disabling fast leave did get a different device back online through.. was a different issue I guess.

 

[MvW]

I’m experiencing the same thing but with wireless and especially Apple TV. Same log message and the Apple TV report every 5-10 mins that it’s not connected to the network. This started after upgrading my AX88U to 386.2
I’ve experienced it before last year at one point with the previous tree firmware.... not sure of the exact firmware version though.




Apr 21 20:00:55 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:00 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:05 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:10 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:14 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:34 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:40 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:45 kernel: C80:83:E0:633 not mesh client, can't update it's ip
Apr 21 20:01:50 kernel: C80:83:E0:633 not mesh client, can't update it's ip

Strange entries in syslog

I am running 386.2.2 on an AC68U and getting a lot of messages in my syslog like this: Apr 19 07:47:30 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip Apr 19 07:49:01 kernel: D0:C5:D3:28:ED:39 not mesh client, can't update it's ip Apr 19 07:49:01 kernel: 44:39:C4:B7:26:AD not...

www.snbforums.com

 

[DJones]

Strange entries in syslog

I am running 386.2.2 on an AC68U and getting a lot of messages in my syslog like this: Apr 19 07:47:30 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip Apr 19 07:49:01 kernel: D0:C5:D3:28:ED:39 not mesh client, can't update it's ip Apr 19 07:49:01 kernel: 44:39:C4:B7:26:AD not...

www.snbforums.com

Aha!.. so we’re chasing false flags. Thank you for pointing this out. Was concerned one of my devices wasn’t working correctly.