ASUS ZenWiFi AX Whole Home Tri-Band Mesh WiFi 6 System Not sure if this is the right place to ask…. I am thinking of upgrading my Google Mesh wifi to the above. Has anyone used this and does it...

[UK Sentinel]

dodgydrains wrote:

Feedback sent, the wireless backhaul went down again and recovered.   I mentioned you in the comments.  The uptime did not reset.

Where all your XT8 using 21617 ?

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[dodgydrains]

UK Sentinel wrote:

dodgydrains wrote:

Feedback sent, the wireless backhaul went down again and recovered. I mentioned you in the comments. The uptime did not reset.

Where all your XT8 using 21617 ?

Yes, all on latest official 21617

You need to login in order to vote

[UK Sentinel]

dodgydrains wrote:

Yes, all on latest official 21617

Great news

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[Jacky Decoster]

hi all,

Tried 3.0.0.4.388.21617 today, but reverted back to 3.0.0.4.386.49873.

• Several ‘Teams meeting’ dropouts
• Several RDP session dropouts.

reminds me of older firmwares that had the same issue.

so, unfortunately : NOGO for me.

Liked by:

You need to login in order to vote

[Comoman]

Jacky Decoster wrote:

hi all, Tried 3.0.0.4.388.21617 today, but reverted back to 3.0.0.4.386.49873.

• Several ‘Teams meeting’ dropouts
• Several RDP session dropouts.

reminds me of older firmwares that had the same issue. so, unfortunately : NOGO for me.

Interesting – I’m also on 21617 and have no issues with Teams.  Consistently inconsistent!

Liked by:

You need to login in order to vote

[UK Sentinel]

Jacky Decoster wrote:

so, unfortunately : NOGO for me.

Totally understandable, is your Adaptive QOS  ‘Learn from Home’ still enabled ?

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[dodgydrains]

Comoman wrote:

Jacky Decoster wrote:

hi all, Tried 3.0.0.4.388.21617 today, but reverted back to 3.0.0.4.386.49873.

• Several ‘Teams meeting’ dropouts
• Several RDP session dropouts.

reminds me of older firmwares that had the same issue. so, unfortunately : NOGO for me.

Interesting – I’m also on 21617 and have no issues with Teams. Consistently inconsistent!

Are you using wired or wireless backhaul?

You need to login in order to vote

[Jacky Decoster]

wireless backhaul : one base-station, one satelite. (V1 – hardware)

internet connection through company VPN (F5 / big ip edge client)

You need to login in order to vote

[dodgydrains]

It will be good to see if Comoman is wired or wireless too

You need to login in order to vote

[Comoman]

dodgydrains wrote:

It will be good to see if Comoman is wired or wireless too

Wireless.

You need to login in order to vote

[UK Sentinel]

dodgydrains wrote:

After exactly 1 day and 8 hours the wireless backhaul went down and then recovered.  These are the logs for the time it happened, not sure if it shows anything, should I send feedback?

ASUS have come back to myself and say they have your feedback and are looking at the logs

In a completely sane world, madness is the only freedom (J.G.Ballard).

Liked by:

You need to login in order to vote

[lifeisfun]

Hi folks, new to the forum …

My 1 year XT8 started to throw this error very often in the log

RMerlin on another forum gave me this explanation:

“Archer is Boradcom`s proprietary NAT accelerator, only they know what any of these cryptic messages mean. Quite often they are just debug output, not actual error conditions.”

https://www.snbforums.com/threads/xt8-kernel-error.81904/

Anyone experienced this?

Thanks

 

It repeats over and over …

Nov 24 07:01:02 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Nov 24 07:06:00 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Nov 24 07:07:31 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind xx:xx:xx:xx:xx:E8, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Nov 24 07:07:43 wlceventd: wlceventd_proc_event(530): eth4: Auth xx:xx:xx:xx:xx:E8, status: Successful (0), rssi:0
Nov 24 07:07:43 wlceventd: wlceventd_proc_event(559): eth4: Assoc xx:xx:xx:xx:xx:E8, status: Successful (0), rssi:-58
Nov 24 07:13:19 acsd: acs_build_candidates(731): eth6: number of valid chanspec is 0
Nov 24 07:19:01 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Nov 24 07:27:10 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind xx:xx:xx:xx:xx:E8, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Nov 24 07:27:25 acsd: acs_build_candidates(731): eth6: number of valid chanspec is 0
Nov 24 07:41:31 acsd: acs_build_candidates(731): eth6: number of valid chanspec is 0
Nov 24 07:42:47 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Nov 24 07:45:38 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Nov 24 07:52:02 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Nov 24 07:55:37 acsd: acs_build_candidates(731): eth6: number of valid chanspec is 0
Nov 24 08:02:46 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Nov 24 08:09:19 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Nov 24 08:09:43 acsd: acs_build_candidates(731): eth6: number of valid chanspec is 0
Nov 24 08:22:34 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Nov 24 08:23:49 acsd: acs_build_candidates(731): eth6: number of valid chanspec is 0
Nov 24 08:24:21 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m

You need to login in order to vote

[UK Sentinel]

I can ask ASUS XT8 team if you wish to see if they may know more ?

is the below the actual log type messages you are interested in knowing more about …

——–

Nov 24 08:09:19 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m

——–

In a completely sane world, madness is the only freedom (J.G.Ballard).

Liked by:

You need to login in order to vote

[lifeisfun]

That would be great!

Yes it is.

Would it be better to send you link to the actual saved log file?

Thanks

Liked by:

You need to login in order to vote

[UK Sentinel]

I will see what ASUS say, I am sure it is nothing to worry about and more annoying keep seeing that repetitive log message and would be interesting if others are seeing this also.

But as you say, RMerlin is probable correct and relates to NAT accelerator and is meaningless to us users, but no harm in checking

In a completely sane world, madness is the only freedom (J.G.Ballard).

Liked by:

You need to login in order to vote

[Author]

Posts