YazFi YazFi -- "Not in Guest Net" ??

[copperhead]

I am experiencing an issue with a new smart plug (Kasa HS103) on my ASUS router running YazFi. The plug initially connected to the guest network (192.168.2.141) and worked fine, but after enabling "Client Isolation" in YazFi and restarting, the smart plug was listed as "Not in Guest Net." Its IP address then changed to 192.168.1.141, which is part of the main LAN.

Even though the plug has never connected to the main LAN, it appears to be receiving an IP from the main network’s DHCP pool instead of the guest pool.

Steps I’ve tried:

• Reverted “Client Isolation” back to NO, but the issue persists.
• Factory reset the smart plug, but the problem remains.
• Tried various iptables and ebtables rules, but nothing seems to block the main LAN DHCP from assigning it an IP.
• Removed dnsmasq.leases
• No other device set to the Guest Network has experienced the same problem; only the Kasa Smart Plug has had this issue.

Can anyone provide insights into why YazFi is not assigning the smart plug an IP from the guest pool and why it's still able to get one from the main LAN’s DHCP? Any advice would be appreciated!

 

[bennor]

Where are are you seeing it indicated "Not in Guest Net"? In the router GUI, or in the IoT device's app/interface?
Does the YazFi GUI page indicate the problematic IoT device is connected?
Does the YazFi CLI interface indicate the problematic IoT device is connected?
Does the System Log > Wireless page indicate the problematic IoT device is connected, if so to which WiFi band/network?
Have you previously configured a manual IP or static IP address for the problematic IoT device?

Also, if you haven't done so already, you may want to search the Asus-Merlin Addon subforum for other YazFi discussions to see if any of the other YazFi discussions have any suggestions.
https://www.snbforums.com/forums/asuswrt-merlin-addons.60/?prefix_id=13

And to confirm, you are not using AiMesh or AP nodes with the RT-AX88U Pro correct? YazFi doesn't work on AiMesh nodes, it only works on the main router.

 

[copperhead]

Where are are you seeing it indicated "Not in Guest Net"? In the router GUI, or in the IoT device's app/interface?

I'm see the message, "Not in Guest Net", in the Router GUI specifically under Guest Network > YazFi where it lists the connected devices:

Does the YazFi GUI page indicate the problematic IoT device is connected?

YES, YazFi does indicate the device is connected (see snapshot, above). Furthermore, under System Log > Wireless Log i do see the device's MAC listed under Guest Network 1 (which is what I'd expect) but the IP Address belongs to the wrong subnet. Yazfi Guest Network is 192.168.2.0/24. FTR the Guest Network 1 is 2.4 GHZ band

Does the YazFi CLI interface indicate the problematic IoT device is connected?

Using AMTM and launching YazFi then selecting "Show connected clients using YazFi" i do see an identical listing as what i saw within the router GUI (first snapshot above) -- the HS103 device IP is showing as "Not in Guest Net". The MAC is correct, Connected Time is 15 hrs, etc.

Does the System Log > Wireless page indicate the problematic IoT device is connected, if so to which WiFi band/network?

Yes, 2.4 GHZ. The SSID is my Guest Network SSID

Have you previously configured a manual IP or static IP address for the problematic IoT device?

I believe i did for the first IoT device but a few months back dropped it. Since then I've factory reset the first IoT device but it still would get the exact same IP. I also purchased a second similar IoT device (different MAC) unknown to my system, no static IP whatsoever but the exact same issue has occurred for it too. Both IoT devices are experiencing this "Not in Guest Net" problem.

Also, if you haven't done so already, you may want to search the Asus-Merlin Addon subforum for other YazFi discussions to see if any of the other YazFi discussions have any suggestions.
https://www.snbforums.com/forums/asuswrt-merlin-addons.60/?prefix_id=13

Thank you!

And to confirm, you are not using AiMesh or AP nodes with the RT-AX88U Pro correct? YazFi doesn't work on AiMesh nodes, it only works on the main router.

No. I only have my single Asus RT-AX88U Pro router which YazFi is running on. Nothing complicated beyond the few scripts running.

 

[bennor]

As a troubleshooting step. Try using Guest Network #2 rather than Guest Network #1. Asus handles Guest Network #1 slightly differently due to it's use for AiMesh (even when not using AiMesh).

If you haven't already done so, make sure to update the Kasa HS103 to it's latest firmware. Check the TP-Link support forums, if you haven't done so already, to see if they have any suggestions.

What are your 2.4Ghz WiFi settings? As a troubleshooting step, try setting the 2.4Ghz Channel Bandwith to 20MHz and try selecting a specific Control Channel. Another troubleshooting step some have tried when having issues with the 2.4Ghz band is setting the Wireless Mode to Legacy.

Don't recall ever seeing the "Not in Guest Net" message before in YazFi.

 

[dave14305]

YazFi will give that message when it cannot find the MAC address in /var/lib/misc/dnsmasq.leases.

 

[Ripshod]

I see this message as well, usually straight after a reboot or if I restart the wifi. In my case though things do settle down and correct themselves.
As @dave14305 suggests dnsmasq.leases would by my main suspect. Whether it's being corrupted (bad ram) or the info is being entered incorrectly in the first case I cannot guess.

 

[bennor]

YazFi will give that message when it cannot find the MAC address in /var/lib/misc/dnsmasq.leases.

If that is the case, wonder if manually adding a fixed/manual DHCP IP address reservations for their Kasa HS103 smart plugs would help @copperhead?
https://github.com/jackyaz/YazFi/wi...verse-DNS-records#a-note-on-dhcp-reservations
https://www.snbforums.com/threads/y...inc-ssid-vpn-client.45924/page-32#post-473403

I always used manual IP reservations for my YazFi clients in recent years so it's possible that could be why I never saw the "Not in Guest Net" message in the YazFi interface (CLI or GUI).

 

[dave14305]

wonder if manually adding a fixed/manual DHCP IP address reservations for their Kasa HS103 smart plugs would help

It probably means the device hasn’t requested to renew its lease since dnsmasq was last restarted.