[xt8user]

It’s been a couple of weeks since I sent in that feedback and I have not received anything back from ASUS.

If you have time, could you check in with them and see if they have any plans to fix the issue?

Thanks!

 

• This reply was modified 10 months, 1 week ago by xt8user.

Liked by:

You need to login in order to vote

[xt8user]

I tried it again this morning and this time the feedback appears to have submitted successfully.

You need to login in order to vote

[xt8user]

I’ve submitted the feedback via the GUI.  No idea if it actually made it since the XT8 crashed about 20 secs after submitting the Feedback.  I did use the same email address as I use here.

This is what I got in the logs:

Jun 2 16:38:41 rc_service: cfg_server 4575:notify_rc restart_sendfeedback
Jun 2 16:38:41 frs_feedback: start_sendfeedback() start…
Dec 31 19:00:30 crashlog: LOG
Dec 31 19:00:30 crashlog: <4>
Dec 31 19:00:30 crashlog: <4>Port Shaper: kbps 2497500, mbs 150000, tokens 31218, bucket_size 196827, bucket 20750
Dec 31 19:00:30 crashlog: <4>PORT[0][00]: Level 0/1024, Writes 0, Write Bytes 0, Bypasses 0, Bypass Bytes 0, Reads 0, Retries 0, Discards 0, Discard Bytes 0, Writes+Bypasses+Discards 0

You need to login in order to vote

[xt8user]

I will certainly do a feedback. What is the correct link to use?

Liked by:

You need to login in order to vote

[xt8user]

No it does not, the “custom” static ip route entry is lost on reboot or if the static route table is changed via the GUI.

I added the ip route add command from my post above to services-start and that works just fine (though this does not cover all potential failure cases based on what I’ve read). 

The services-start addition gives me a workable solution using Merlin/Gnuton but I’m not aware of one for stock software.

Any chance you can pass this “upstairs” to ASUS to see if they have any interest in fixing it?

BTW as someone who also worked on Cisco stuff back in the mists of time, “Cisco had a GUI?”

Andrew

 

Liked by:

You need to login in order to vote

[xt8user]

I have “fallen” on an interesting issue related to static routes.  The same issue occurs both in stock XT8 software and 3004.388.8_4-gnuton1.

What I am trying to do is add a static route to a router connected to VLAN 503 on Guest Network 1.

If I add a static route using the web gui to an IP address on the “Non Guest” part of the router (say 192.168.48.4) then every thing works normally. A route is created in the gui and a matching entry created in the route table.  If however I point a static route at a device in the guest 1 network (in this case 192.168.103.250) the route appears to be created in the gui (see attached) however looking at route -n no route is actually created and a bunch of the following error is generated.

Jun 2 06:54:07 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,1015: interface 24 could not be found^[[0m
Jun 2 06:54:07 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,1015: interface 24 could not be found^[[0m
Jun 2 06:54:07 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,1015: interface 24 could not be found^[[0m

If however, I delete the static route from the gui and add it via ssh with:

ip route add 192.168.20.0/24 via 192.168.103.250

The route is created correctly and everything works correctly.  As expected the web gui is “unaware” of this route (even though it works just fine).

Here is a snippet from the route table (route -n) (note the 81.0 subnet is created by OpenVPN):

192.168.20.0    192.168.103.250 255.255.255.0   UG    0      0        0 br3
192.168.48.0    0.0.0.0         255.255.252.0   U     0      0        0 br0
192.168.81.0    0.0.0.0         255.255.255.0   U     0      0        0 tun21
192.168.102.0   0.0.0.0         255.255.255.0   U     0      0        0 br2
192.168.103.0   0.0.0.0         255.255.255.0   U     0      0        0 br3

It appears that the gui is getting “confused” when it tries to create the route however the rest of the system is “happy”.

Any thoughts appreciated.

 

• This reply was modified 10 months, 3 weeks ago by xt8user.

Attachments:

1. 

   Screenshot-2025-06-02-at-6.56.30 AM.png
   

You need to login in order to vote

[xt8user]

UK Sentinel wrote:

I also have some background information which may help other ASUS ZenWifi XT8 owners. ASUS ZenWifi XT8 Details

1. The ASUS ZenWifi XT8 can support upto 9 wireless AiMesh Nodes
2. The ASUS ZenWifi XT8 can support upto a theoretical maximum number of wifi clients.
   1. 2.4G: 128 wifi clients
   2. 5G-1: 128 wifi clients
   3. 5G-2: 64 wifi clients

‘note: this is a theoretical maximum ‘

Are those limits per XT8 system (router plus all nodes) or per XT8 unit?

 

Liked by:

You need to login in order to vote

[xt8user]

I tried 3.0.0.4.388_22525 for a week or so (clean install) plus several reboots but have now gone back to 3.0.0.4.386_49873. I was getting a number of devices on 2.4Ghz (both Wemo switches and Raspberry Pis) that were periodically inaccessible (a restart of the individual device fixed the issues) plus substantial variation in ping times and (some) packet loss which was not there before to devices with good RF signal.  This is using the same 2.4Ghz channel (11) on both releases.  I also saw on two occasions that after a software reboot of the router node the connection to the cable modem did not go in service (LED stayed red).  A power-cycle of the router node fixed the issue, but another restart got me back to the same point (red LED, needing a power-cycle).

Reverting back to 3.0.0.4.386_49873 resolves all of these issues.  I typically manually restart this configuration about once a month (just because) however it has been entirely stable for me.  (Note: I use Ethernet backhaul, external DHCP/DNS Servers and do not use any of the Parental Control, AIProtection (or similar) features.

I have a router + 2 mesh node system with approx 120 total devices with about 80 of those wireless.

Liked by:

You need to login in order to vote

[xt8user]

I do not see that accessing the support site from the US.  The latest release shown is 3.0.0.4.388.21617.  I also have a V1 system. (It says HW Ver.: 1.0 on the label on the bottom).

However if I VPN using a node in the UK (Southampton) and do the same I see the 22068 release however it says it is for V1 hardware now (see the attached).

It’s fair to say I’m a little confused!

Attachments:

1. 

   IMG_0635.png
   

You need to login in order to vote

[xt8user]

What do we know about version 3.0.0.4.388.22068? It is being offered by the iOS App and via the XT8 Web UI however it does not appear on the ASUS website?

 

You need to login in order to vote

[xt8user]

xt8user wrote:

UK Sentinel wrote:

Load 386.49873 to Nodes and reboot and then load 386.49873 to Primary and reboot. This should work but if you notice any issues, then option 2 will be required. This should not break mesh as you are using ethernet

I notice you don’t mention loading the 386.49873 backup in option 1. Do you feel that is not useful? Thanks for your help.

Thanks for your assistance with this.  The “downgrade” in the order you mentioned plus restoring the previously saved configuration for that release seemed to have worked just fine. I’m back on 386.49873 now.

You need to login in order to vote

[xt8user]

UK Sentinel wrote:

Load 386.49873 to Nodes and reboot and then load 386.49873 to Primary and reboot. This should work but if you notice any issues, then option 2 will be required. This should not break mesh as you are using ethernet

I notice you don’t mention loading the 386.49873 backup in option 1.  Do you feel that is not useful?

Thanks for your help.

Liked by:

You need to login in order to vote

[xt8user]

I have 3 XT8s (1 router, 2 nodes) currently on 388.21099. They are Ethernet connected. I would like to go back to 386.49873. I have a backup of the 386.49873 configuration. What is the best sequence of downgrading the units, reloading the saved database etc?

Thanks in advance.

You need to login in order to vote

[Author]

Posts