starred/AdGuardHome

Fork 0

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

Allow RDNS to check/discover hostnames when ARP Implementation does not provide them. #3571

New issue

Open

opened 2026-03-04 03:53:19 -05:00 by deekerman · 1 comment

deekerman commented

2026-03-04 03:53:19 -05:00

Owner

Originally created by @jumpsmm7 on GitHub (Mar 23, 2022).

Have a question or an idea? Please search it on our forum to make sure it was not yet asked. If you cannot find what you had in mind, please submit it here.

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

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

Problem Description

As mentioned previous problems #3142 #3597 spawned a new feature request as a result of not every ARP implementation providing Client hostname information along side it. A conundrum is created. While the addition of the reading of ARP cache allows for the addition of more Client DATA, the conundrum present means that not all clients will have hostnames available. A recipe for an incomplete client list.

Proposed Solution

A propose solution as discussed between @EugeneOne1 and I in prior issue #3142 , https://github.com/AdguardTeam/AdGuardHome/issues/3142#issuecomment-1075474442

Some of the devices discovered under ARP, do have an RDNS associated as well.
Is there away this could be a joined feature as well. Maybe RDNS is not working hard enough and needs to be used after ARP is discovered as well.

we're already have a couple of related issues (https://github.com/AdguardTeam/AdGuardHome/issues/1949, https://github.com/AdguardTeam/AdGuardHome/issues/3020).
However, if I recall correctly, no one ever suggested to resolve clients recieved from ARP with rDNS. This may be useful since some implementations of ARP don't support hostnames.

Alternatives Considered

Will be added pending other suggestions are presented.

Additional Information

Shortened for readability

/tmp/home/root# cat /proc/net/arp
IP address HW type Flags HW address Mask Device
192.168.1.133 0x1 0x2 74:e1:82:36:05:ef * br0
192.168.1.183 0x1 0x2 00:c3:f4:df:12:7e * br0
192.168.1.17 0x1 0x2 e4:5f:01:45:57:9d * br0
192.168.1.12 0x1 0x2 34:97:f6:70:16:50 * br0

/tmp/home/root# arp -an
? (192.168.1.133) at 74:e1:82:36:05:ef [ether] on br0
? (192.168.1.183) at 00:c3:f4:df:12:7e [ether] on br0
? (192.168.1.17) at e4:5f:01:45:57:9d [ether] on br0
? (192.168.1.12) at 34:97:f6:70:16:50 [ether] on br0

Originally created by @jumpsmm7 on GitHub (Mar 23, 2022). Have a question or an idea? Please search it [on our forum](https://github.com/AdguardTeam/AdGuardHome/discussions) to make sure it was not yet asked. If you cannot find what you had in mind, please [submit it here](https://github.com/AdguardTeam/AdGuardHome/discussions/new). ### Prerequisites Please answer the following questions for yourself before submitting an issue. **YOU MAY DELETE THE PREREQUISITES SECTION.** - [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 ### Problem Description As mentioned previous problems #3142 #3597 spawned a new feature request as a result of not every ARP implementation providing Client hostname information along side it. A conundrum is created. While the addition of the reading of ARP cache allows for the addition of more Client DATA, the conundrum present means that not all clients will have hostnames available. A recipe for an incomplete client list. ### Proposed Solution A propose solution as discussed between @EugeneOne1 and I in prior issue #3142 , https://github.com/AdguardTeam/AdGuardHome/issues/3142#issuecomment-1075474442 > Some of the devices discovered under ARP, do have an RDNS associated as well. >Is there away this could be a joined feature as well. Maybe RDNS is not working hard enough and needs to be used after ARP is discovered as well. > we're already have a couple of related issues (https://github.com/AdguardTeam/AdGuardHome/issues/1949, https://github.com/AdguardTeam/AdGuardHome/issues/3020). >However, if I recall correctly, no one ever suggested to resolve clients recieved from ARP with rDNS. This may be useful since some implementations of ARP don't support hostnames. ### Alternatives Considered >Will be added pending other suggestions are presented. ### Additional Information ![image](https://user-images.githubusercontent.com/49514613/159683458-009df763-02c7-4444-bc4a-9d07013b66c9.png) ### Shortened for readability `/tmp/home/root# cat /proc/net/arp` `IP address HW type Flags HW address Mask Device` `192.168.1.133 0x1 0x2 74:e1:82:36:05:ef * br0` `192.168.1.183 0x1 0x2 00:c3:f4:df:12:7e * br0` `192.168.1.17 0x1 0x2 e4:5f:01:45:57:9d * br0` `192.168.1.12 0x1 0x2 34:97:f6:70:16:50 * br0` `/tmp/home/root# arp -an` `? (192.168.1.133) at 74:e1:82:36:05:ef [ether] on br0` `? (192.168.1.183) at 00:c3:f4:df:12:7e [ether] on br0` `? (192.168.1.17) at e4:5f:01:45:57:9d [ether] on br0` `? (192.168.1.12) at 34:97:f6:70:16:50 [ether] on br0`

deekerman added the

enhancement

label

2026-03-04 03:53:19 -05:00

deekerman commented

2026-03-04 03:53:27 -05:00

Author

Owner

@t0niX commented on GitHub (Oct 14, 2023):

Interested in this as well.

@t0niX commented on GitHub (Oct 14, 2023): Interested in this as well.

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

No description provided.

Rows
Columns