Encapsulated DHCP options are not supported in neutron
Bug #1860488 reported by
Brian Haley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
New
|
Medium
|
Unassigned |
Bug Description
Some PXE implementations, including iPXE, use vendor-specific options
encapsulated in a single top-level option to send configuration data in
DHCP packets. As an example, iPXE encapsulates various options in option
175.
This is fully supported by dnsmasq (see below), however, the original
code which translates a DHCP option name and value into a dnsmasq
command-line argument would expect any non-numeric option 'name' to be a
named option, hence prepending with `option:`.
The dhcp agent should be changed to ensure `encap:X,Y` is properly translated
into either `encap:X,Y` if Y is numerical, or `encap:X,option:Y` if Y is text.
Changed in neutron: | |
status: | Confirmed → In Progress |
tags: | added: l3-ipam-dhcp |
To post a comment you must log in.
For some reason launchpad missed the proposed fix for this one: /review. opendev. org/681466
https:/