it seems that aiprotection not work in this version....
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 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.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.
this site is blocked, but no info in router aiprotection/malicious sites blocking.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....
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.
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.
any ideas of what it meas or where i can find more info on these log msgs?
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.They're just reports of wireless clients associating/disconnecting from the router.
Maybe updating the weather data every minute?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
ok then, i'll live with it.The frequency seems very regular indeed, I suspect the device is possibly disconnecting and reconnecting every 30 secs or so.
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.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!