neutron

Quantum-dhcp dnsmasq driver doesn't have ip ranges in subnet

Bug #1029034 reported by MURAOKA Yusuke
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Invalid
Undecided
Unassigned

Bug Description

Quantum db model v2 has ranges which ip addresses can be allocated. But the dnsmasq driver doesn't follow them, use only cidr of subnet.
If you specify the cidr 192.168.1.0, dnsmasq allocate ip addresses 192.168.1.2 to 192.168.1.254. Thus, you can't allocate any static ip address manually in same subnet.

Revision history for this message
Mark McClain (markmcclain) wrote :

dnsmasq is set for static allocations and only responds if there is an allocation in the Quantum database. If you want to reserve a portion of the range for static IP addresses, you will need to update the IP allocation pool for the subnet in the Quantum database to prevent Quantum from assigning that range.

Have you seen any instances where an address was given out by dnsmasq that was not in the Quantum database?

MURAOKA Yusuke (yusuke)
Changed in quantum:
status: New → Invalid
Revision history for this message
MURAOKA Yusuke (yusuke) wrote :

Thank you for the explanation. I reviewed your code with your explanation again then I got I was in miss-understanding.
I thought --dhcp-range and --dhcp-host are split, can't be used together. It was wrong.
Your code describes that defines subnet network range, and defines static ip addresses in the subnet together.

Please ignore this report. I'm so sorry.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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