← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1699754] [NEW] [RFE] DHCP linux agent - set <prefix-len> in dhcp-range option to support networks via ralay agent

 

Public bug reported:

To complete the DHCP support for remote routed networks via relay agent
the dhcp agent must configure the <prefix-len> in the --dhcp-range
option. This was previously not requred becuase dnsmasq can determine it
from the local interface information. For remote networks we need to set
this property.

DNSMASQ(8)
"""
For directly connected networks (ie, networks on which the machine running dnsmasq has an interface) the netmask is  optional:  dnsmasq  will  determine it from the interface configuration. For networks which receive DHCP service via a relay agent, dnsmasq cannot determine the netmask itself, so it should be specified, otherwise dnsmasq  will have to guess, based on the class (A, B or C) of the network address. The broadcast address is always optional. It is always allowed to have more than one dhcp-range in a single subnet.
"""

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: l3-ipam-dhcp

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

Title:
  [RFE] DHCP linux agent - set <prefix-len> in dhcp-range option to
  support networks via ralay agent

Status in neutron:
  New

Bug description:
  To complete the DHCP support for remote routed networks via relay
  agent the dhcp agent must configure the <prefix-len> in the --dhcp-
  range option. This was previously not requred becuase dnsmasq can
  determine it from the local interface information. For remote networks
  we need to set this property.

  DNSMASQ(8)
  """
  For directly connected networks (ie, networks on which the machine running dnsmasq has an interface) the netmask is  optional:  dnsmasq  will  determine it from the interface configuration. For networks which receive DHCP service via a relay agent, dnsmasq cannot determine the netmask itself, so it should be specified, otherwise dnsmasq  will have to guess, based on the class (A, B or C) of the network address. The broadcast address is always optional. It is always allowed to have more than one dhcp-range in a single subnet.
  """

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


Follow ups