No validation for DHCP options may lead to potential issues with different dhcp backends

Bug #1723354 reported by Vasyl Saienko
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

DHCP option names are not standardized and option names that works with dnsmasq doesn't work with Contrail. By trying to switch to dhcp option values we found that it breaks dnsmasq case. As dnsmasq always set `siaddr` field in dhcp reply to dnsmasq host ip unless `server-ip-address` is not configured. This field is treated by pxe client as tftp server more information about this may be found here
We left this dnsmasq internal option `server-ip-address`. All dhcp providers we tried contrail/dnsmasq/isc just silently ignore unknown options. But still we concern that it may blow up with others. This is not an actual bug, it is only our concern. And we wondered that it maybe standardized on Neutron side somehow or at least basic validation is provided.

Tags: l3-ipam-dhcp
Changed in neutron:
importance: Undecided → Wishlist
tags: added: l3-ipam-dhcp
Revision history for this message
Boden R (boden) wrote :

If someone has the time to work on this, seems like maybe it could come through the blueprint/spec process, just to make sure everyone is on the same page.


Changed in neutron:
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.