yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1723354@xxxxxxxxxxxxxxxxxx>]

Closing this bug due to the lack of activity. Please feel free to reopen
it.

** Changed in: neutron
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1723354

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

Status in neutron:
  Won't Fix

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 https://tools.ietf.org/html/rfc5859.
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1723354/+subscriptions