ASUS RT-AC86U firmware release 3.0.0.4.384.45149 12/05/2018

[VANT]

it seems that aiprotection not work in this version....

 

[RMerlin]

it seems that aiprotection not work in this version....

How are you testing it?

 

[OzarkEdge]

Any gamers trying to use this firmware with AIMesh? It's most noticeable when you drop out in games. It's not as bad as previous versions where the drop out results in 3-8 minutes of no wifi. In the latest iteration, the drop appears to be more in the 5-20s range (which is still terrible for online games but less noticeable in streaming environments with buffering).

I have a desktop PC directly connected to the AiMesh Node, and when the signal goes out, I'm unable to access to the main router page (easiest sign that it was a router issue).

I'd be interested in you performing my test to see if your issue is similar to mine prior to 45149...

I assume your desktop PC connection to the node is wireless.

Open the MS Windows connection status for your wireless connection to observe the connection link rate (it's labeled Speed... harder to find on Win10). A solid ac link rate should be pegged at 866 Mbps (or 433 depending on the streams/antennas supported).

Then run speedtest.net (or similar) repeatedly while observing the MS Windows wireless connection link rate. Does the link rate hold steady, or does it droop or even drop completely?

And for reference, what are your nominal ISP speeds down/up?

OE

 

[VANT]

How are you testing it?

i try open some malicious sites. Some is opened without any problems, some not, but no info about this in aiprotection/"Malicious sites blocking" and other.

 

[Datalink]

Try the following Trend Micro test site:

https://success.trendmicro.com/solu...the-web-reputation-feature-in-officescan-osce

Only the first three sites work for test purposes.

 

[RMerlin]

i try open some malicious sites. Some is opened without any problems, some not, but no info about this in aiprotection/"Malicious sites blocking" and other.

Do a search for WICAR. The WICAR website is a special test site which does get blocked for me when I enable Malicious Website blocking (on a different firmware release).

 

[VANT]

Do a search for WICAR. The WICAR website is a special test site which does get blocked for me when I enable Malicious Website blocking (on a different firmware release).

this site is blocked, but no info in router aiprotection/malicious sites blocking.
All counters under aiprotection is 0....

 

[RMerlin]

this site is blocked, but no info in router aiprotection/malicious sites blocking.
All counters under aiprotection is 0....

Could be a bug in 45149 then, I know Asus were looking into a few things related to Trend Micro's engine in that release. My firmware isn't affected because I'm still based on older firmware code.

 

[Scansbar]

Just to chime in, i also get the same errors in my logs and notice that my mesh drops once every few days. Sometimes in the wifi log my 5ghz shows no connections, until I reboot the main router. Guess I'll deal with it until the next update.... been an asus fan for a long time but sense change in the future.

 

[OzarkEdge]

As I see it, the change is mesh systems or whatever product that brings universal wireless networking to consumers. If it's not AiMesh at home (for now), what is it and is that any less troublesome/desirable (for now)?

AiMesh with wireless backhaul is working better for me than a repeater.

OE

 

[mogulman]

i try open some malicious sites. Some is opened without any problems, some not, but no info about this in aiprotection/"Malicious sites blocking" and other.

I get notifications, but I noticed the same thing. The aiprotection page doesn't show the number of malicious attempts since I updated.

 

[Tonycv51]

These messages appear to be documenting when devices join or leave the wireless networks. ASUS didn't seem to be logging this information in previous firmwares. Maybe it was accidental for this firmware.

I use the WHAALE app to airplay to multiple devices from my iphone. It was always rock solid but the music now frequently cuts out, reverts to the phone speaker, and then restarts on the target airplay device(s). I can't be precise but my suspicion is that the dropouts are due to the disassoc/reassoc around the same time on the logs for the iphone MAC address.

Note the only wifi in the equation is the iphone - the airplay devices are wired

 

[128bit]

not to take over the thread but not only do i see the kernal msgs in the log i also see this -
Dec 24 10:38:23 WLCEVENTD: wl0.1: Assoc 5C:CF:...
Dec 24 10:39:23 WLCEVENTD: wl0.1: Disassoc 5C:CF:...

any ideas of what it meas or where i can find more info on these log msgs?

also, i have trend micro disabled. didn't even agree to the eula, and i'm soft-crashing with similar msgs but it's rare. and not many new connections happen that often. also, ipv6 is disabled.

 

[RMerlin]

any ideas of what it meas or where i can find more info on these log msgs?

They're just reports of wireless clients associating/disconnecting from the router.

 

[128bit]

They're just reports of wireless clients associating/disconnecting from the router.

well sir, the frequency is disturbing. granted it's a la crosse weather station but i've never seen these prior to the last update.

Dec 25 14:24:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:24:43 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:24:43 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:26:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:26:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:27:01 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:27:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:28:02 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:28:02 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:29:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:29:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:30:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:30:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:31:22 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:31:22 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:32:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:32:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:33:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:33:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:34:42 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:34:42 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:35:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:35:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:36:03 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:36:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:37:03 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:38:02 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:38:24 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:38:24 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:39:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:39:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:41:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:41:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:42:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:42:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:44:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:44:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:44:43 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:44:43 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:45:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:45:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:47:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:47:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:48:02 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:48:02 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:48:26 WLCEVENTD: wl0.1: Disassoc 5C:CF​

seems a bit excessive to me even for a weather/clock device. btw, no other devices show this pattern when connecting.

thanks much

 

[Centrifuge]

well sir, the frequency is disturbing. granted it's a la crosse weather station but i've never seen these prior to the last update.

Dec 25 14:24:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:24:43 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:24:43 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:26:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:26:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:27:01 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:27:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:28:02 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:28:02 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:29:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:29:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:30:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:30:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:31:22 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:31:22 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:32:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:32:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:33:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:33:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:34:42 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:34:42 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:35:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:35:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:36:03 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:36:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:37:03 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:38:02 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:38:24 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:38:24 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:39:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:39:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:41:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:41:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:42:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:42:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:44:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:44:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:44:43 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:44:43 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:45:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:45:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:47:21 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:47:21 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:48:02 WLCEVENTD: wl0.1: Disassoc 5C:CF:
Dec 25 14:48:02 WLCEVENTD: wl0.1: Assoc 5C:CF:
Dec 25 14:48:26 WLCEVENTD: wl0.1: Disassoc 5C:CF​

seems a bit excessive to me even for a weather/clock device. btw, no other devices show this pattern when connecting.

thanks much

Maybe updating the weather data every minute?

 

[RMerlin]

The frequency seems very regular indeed, I suspect the device is possibly disconnecting and reconnecting every 30 secs or so.

 

[128bit]

The frequency seems very regular indeed, I suspect the device is possibly disconnecting and reconnecting every 30 secs or so.

ok then, i'll live with it.
thanks much

 

[kew]

not to take over the thread but not only do i see the kernal msgs in the log i also see this -
Dec 24 10:38:23 WLCEVENTD: wl0.1: Assoc 5C:CF:...
Dec 24 10:39:23 WLCEVENTD: wl0.1: Disassoc 5C:CF:...

any ideas of what it meas or where i can find more info on these log msgs?

also, i have trend micro disabled. didn't even agree to the eula, and i'm soft-crashing with similar msgs but it's rare. and not many new connections happen that often. also, ipv6 is disabled.

I had that same, until I removed the
roaming assistant
Test it.

 

[tallytr]

I had that same, until I removed the
roaming assistant
Test it.

Why would you remove the roaming assistant? Isn't that what AiMesh is all about?