starred/AdGuardHome

Fork 0

mirror of https://github.com/AdguardTeam/AdGuardHome.git synced 2026-03-04 00:01:12 -05:00

Connected client number #1625

New issue

Closed

opened 2026-03-04 01:25:39 -05:00 by deekerman · 7 comments

deekerman commented

2026-03-04 01:25:39 -05:00

Owner

Originally created by @sheminasalam on GitHub (May 28, 2020).

Can you add a tab in the dashboard to see how many devices are currently connected to Adguard? And also what all are these? I am asking because, whenever I have to restart Adguard host system my router sets the secondary DNS address as defaults and wont change until the router is rebooted or connection reset. In those circumstances it would be helpful to know which all and how may clients are presently connected.

Originally created by @sheminasalam on GitHub (May 28, 2020). Can you add a tab in the dashboard to see how many devices are currently connected to Adguard? And also what all are these? I am asking because, whenever I have to restart Adguard host system my router sets the secondary DNS address as defaults and wont change until the router is rebooted or connection reset. In those circumstances it would be helpful to know which all and how may clients are presently connected.

deekerman

2026-03-04 01:25:39 -05:00

closed this issue
added the
wontfix
label

deekerman commented

2026-03-04 01:25:48 -05:00

Author

Owner

@ameshkov commented on GitHub (May 28, 2020):

Devices do not maintain some persistent connections to AdGuard, they make requests when they need to.

So it would quite problematic to define what devices we consider "connected".

@ameshkov commented on GitHub (May 28, 2020): Devices do not maintain some persistent connections to AdGuard, they make requests when they need to. So it would quite problematic to define what devices we consider "connected".

deekerman commented

2026-03-04 01:25:48 -05:00

Author

Owner

@sheminasalam commented on GitHub (May 29, 2020):

I have been using pihole for a long time and in that I had the option to view the connected clients. Thats why I requested for this function.

@sheminasalam commented on GitHub (May 29, 2020): I have been using pihole for a long time and in that I had the option to view the connected clients. Thats why I requested for this function.

deekerman commented

2026-03-04 01:25:48 -05:00

Author

Owner

@ameshkov commented on GitHub (May 29, 2020):

Btw, how does it work in Pi-Hole? Which clients they consider "connected"?

@ameshkov commented on GitHub (May 29, 2020): Btw, how does it work in Pi-Hole? Which clients they consider "connected"?

deekerman commented

2026-03-04 01:25:48 -05:00

Author

Owner

@sheminasalam commented on GitHub (May 29, 2020):

I have limited knowledge on its technical side but if you are familiar with pihole, its there in the dashboard itself. It helped me to know if my router was pulling queries from pihole or not. Maybe they were checking the persistence with which queries arrives. I think so because in the present IoT system there are negligible devices which doesn't pull queries which in a very short span of time. Its true in the case of any routers or handheld devices. So if a device doesn't pull quires for a particular amount of time, it might be deemed disconnected.

@sheminasalam commented on GitHub (May 29, 2020): I have limited knowledge on its technical side but if you are familiar with pihole, its there in the dashboard itself. It helped me to know if my router was pulling queries from pihole or not. Maybe they were checking the persistence with which queries arrives. I think so because in the present IoT system there are negligible devices which doesn't pull queries which in a very short span of time. Its true in the case of any routers or handheld devices. So if a device doesn't pull quires for a particular amount of time, it might be deemed disconnected.

deekerman commented

2026-03-04 01:25:48 -05:00

Author

Owner

@werlitong commented on GitHub (May 29, 2020):

Btw, how does it work in Pi-Hole? Which clients they consider "connected"?

Probably they consider devices that in the past 24h done queries to server.

@werlitong commented on GitHub (May 29, 2020): > Btw, how does it work in Pi-Hole? Which clients they consider "connected"? Probably they consider devices that in the past 24h done queries to server.

deekerman commented

2026-03-04 01:25:48 -05:00

Author

Owner

@sheminasalam commented on GitHub (May 29, 2020):

Nop, i dont think 24 hours is too much time frame. Since we are setting our DNS mostly in router which is connected to multiple devices, I believe a quire from router inevitable within a minute or so. And also now most of the routers check if the network is online and for this they ping an address provided by the parent company. For example my tenda router at regular intervals check with the address api.cloud.tenda.com.cn . So if adguard can find such regular address and the frequency it repeats, it can ensure that the device is online or offline within a short interval of time.

@sheminasalam commented on GitHub (May 29, 2020): Nop, i dont think 24 hours is too much time frame. Since we are setting our DNS mostly in router which is connected to multiple devices, I believe a quire from router inevitable within a minute or so. And also now most of the routers check if the network is online and for this they ping an address provided by the parent company. For example my tenda router at regular intervals check with the address api.cloud.tenda.com.cn . So if adguard can find such regular address and the frequency it repeats, it can ensure that the device is online or offline within a short interval of time.

deekerman commented

2026-03-04 01:25:48 -05:00

Author

Owner

@stale[bot] commented on GitHub (Jul 28, 2020):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Jul 28, 2020): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

deekerman referenced this issue

2026-03-04 01:29:47 -05:00

[Feature Request] Enable Drill Through to the Query log from the Dashboard #1714

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/AdGuardHome#1625

No description provided.

Rows
Columns