Reviewed: https://review.openstack.org/476477 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c28dd28514e37e1f655118a8b9d8bb34174b4a82 Submitter: Jenkins Branch: master
commit c28dd28514e37e1f655118a8b9d8bb34174b4a82 Author: Harald Jensas <[email protected]> Date: Thu Jun 22 13:17:21 2017 +0200 DHCP Agent: Set dhcp-range netmask property To complete the DHCP support for non-local routed networks via relay agent the dhcp agent must configure the netmask in the --dhcp-range option for IPv4 networks. This was previously not required becuase dnsmasq can determine it from the local interface information for local networks. 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. Change-Id: I5d609e47a3463c11338dd38aedebfb4a6822f503 Closes-Bug: #1699754 ** Changed in: neutron Status: In Progress => Fix Released -- 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: Fix Released 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
