starred/AdGuardHome

Fork 0

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

Removing leases.db unsets client-requests data #2836

New issue

Closed

opened 2026-03-04 02:28:43 -05:00 by deekerman · 3 comments

deekerman commented

2026-03-04 02:28:43 -05:00

Owner

Originally created by @agneevX on GitHub (Jun 7, 2021).

Prerequisites

I am running the latest version
I checked the documentation and found no answer
I checked to make sure that this issue has not already been filed

Environment

Version of AdGuard Home server: 0.106.3
How did you install AdGuard Home: GH Releases
How did you setup DNS configuration: AGH DHCP
If it's a router or IoT, please write device model:
CPU architecture: arm64
Operating system and version: Ubuntu 20.04

Issue Details

I had to remove leases.db because a certain DHCP client's hostname was showing up blank.

After I started up AGH, the client's hostname was correctly visible

However, after I renewed leases on a few devices, I noticed that Top Clients was showing incorrect data for hostnames.

Expected Behavior

Historical queries would get mapped correctly to the client.

Is there a way I can rectify this at this time?3

Originally created by @agneevX on GitHub (Jun 7, 2021). ### Prerequisites - [x] I am running the latest version - [x] I checked the documentation and found no answer - [x] I checked to make sure that this issue has not already been filed ### Environment * **Version of AdGuard Home server:** 0.106.3 * **How did you install AdGuard Home:** GH Releases * **How did you setup DNS configuration:** AGH DHCP * **If it's a router or IoT, please write device model:** * **CPU architecture:** arm64 * **Operating system and version:** Ubuntu 20.04 ### Issue Details I had to remove `leases.db` because a certain DHCP client's hostname was showing up blank. After I started up AGH, the client's hostname was correctly visible However, after I renewed leases on a few devices, I noticed that Top Clients was showing incorrect data for hostnames. ### Expected Behavior Historical queries would get mapped correctly to the client. Is there a way I can rectify this at this time?3

deekerman

2026-03-04 02:28:43 -05:00

closed this issue
added the
question
label

deekerman commented

2026-03-04 02:29:02 -05:00

Author

Owner

@ainar-g commented on GitHub (Jun 7, 2021):

Hi. Unfortunately I don't think that this is currently possible, as these statistics are joined to the data from the leases database. Such situations should become less frequent once we find a better storage format in #2290.

@ainar-g commented on GitHub (Jun 7, 2021): Hi. Unfortunately I don't think that this is currently possible, as these statistics are joined to the data from the leases database. Such situations should become less frequent once we find a better storage format in #2290.

deekerman commented

2026-03-04 02:29:02 -05:00

Author

Owner

@agneevX commented on GitHub (Jun 7, 2021):

Ah ok! As of now, how are queries mapped to clients?

If it's dynamic, I'm not sure why it can't be mapped, unless AGH tends to give the same DHCP IP to clients?

@agneevX commented on GitHub (Jun 7, 2021): Ah ok! As of now, how are queries mapped to clients? If it's dynamic, I'm not sure why it can't be mapped, unless AGH tends to give the same DHCP IP to clients?

deekerman commented

2026-03-04 02:29:02 -05:00

Author

Owner

@ainar-g commented on GitHub (Jun 7, 2021):

They are mapped by ClientID and, if there is none, by IP address. So, if your DHCP clients receive a different IP address, the stats won't be accurate. Creating clients by MAC would fix it, but our current stats don't know anything about MAC, unfortunately. Most of these issues should get solved once we have a better database.

I'll close this issue, if you don't mind, as there is little we can do here at the moment. Apologies for the inconvenience!

@ainar-g commented on GitHub (Jun 7, 2021): They are mapped by ClientID and, if there is none, by IP address. So, if your DHCP clients receive a different IP address, the stats won't be accurate. Creating clients by MAC would fix it, but our current stats don't know anything about MAC, unfortunately. Most of these issues should get solved once we have a better database. I'll close this issue, if you don't mind, as there is little we can do here at the moment. Apologies for the inconvenience!

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#2836

No description provided.

Rows
Columns