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
Added client ipv6 suffix as client identifier (::[fixed_part])
Proposed Solution
Implement either:
Pattern matching for client suffixes (::[fixed_part])
MAC-based IPv6 client identification without DHCP dependency
Expected result
Persistent client identification through suffix wildcards or MAC binding
Actual result
Requires full IPv6 address updates daily due to ISP prefix rotation
Additional information and/or screenshots
No response
The text was updated successfully, but these errors were encountered:
thewolfwood
changed the title
IPv6 alias (dynamic IPv6) not working for persistent clients
Dynamic IPv6 prefix changes force daily manual client updates in persistent client list
Feb 26, 2025
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question or ask for help
I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
FreeBSD, ARM64
Installation
GitHub releases or script from README
Setup
On a router, DHCP is handled by the router
AdGuard Home version
v0.107.57
Action
Added client ipv6 suffix as client identifier (
::[fixed_part]
)Proposed Solution
Implement either:
::[fixed_part]
)Expected result
Persistent client identification through suffix wildcards or MAC binding
Actual result
Requires full IPv6 address updates daily due to ISP prefix rotation
Additional information and/or screenshots
No response
The text was updated successfully, but these errors were encountered: