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
I have searched other issues and found no duplicates
I want to report a bug and not ask a question
Operating system type
macOS (aka Darwin)
CPU architecture
AMD64
Installation
GitHub releases or script from README
Setup
On one machine
AdGuard Home version
Built from master
Description
What did you do?
Request and receive a dynamic lease with the Client Host Name option (12) specified.
Repeat the step above before the lease expired.
Expected result
The latest lease has the same host name in the option 12 as the one before.
Actual result
AdGuard Home considers the sender of the DHCPREQUEST message as the new client and checks it's host name for uniqueness, finds the same client and responds with generated host name.
The subsequent releases will swap these names over and over again.
Additional information
Currently, AdGuard Home processes the DHCPREQUEST messages in a single way (as if it follows the DHCPDISCOVER message). RFC 2131, however, states a few kinds of DHCPREQUEST, such as for rebinding or for lease extension. This leads to incorrect serving of the clients sending standalone DHCPREQUEST messages for those purposes.
The text was updated successfully, but these errors were encountered:
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
Operating system type
macOS (aka Darwin)
CPU architecture
AMD64
Installation
GitHub releases or script from README
Setup
On one machine
AdGuard Home version
Built from master
Description
What did you do?
12
) specified.Expected result
The latest lease has the same host name in the option
12
as the one before.Actual result
AdGuard Home considers the sender of the DHCPREQUEST message as the new client and checks it's host name for uniqueness, finds the same client and responds with generated host name.
The subsequent releases will swap these names over and over again.
Additional information
Currently, AdGuard Home processes the DHCPREQUEST messages in a single way (as if it follows the DHCPDISCOVER message). RFC 2131, however, states a few kinds of DHCPREQUEST, such as for rebinding or for lease extension. This leads to incorrect serving of the clients sending standalone DHCPREQUEST messages for those purposes.
The text was updated successfully, but these errors were encountered: