<div dir="ltr"><p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-IN">The issue
is seen even after porting the latest Dnsmasq version 2.89 also.</span></p><p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-IN"><br></span></p><p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">Thanks,</p><p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">Shashi</p></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 4, 2023 at 1:20 PM Geert Stappers <<a href="mailto:stappers@stappers.nl">stappers@stappers.nl</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, Aug 04, 2023 at 11:54:15AM +0530, shashikumar Shashi wrote:<br>
> Hi,<br>
> <br>
> Observing that dnsmasq (version 2.80) is offering DHCP IP to the client<br>
        <snip/> <br>
> If dnsmasq is rebuilt by commenting out the following code block from<br>
> dhcp_reply function, then in the above case, dnsmasq offers IP from the<br>
> vlan19 pool (the correct pool) even if vlan99 is DOWN.<br>
        <snip/> <br>
> Has anyone come across such an issue?<br>
<br>
Could be.<br>
Most likely they tried a more recent version.<br>
<br>
<br>
<br>
Groeten<br>
Geert Stappers<br>
-- <br>
Silence is hard to parse<br>
<br>
_______________________________________________<br>
Dnsmasq-discuss mailing list<br>
<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">Dnsmasq-discuss@lists.thekelleys.org.uk</a><br>
<a href="https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss</a><br>
</blockquote></div>