386.5 Alpha1?

[agbommarito]

Did a dirty upgrade of an RT-AX86U access point to alpha2. The logging problem identified in the post below is fixed. And the Google Drive problem I experienced with alpha1 is no longer present.

https://www.snbforums.com/threads/syslog-client-needs-a-push.75644/

 

[ugandy]

a1 -> a2 upgrade. no issues to report.

 

[Zastoff]

Updated from alpha 1 to alpha 2 about 8 hours ago on my ax88u.
Checked log again now, I get spammed with these:

Feb 19 17:03:02 RT-AX88U-6C58 kernel: ** ERROR: [send_redir_page:625] # redir_url=https://192.168.1.1:8443/blocking.asp?cat_id=23&mac=**********23&domain=acds.prod.vidible.tv
Feb 19 17:03:03 RT-AX88U-6C58 kernel: ** ERROR: [send_redir_page:625] # redir_url=https://192.168.1.1:8443/blocking.asp?cat_id=23&mac=**********23&domain=acds.prod.vidible.tv
Feb 19 17:03:04 RT-AX88U-6C58 kernel: ** ERROR: [send_redir_page:625] # redir_url=https://192.168.1.1:8443/blocking.asp?cat_id=23&mac=**********23&domain=acds.prod.vidible.tv
Feb 19 17:03:04 RT-AX88U-6C58 kernel: ** ERROR: [send_redir_page:625] # redir_url=https://192.168.1.1:8443/blocking.asp?cat_id=23&mac=**********23&domain=acds.prod.vidible.tv
Feb 19 17:03:05 RT-AX88U-6C58 kernel: ** ERROR: [send_redir_page:625] # redir_url=https://192.168.1.1:8443/blocking.asp?cat_id=23&mac=**********23&domain=acds.prod.vidible.tv
Feb 19 17:03:07 RT-AX88U-6C58 kernel: ** ERROR: [send_redir_page:625] # redir_url=https://192.168.1.1:8443/blocking.asp?cat_id=23&mac=**********23&domain=acds.prod.vidible.tv
Feb 19 17:03:07 RT-AX88U-6C58 kernel: ** ERROR: [send_redir_page:625] # redir_url=https://192.168.1.1:8443/blocking.asp?cat_id=23&mac=**********23&domain=acds.prod.vidible.tv
Feb 19 17:03:08 RT-AX88U-6C58 kernel: ** ERROR: [send_redir_page:625] # redir_url=https://192.168.1.1:8443/blocking.asp?cat_id=23&mac=**********23&domain=acds.prod.vidible.tv
Feb 19 17:03:08 RT-AX88U-6C58 kernel: ** ERROR: [send_redir_page:625] # redir_url=https://192.168.1.1:8443/blocking.asp?cat_id=23&mac=**********23&domain=acds.prod.vidible.tv
Feb 19 17:03:09 RT-AX88U-6C58 kernel: ** ERROR: [send_redir_page:625] # redir_url=https://192.168.1.1:8443/blocking.asp?cat_id=23&mac=**********23&domain=acds.prod.vidible.tv

Was the same on alpha 1 and i did not get these on 386.4
It only happens with clients i have in DNS-Filter mostly set to use cleanbrowsing-family and NextDNS
(No one is complaining in the family so guess things work anyway on these clients but get spammed in the log..)
Did something change with DNS-Filter since 386.4?
Anyone else seen these?

 

[Deleted member 22229]

Flashed 386.5_A2, AX58U All working good !!

 

[arewhy]

Anxiously awaiting 386.5 Alpha for GT-AX11000. I guess ASUS hasn't provided the GPL for that model yet

 

[Clark Griswald]

Latest alpha survived a Friday night of internet/LAN usage with zero issues!

@arewhy
I see your 11000 and raise with the GT-AXE16000
Since I saw a pic of the GT-AX6000 on somebody's table, I've been waiting for other surprises

 

[Morpheus2020]

Router: AX86U
Version: 386.5_alpha2-g4fa87261ad

Adaptive Qos > Bandwidth Monitor and FlexQoS tabs both report completely wrong or no real-time usage at all, even though 2 devices streaming and system status > internet traffic graph shows correct usage.

if you choose traditional qos it shows correct real time usage so it looks like this issue limited to adaptive qos.

Confirm.
AX86U 386.5 alpha2. Dirty upgrade from 386.4.
Adapitve QOS and FlexQOS 1.3.0 are ON. But it doesn't work at all, like 384 official firmware. The values of Bandwidth Monitor were consistently low.
Dirty downgrade to 386.4. This issues does not exist.
@dave14305

 

[Mutzli]

Dirty update from alpha 1 to 2 and everything is working as expected. Alpha 1 was much better than 386.4, hopefully this continues with alpha 2.

 

[RMerlin]

Updated from alpha 1 to alpha 2 about 8 hours ago on my ax88u.
Checked log again now, I get spammed with these:

The device with the listed MAC address is trying to access the listed site, which is linked to a scam site and therefore is getting blocked by AiProtection. You can see the entry in your AiProtection -> Malicious Website log.

You need to clean that device. The router is simply working as intended here by blocking it.

 

[Zastoff]

The device with the listed MAC address is trying to access the listed site, which is linked to a scam site and therefore is getting blocked by AiProtection. You can see the entry in your AiProtection -> Malicious Website log.

You need to clean that device. The router is simply working as intended here by blocking it.

Think I looked at ai-protect and did not see anything registered there, but will re check that and the devices.
Thanks RMerlin

 

[Ellenswamy]

Question on the Alpha, I have Aimesh going with a AX11000 and AX58u. I know the alpha is not out yet for the AX11000 but it is for the 58u, can I upgrade the 58u and keep the ax on the latest stable with no issues?

 

[Sonyrolfy]

Dirty upgrade with the Alpha2. Reverting dnsmasq from 2.86 to 2.85 gives no more tainted errors. Service state on the VPN client is back as well. Solid!
Thank you Sir!

 

[unsynaps]

Clean load of alpha 2 on AXE11000
factory version -> Merlin version -> factory default and wipe jffs -> configure by hand

Only thing I am running into is the log file getting spammed with events from hostapd.

Feb 19 07:00:49 mpu hostapd: eth6: STA 00:04:20:f1:b4:e7 IEEE 802.11: associated
Feb 19 07:00:49 mpu hostapd: eth6: STA 74:40:bb:6b:ed:2b IEEE 802.11: disassociated
Feb 19 07:00:49 mpu hostapd: eth6: STA 74:40:bb:6b:ed:2b IEEE 802.11: disassociated
Feb 19 07:00:52 mpu hostapd: eth6: STA 74:40:bb:6b:ed:2b IEEE 802.11: associated
Feb 19 07:00:53 mpu hostapd: eth6: STA 00:04:20:f1:b4:e7 IEEE 802.11: disassociated
Feb 19 07:00:53 mpu hostapd: eth6: STA 00:04:20:f1:b4:e7 IEEE 802.11: disassociated
Feb 19 07:00:56 mpu hostapd: eth6: STA 74:40:bb:6b:ed:2b IEEE 802.11: disassociated
Feb 19 07:00:56 mpu hostapd: eth6: STA 74:40:bb:6b:ed:2b IEEE 802.11: disassociated
Feb 19 07:00:59 mpu hostapd: eth6: STA 74:40:bb:6b:ed:2b IEEE 802.11: associated
Feb 19 07:01:03 mpu hostapd: eth6: STA 74:40:bb:6b:ed:2b IEEE 802.11: disassociated
Feb 19 07:01:03 mpu hostapd: eth6: STA 74:40:bb:6b:ed:2b IEEE 802.11: disassociated

I am guessing eth6 is one of the wireless interfaces and something is being an butt connecting or whatever.
Going to wrangle it in with scribe later.

EDIT: Hon Hai Precision Ind. Co.,Ltd.
EDIT: FoxCon
EDIT: Meh been up all night. Gonna dig some more after some sleep.

Well it seems that device is just my wireless P-Touch label printer spazzing out.

EDIT: Oh FYI it is because the wrong password was in the unit. It just kept retrying to connect over and over and over and over...

 

[Zastoff]

The device with the listed MAC address is trying to access the listed site, which is linked to a scam site and therefore is getting blocked by AiProtection. You can see the entry in your AiProtection -> Malicious Website log.

You need to clean that device. The router is simply working as intended here by blocking it.

Now checked again AiProtection - Malicious Sites Blocking = No Event Detected
And scanned 2 devices (2 windows 10 pc) that spammed the log, Scanned with Malwarebytes and windows defender and nothing found.
The devices is on my guest network (2) with Access Intranet = disable and they are set on dns-filter to use cleanbrowsing-family or nextdns

 

[Sander_H]

There is something peculiar with the AC68U alpha2 build. It is huge, over twice the normal size: 88 vs 34 mb.

 

[bennor]

There is something peculiar with the AC68U alpha2 build. It is huge, over twice the normal size: 88 vs 34 mb.

The stock Asus firmware (FW_RT_AC68U_300438646065) is also 98 mb. It was said elsewhere, when I searched for the size difference explanation this morning, that sometimes the size difference in Merlin firmware is due to the larger file having firmware for two or more models. There is an AC68U_V4 model apparently.

 

[RMerlin]

Now checked again AiProtection - Malicious Sites Blocking = No Event Detected
And scanned 2 devices (2 windows 10 pc) that spammed the log, Scanned with Malwarebytes and windows defender and nothing found.
The devices is on my guest network (2) with Access Intranet = disable and they are set on dns-filter to use cleanbrowsing-family or nextdns

Then there is an AiProtection logging issue. The log entry is clear as to what is going on, something on that device is trying to connect to that specified site, and that site is blocked by AiProtection. This has nothing to do with the DNS configuration.

A quick search seem to indicate this might come from a Chrome plugin.

 

[Zastoff]

Then there is an AiProtection logging issue. The log entry is clear as to what is going on, something on that device is trying to connect to that specified site, and that site is blocked by AiProtection. This has nothing to do with the DNS configuration.

A quick search seem to indicate this might come from a Chrome plugin.

Will check that out tomorrow.
Thank you again RMerlin

 

[ComputerSteve]

What about GT-AX11000?

Coming soon?

I was gonna ask where’s the GT-AX11000

 

[SheikhSheikha]

Alpha2 is a rock solid foundation!