You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running on version: v0.107.78, AGH seems to try to only lookup runtime client names rather than all client names. This difference has been made apparent in my use case with wireguard, where the wireguard clients are not gathered into the runtime clients. Note, wireguard does not in itself manage rDNS, but I have manually added rewrites and ptr entries in AGH to make that side of things work. This creates a situation where while AGH knows their rDNS names, it never asks for them to populate the client names.
To solve this issue, it would be great if the rDNS resolution can be expanded to all clients rather than just runtime. It would additionally be useful to add a setting in the persistent clients section to prefer rDNS names over the names manually entered. This allows the Top clients table to reflect the actual name of the device (if it has one), and in the case of cidr subnet rules, will prevent all affected clients from sharing the same name.
Obviously, this is a rather minor issue, but I think it would really help consistency and visibility of clients in the WebUI.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hello,
Running on version: v0.107.78, AGH seems to try to only lookup runtime client names rather than all client names. This difference has been made apparent in my use case with wireguard, where the wireguard clients are not gathered into the runtime clients. Note, wireguard does not in itself manage rDNS, but I have manually added rewrites and ptr entries in AGH to make that side of things work. This creates a situation where while AGH knows their rDNS names, it never asks for them to populate the client names.
To solve this issue, it would be great if the rDNS resolution can be expanded to all clients rather than just runtime. It would additionally be useful to add a setting in the persistent clients section to prefer rDNS names over the names manually entered. This allows the Top clients table to reflect the actual name of the device (if it has one), and in the case of cidr subnet rules, will prevent all affected clients from sharing the same name.
Obviously, this is a rather minor issue, but I think it would really help consistency and visibility of clients in the WebUI.
All reactions