Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include 'vendor class identifier' option into DHCPREQUEST message #5380

Merged
merged 1 commit into from Feb 20, 2017

Conversation

2 participants
@agalanin
Copy link
Contributor

commented Feb 18, 2017

According to RFC 2131:

If the client uses a 'client identifier' in a
DHCPREQUEST message, it MUST use that same 'client identifier' in all
subsequent messages. If the client included a list of requested
parameters in a DHCPDISCOVER message, it MUST include that list in
all subsequent messages.

@agalanin agalanin changed the title Include 'vendor class identifier option' into DHCPREQUEST message Include 'vendor class identifier' option into DHCPREQUEST message Feb 18, 2017

@martinpitt martinpitt added the dhcp label Feb 20, 2017

@martinpitt

This comment has been minimized.

Copy link
Contributor

commented Feb 20, 2017

Makes sense. Thank you!

@martinpitt martinpitt merged commit 5153494 into systemd:master Feb 20, 2017

5 checks passed

default Build finished.
Details
semaphoreci The build passed on Semaphore.
Details
xenial-amd64 autopkgtest finished (success)
Details
xenial-i386 autopkgtest finished (success)
Details
xenial-s390x autopkgtest finished (success)
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.