@UKTechHub
.
.

Reply To: 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…

UKTH forums 🛜 Wireless Routers & Modems ASUS & Wireless 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... Reply To: 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…

#37931
Avatarxt8user
  • Replies 13
  • New Here

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 Avatarxt8user.
Latest Posts