<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hi Brian,<div><br><div>Ok, I'll file a bug there. Until today, it was not clear to happen only with Neutron. </div><div><br></div><div>To explain, "LAN change" is connect a specific DHCP client from "namespace A" to "namespace B". Each namespace with a different provider:segmentation_id (VLAN) and Subnet, and the same gateway network. </div><div>It's like change a "phone" from "AccessPoint router A" to "AccessPoint router B" and in this case, the WAN link from both routers is the same net(gateway). </div><div><br></div><div>DNSMASQ debug config that I'm using are, log-queries + log-dhcp <a class="gmail_plusreply" id="plusReplyChip-0">+</a> log-facility=/tmp/dnsmasq.log </div><div><br></div><div>Thanks<br clear="all"><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><span style="font-size:12.8px"><font color="#666666">--</font></span></div><div><span style="font-size:12.8px"><font color="#666666">Luis Kleber</font></span></div><div><br></div></div></div></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">Em qui, 6 de dez de 2018 às 17:47, Brian Haley <<a href="mailto:haleyb.dev@gmail.com">haleyb.dev@gmail.com</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Luis,<br>
<br>
You should probably file a bug against neutron <br>
(<a href="https://bugs.launchpad.net/neutron/" rel="noreferrer" target="_blank">https://bugs.launchpad.net/neutron/</a>) with the relevant info, along with <br>
the neutron commands you're running and debug from the dhcp-agent and <br>
/var/lib/neutron/dhcp/xxx/ files as necessary. I don't exactly <br>
understand what you mean by "LAN changing", perhaps if I knew the <br>
commands you're using it would be clearer.<br>
<br>
Thanks,<br>
<br>
-Brian (from the Neutron team)<br>
<br>
On 12/6/18 9:47 AM, Luis Kleber wrote:<br>
> Last days I install 2 servers, one with Centos7 and other with Debian8, <br>
> without Openstack/Neutron. Both with the same DNSMASQ config I <br>
> originally posted.<br>
> On both I was using version 2.76 and upgraded to 2.78, using the same <br>
> ethernet interface changing the IP address between <a href="http://100.97.97.1/24" rel="noreferrer" target="_blank">100.97.97.1/24</a> <br>
> <<a href="http://100.97.97.1/24" rel="noreferrer" target="_blank">http://100.97.97.1/24</a>> and <a href="http://100.98.98.1/24" rel="noreferrer" target="_blank">100.98.98.1/24</a> <<a href="http://100.98.98.1/24" rel="noreferrer" target="_blank">http://100.98.98.1/24</a>>, and <br>
> everything works as expected. I also tested with 2 different interfaces <br>
> ont each case and also worked fine.<br>
> The DHCP client always was the same in all cases (Debian8, Centos7, and <br>
> Centos7 with Neutron).<br>
> <br>
> It seems that the problem only happens when using DNSMAQ with Neutron <br>
> routers.<br>
> How debug it better within Neutron? Another cache table, or how see <br>
> more detailed debug infos?<br>
> <br>
> Thanks<br>
> --<br>
> Luis Kleber<br>
> <br>
> <br>
> Em sex, 30 de nov de 2018 às 19:07, Luis Kleber <<a href="mailto:luis.kleber@gmail.com" target="_blank">luis.kleber@gmail.com</a> <br>
> <mailto:<a href="mailto:luis.kleber@gmail.com" target="_blank">luis.kleber@gmail.com</a>>> escreveu:<br>
> <br>
> Hi Stappers!<br>
> <br>
> No hardfeelings! There was only a question missing! :)<br>
> Thanks for your reply and yes, it's a complex setup because of the<br>
> Neutron use (all installation needed).<br>
> <br>
> After explained the problem, I was expecting a help to "how better<br>
> debug", how see some other logs, activate another debug, another<br>
> configuration, and so on...<br>
> I'll try if the same problem happens without Neutron. Only using a<br>
> DNSMASQ with 2 different access interfaces/networks.<br>
> <br>
> Tanks.<br>
> --<br>
> Luis Kleber<br>
> <br>
> <br>
> Em sex, 30 de nov de 2018 às 16:33, Geert Stappers<br>
> <<a href="mailto:stappers@stappers.nl" target="_blank">stappers@stappers.nl</a> <mailto:<a href="mailto:stappers@stappers.nl" target="_blank">stappers@stappers.nl</a>>> escreveu:<br>
> <br>
> On Wed, Nov 28, 2018 at 08:49:57AM -0200, Luis Kleber wrote:<br>
> > Em ter, 27 de nov de 2018 às 20:12, Geert Stappers escreveu:<br>
> > > On Mon, Nov 26, 2018 at 04:42:05PM -0200, Luis Kleber wrote:<br>
> > > <snip/><br>
> > > > dhcp-range=set:infra-70-subnet,100.101.1.11,100.101.1.64,600s<br>
> > > > dhcp-option=tag:infra-70-subnet,3,100.101.1.1<br>
> > > > dhcp-range=set:infra-71-subnet,100.101.2.11,100.101.2.64,600s<br>
> > > > dhcp-option=tag:infra-71-subnet,3,100.101.2.1<br>
> > > > dhcp-range=set:infra-72-subnet,100.98.98.11,100.98.98.64,600s<br>
> > > > dhcp-option=tag:infra-72-subnet,3,100.98.98.1<br>
> > > <snip> infra-73 ... infra-92 </snip><br>
> > > > dhcp-range=set:infra-93-subnet,100.103.8.11,100.103.8.64,600s<br>
> > > > dhcp-option=tag:infra-93-subnet,3,100.103.8.1<br>
> > > > dhcp-range=set:infra-94-subnet,100.104.1.11,100.104.1.64,600s<br>
> > > > dhcp-option=tag:infra-94-subnet,3,100.104.1.1<br>
> > > > dhcp-range=set:infra-95-subnet,100.96.96.11,100.96.96.64,600s<br>
> > > > dhcp-option=tag:infra-95-subnet,3,100.96.96.1<br>
> > ><br>
> > > Why?<br>
> > ><br>
> ><br>
> > "Why" what?<br>
> > If the question is the all other dhcp-ranges (unused for this<br>
> scenario),<br>
> > the answer is because in production case these other networks<br>
> for each dhcp<br>
> > range exist. These other unused ranges for this test case,<br>
> this cannot be a<br>
> > problem.<br>
> ><br>
> > Thanks<br>
> <br>
> No problem, no hardfeelings.<br>
> <br>
> It was me who should have wrote in his initial reply<br>
> <br>
> <br>
> Oops, that is a complex setup. Is really all the complexity<br>
> needed?<br>
> <br>
> <br>
> Anyway: Feel free to post, do known that it is been readed.<br>
> <br>
> <br>
> Groeten<br>
> Geert Stappers<br>
> -- <br>
> > this cannot be a problem.<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>
> <mailto:<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">Dnsmasq-discuss@lists.thekelleys.org.uk</a>><br>
> <a href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss</a><br>
> <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="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss</a><br>
> <br>
</blockquote></div></div></div></div></div></div></div>