starred/uspot

Fork 0

mirror of https://github.com/f00b4r0/uspot.git synced 2026-04-25 22:25:51 +03:00

[GH-ISSUE #31] uspot clients only showing Authenticated devices #18

New issue

Open

opened 2026-03-04 14:52:24 +03:00 by kerem · 6 comments

kerem commented

2026-03-04 14:52:24 +03:00

Owner

Originally created by @PWJW on GitHub (Jun 23, 2025).
Original GitHub issue: https://github.com/f00b4r0/uspot/issues/31

When running the uspot clients command, it only appears to return devices that have fully authenticated, not devices that are in the pre-auth (walled gardened) state. Is this expected or a bug?

Steps:

I connected a device with mac 92:2c:96:76:40:70
the configured splash page appears on the device as normal
running uspot clients yields an empty json array:

hotspot:
{
}

after the device logs in via the presented splash page (radius auth successful), uspot clients then shows it:

hotspot:
{
        "92:2c:96:76:40:70": {
                "status": "Authenticated",
                "time": 620,
                "idle": 0,
                "lost": 0,
                "ip4addr": "10.1.0.236",
                "ip6addr": "",
                "sessionid": "7710674ba637ec3a",
                "username": "xx@054a25",
                [...snip...]
        }
}

Thanks

Originally created by @PWJW on GitHub (Jun 23, 2025). Original GitHub issue: https://github.com/f00b4r0/uspot/issues/31 When running the `uspot clients` command, it only appears to return devices that have fully authenticated, not devices that are in the pre-auth (walled gardened) state. Is this expected or a bug? Steps: 1. I connected a device with mac 92:2c:96:76:40:70 2. the configured splash page appears on the device as normal 3. running `uspot clients` yields an empty json array: ``` hotspot: { } ``` 4. after the device logs in via the presented splash page (radius auth successful), `uspot clients` then shows it: ``` hotspot: { "92:2c:96:76:40:70": { "status": "Authenticated", "time": 620, "idle": 0, "lost": 0, "ip4addr": "10.1.0.236", "ip6addr": "", "sessionid": "7710674ba637ec3a", "username": "xx@054a25", [...snip...] } } ``` Thanks

kerem added the

enhancement

question

labels

2026-03-04 14:52:24 +03:00

kerem commented

2026-03-04 14:52:25 +03:00

Author

Owner

@PWJW commented on GitHub (Jun 25, 2025):

Let me know if you need any further testing on this one :)

@PWJW commented on GitHub (Jun 25, 2025): Let me know if you need any further testing on this one :)

kerem commented

2026-03-04 14:52:25 +03:00

Author

Owner

@f00b4r0 commented on GitHub (Jun 25, 2025):

No thanks, I'll take a look when I get a chance. As I said bin/uspot is low prio :)

@f00b4r0 commented on GitHub (Jun 25, 2025): No thanks, I'll take a look when I get a chance. As I said bin/uspot is low prio :)

kerem commented

2026-03-04 14:52:25 +03:00

Author

Owner

@PWJW commented on GitHub (Jun 25, 2025):

No thanks, I'll take a look when I get a chance. As I said bin/uspot is low prio :)

Appreciate that. For context, it's really useful when you are a wireless network provider offering guest services to customers. We pull this info remotely and show the connected (authed/unauthed clients) on a web interface for our customers so they can see live data.

@PWJW commented on GitHub (Jun 25, 2025): > No thanks, I'll take a look when I get a chance. As I said bin/uspot is low prio :) Appreciate that. For context, it's really useful when you are a wireless network provider offering guest services to customers. We pull this info remotely and show the connected (authed/unauthed clients) on a web interface for our customers so they can see live data.

kerem commented

2026-03-04 14:52:26 +03:00

Author

Owner

@f00b4r0 commented on GitHub (Jun 28, 2025):

No thanks, I'll take a look when I get a chance. As I said bin/uspot is low prio :)

Appreciate that. For context, it's really useful when you are a wireless network provider offering guest services to customers. We pull this info remotely and show the connected (authed/unauthed clients) on a web interface for our customers so they can see live data.

Ok, the binary is definitely not designed for that purpose, I'll think about this. One of the issues is that "unauth clients" is a pretty loose group: it may include e.g. devices that were just "passing by".

Anyway, testing #28 and confirming it works is much more important: you haven't confirmed that it does following the last changes so I don't know if I correctly addressed the problem you reported? Thanks

@f00b4r0 commented on GitHub (Jun 28, 2025): > > No thanks, I'll take a look when I get a chance. As I said bin/uspot is low prio :) > > Appreciate that. For context, it's really useful when you are a wireless network provider offering guest services to customers. We pull this info remotely and show the connected (authed/unauthed clients) on a web interface for our customers so they can see live data. Ok, the binary is definitely not designed for that purpose, I'll think about this. One of the issues is that "unauth clients" is a pretty loose group: it may include e.g. devices that were just "passing by". Anyway, testing #28 and confirming it works is much more important: you haven't confirmed that it does following the last changes so I don't know if I correctly addressed the problem you reported? Thanks

kerem commented

2026-03-04 14:52:26 +03:00

Author

Owner

@f00b4r0 commented on GitHub (Jul 7, 2025):

So I took another look at this: if the goal as I understand it is to keep track of (and be able to list) clients which have loaded the portal (seen the splash page) but not yet clicked on anything, this is going to require a non-trivial rewrite of how uspot currently operates and that's fairly low prio for me at this point. I'll keep this issue open in the meantime.

@f00b4r0 commented on GitHub (Jul 7, 2025): So I took another look at this: if the goal as I understand it is to keep track of (and be able to list) clients which have loaded the portal (seen the splash page) but not yet clicked on anything, this is going to require a non-trivial rewrite of how uspot currently operates and that's fairly low prio for me at this point. I'll keep this issue open in the meantime.

kerem commented

2026-03-04 14:52:26 +03:00

Author

Owner

@nemesifier commented on GitHub (Jul 17, 2025):

Iwinfo/hostapd (depending if it's the interface is normal AP/sta or a mesh/adhoc interface) can already return the list of connected wifi stations / peers, there's also ubus modules for this, we use it in OpenWISP: github.com/openwisp/openwrt-openwisp-monitoring@4998b0a6a5/openwisp-monitoring/files/sbin/netjson-monitoring.lua (L102-L109)

This means that after getting the full list of connected stations, one could subtract the authenticated clients and hence get the list of unauthenticated clients, without adding more complexity here in uspot, which is good for maintainability.

@nemesifier commented on GitHub (Jul 17, 2025): Iwinfo/hostapd (depending if it's the interface is normal AP/sta or a mesh/adhoc interface) can already return the list of connected wifi stations / peers, there's also ubus modules for this, we use it in OpenWISP: https://github.com/openwisp/openwrt-openwisp-monitoring/blob/4998b0a6a5c7a0fdf23e86ce339e5fff36b94fc7/openwisp-monitoring/files/sbin/netjson-monitoring.lua#L102-L109 This means that after getting the full list of connected stations, one could subtract the authenticated clients and hence get the list of unauthenticated clients, without adding more complexity here in uspot, which is good for maintainability.