Asus Router RT-AC88U: Merlin 386.2
AirMesh Node RT-AC68U: 3.0.0.4.386_41634-g08f88ae
YazFi: v4.2.0
Not sure when this started happening, i just happened to notice it after i applied the 386.2 update. What i found some times is that clients on guest network get the 192.168.1.0/24 subnet. YazFI is configured to use 192.168.2.0/24 (2.4GHz) and 192.168.5.0/24 (5GHz).
If i bound the client to the main router then it would get the correct subnet and ip on the device confirmed that (however the UI still shows the IP addr in 192.168.1.0/24 subnet.) and yazfi cli shows it as a connected client. If the client was bound to the airmesh node ip shown on the device was in 192.168.1.0/24 subnet and i could see dns queries from this device showing up in my local dns server which guest network does not have access to.
I have seen this happen with a couple of devices that always connect to guest network and sometimes they get the ip in the correct subnet and some times they do not.
I have also tried restarting the router and the airmesh node and it did not help. I was curious if any one else has seen this? and if any one has any pointers on how i could fix this.
AirMesh Node RT-AC68U: 3.0.0.4.386_41634-g08f88ae
YazFi: v4.2.0
Not sure when this started happening, i just happened to notice it after i applied the 386.2 update. What i found some times is that clients on guest network get the 192.168.1.0/24 subnet. YazFI is configured to use 192.168.2.0/24 (2.4GHz) and 192.168.5.0/24 (5GHz).
If i bound the client to the main router then it would get the correct subnet and ip on the device confirmed that (however the UI still shows the IP addr in 192.168.1.0/24 subnet.) and yazfi cli shows it as a connected client. If the client was bound to the airmesh node ip shown on the device was in 192.168.1.0/24 subnet and i could see dns queries from this device showing up in my local dns server which guest network does not have access to.
I have seen this happen with a couple of devices that always connect to guest network and sometimes they get the ip in the correct subnet and some times they do not.
I have also tried restarting the router and the airmesh node and it did not help. I was curious if any one else has seen this? and if any one has any pointers on how i could fix this.