Hi dnsmasq guys.

I'm Yuki Nishiwaki.
Recently I started to work on dnsmasq stuff. I could ask stupid thing
though I want to ask if anyone think the same thing as me.

I'm using dnsmasq under cloud controller and dnsmasq have responsibility to
lease IP for
our all virtual machines connected to Host via tap on the same host running

In order to do that, I had to specify same number of --dhcp-range as the
number of subnet VM belong to but
we can not add dynamically "--dhcp-range" and I don't wanna restart
everytime new subnet added.

So I was going to specify "--dhcp-range=,static,"  or
--dhcp-range=,static," to
support all subnets possibly will be added in the future and lease IP for
only known client.
It kind of worked but the netmask of leased IP was the same as dhcp-range
I expected the netmask will be got from the NIC receiving DHCP request and
dhcp-range's netmask is only used for judging if dnsmasq should reply or

After read the code around
https://github.com/imp/dnsmasq/blob/master/src/dhcp.c#L501-L561, I
understood why I can not.
But If there is any chance I can add new option or other behaviour to cover
my usecase
so that dnsmasq can use the netmask of NIC's IP receiving DHCP request for
the IP to be leased while the netmask dhcp-range specified is used to judge
dnsmasq should reply or not, I'm willing to write the patch but
beforehand I want to ask what do you think about such additional change. Is
this good approach, feature or bad approach, feature nobody want but me?


Yuki Nishiwaki
Dnsmasq-discuss mailing list

Reply via email to