What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

YazFi guest clients not shown in client list - problems with NetAlertX

HeeroYuy

Occasional Visitor
Hi.
I have YazFi v4.4.4. running on a GT-AXE16000 with Merlin 3004.388.8_2_rog. YazFi itself works fine, I can see my guest clients in the YazFi-section.
But they don't appear in the client list from the asus gui.
YazFi:
1737412912683.png

Client list:
1737412931886.png

But the guests can be found even with tools like NetSetMan:
1737412967931.png


So my question: Is this behavior intended or a bug in the client list / code?
Reason: I'm using NetAlertX from jakob-sk and the ASUSWRT-plugin from labmonkey. They both work fine but the ASUS plugin relies on the client list from an ASUS router.
It would be great if the clients can be shown in the original client list or someone has ideas how to detect the guest networks with NetAlertX.

And yes, communication from private network into guest networks is allowed, but not vice versa. And guest clients are isolated.
But guests are using my PiHole in the private network.

Good night folks.
 
So my question: Is this behavior intended or a bug in the client list / code?
Standard behavior. The YazFi clients will show up; in the router GUI System Log > Wireless Log page, in the YazFi Gui page, and in the YazFi CLI page (via SSH). And it will show up if one uses SSH to issue the cat /var/lib/misc/dnsmasq.leases command. YazFi clients generally will not show up in the Network Map listings because it's IP addresses are a different IP address subnet from the firmware's main LAN IP subnet.

Edit to add: It's a question that gets asked from time to time. For example a couple of past posts about it...
https://www.snbforums.com/threads/yazfi-guests-showing-in-main-network-map.77882/#post-754320
https://www.snbforums.com/threads/yazfi-v4-x-continued.83846/#post-826676
2. is well known, Asus Network Map only shows devices on the same subnet/network
 
Last edited:
ah okay thanks. but the info with the ssh connection and reading the dhcp.leases is a good entry point. I'll suggest this to the dev of the asus-wrt plugin.
 
I'll suggest this to the dev of the asus-wrt plugin.
YazFi is no longer being actively developed by the developer.
https://www.snbforums.com/threads/dhcp-list-max-limit-increased.79634/#post-775042
I pop up occasionally, but since I moved to pfSense and UniFi, and my Asus routers decided to give up the ghost, I'm not actively developing anymore. I chime in on support requests when I have time as well
The developer was well aware of the issue since it came up from time to time in the main YazFi script discussion topic. It is possible that the Network Map and related firmware code are closed source and if so couldn't be modified to include the YazFi IP address subnet ranges.
PS: Its just a quirk one learns to live with when using YazFi. When using YazFi one can simply invoke the cat /var/lib/misc/dnsmasq.leases command via a SSH batch file script (using Plink on Windows) to quickly see the connected clients without opening the GUI and going to the Wireless Log page or YazFi page.
 
Last edited:
Yeah I'm aware of it but as long as I haven't the time or money for a selfmade router, I'll stick to my Asus until it dies.
So grabbing the dnsmasq.leases would be a good implementation in NetAlertX
 

Similar threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Back
Top