It's likely a guest network. On some routers, under the right conditions, the router will create a guest network using a new IP network, then assign it to a new bridge (br1), rather than making the guest network part of the existing private network (br0).
Not easily. Just use Guest Network 2 and/or 3.I just discovered this as well. Is there any way to configure the LAN segment (to not be .101.xxx) either via the UI or even on the CLI. It seems like YazFi does not play with this very well yet. If one sets YazFi to use a different segment, the clients stay on 101. If You specify 101 is YazFi, it won't start because the segment is already specified.
Is it safe then to say that YazFi does not currently work with the current version then?Not easily. Just use Guest Network 2 and/or 3.
The 192.168.101.0/24 and 192.168.102.0/24 Guest Network 1's were set that way to enable guest WIFI on AiMesh nodes.
Develop branch of YazFi works with 386 (in fact it forces off the Asus isolation)Is it safe then to say that YazFi does not currently work with the current version then?
Also I am noticing that, indeed Guest 1 gets sent to the AiMesh nodes. However, on Guest 2, the clients do get attached back to br0 (so not br1 or a new br2) and Guest 2 is not on the nodes. Am I doing something wrong?
Great to hear! I will be testing that this evening.Develop branch of YazFi works with 386 (in fact it forces off the Asus isolation)
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!