Release Asuswrt-Merlin 386.2 is now available

[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.

 

[m0rF1uS]

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

I’m aware of that and generally don’t pay attention to logs and they don’t bother me. However here the issue is that before the update to 386.2 I did not have any problems with the Apple TV getting disconnected randomly from the network. And it does it multiple times in a roll. MAC address from the log matched the Apple TV and once I turn it on after a few minutes it starts to disconnect and connect to the network every couple minutes.
i did full factory reset after upgrading to 386.1 and then a dirty update to 386.2.
problem was not present when i was running 386.1 but it is when running 386.2
also experienced the same issue with one of the firmware releases last year on the 384 tree.

this is the only other thing I can find in the logs that is for the same device:

Apr 20 21:52:12 miniupnpd[1950]: upnp_event_process_notify: connect(192.168.50.56:2869): Connection timed out
Apr 20 21:52:12 miniupnpd[1950]: upnp_event_process_notify: connect(192.168.50.56:2869): Connection timed out
Apr 20 21:52:12 miniupnpd[1950]: upnpevents_processfds: 0x7c9f00, remove subscriber uuid:2d70d272-1b71-498b-9233-5735a897b0b3 after an ERROR cb: http://192.168.50.56:2869/upnp/eventing/ccaaemxtha

 

[gattaca]

^^^ This recent thread covered that miniupnpd being stealthily re-activated and how it must be turned off in several places on the routers and the newer routers added yet another place to deactivate *@(*@* upnp which is a valid high security concern to turn off and keep off.

https://www.snbforums.com/threads/r...pletely-disable-upnp.70041/page-2#post-672419

IDK why your apple devices are having problem. I have all ours set to not do that "private" MAC address each time they connect...

 

[MvW]

I have upnp disabled and I don't have any disconnects on either of our AppleTV's (on is a 3rd gen and the one in the living room is 4K version). As a matter of fact, I haven't seen that log message for days now. I had (ui)Scribe and syslog-ng installed to filter out the noise, but I had to remove them because without it was easier to troubleshoot an issue in chronological order rather than in separate logfiles and I haven't seen the message return nor have I experienced (or seen... I do like staring at logfiles) any disconnects. For all iPhones and iPads the private network has been turned of for my home network (2 SSID's) and for others it has been left on. Both AppleTV's are hardwired to the nearest switch so to be honest, I haven't even seen the option there.