Re: [Dnsmasq-discuss] DNSMASQ wrong addresses allocated after changing DHCP Clients between Neutron vRouters

2018-12-06 Thread Luis Kleber 
Hi Brian,

Ok, I'll file a bug there. Until today, it was not clear to happen only
with Neutron.

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.
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).

DNSMASQ debug config that I'm using are, log-queries +  log-dhcp +
log-facility=/tmp/dnsmasq.log

Thanks
--
Luis  Kleber


Em qui, 6 de dez de 2018 às 17:47, Brian Haley 
escreveu:

> Luis,
>
> You should probably file a bug against neutron
> (https://bugs.launchpad.net/neutron/) with the relevant info, along with
> the neutron commands you're running and debug from the dhcp-agent and
> /var/lib/neutron/dhcp/xxx/ files as necessary.  I don't exactly
> understand what you mean by "LAN changing", perhaps if I knew the
> commands you're using it would be clearer.
>
> Thanks,
>
> -Brian (from the Neutron team)
>
> On 12/6/18 9:47 AM, Luis Kleber wrote:
> > Last days I install 2 servers, one with Centos7 and other with Debian8,
> > without Openstack/Neutron. Both with the same DNSMASQ config I
> > originally posted.
> > On both I was using version 2.76 and upgraded to 2.78, using the same
> > ethernet interface changing the IP address between 100.97.97.1/24
> >  and 100.98.98.1/24 , and
> > everything works as expected. I also tested with 2 different interfaces
> > ont each case and also worked fine.
> > The DHCP client always was the same in all cases (Debian8, Centos7, and
> > Centos7 with Neutron).
> >
> > It seems that the problem only happens when using DNSMAQ with Neutron
> > routers.
> > How debug it better within Neutron?  Another cache table, or how see
> > more detailed debug infos?
> >
> > Thanks
> > --
> > Luis  Kleber
> >
> >
> > Em sex, 30 de nov de 2018 às 19:07, Luis Kleber  > > escreveu:
> >
> > Hi Stappers!
> >
> > No hardfeelings! There was only a question missing! :)
> > Thanks for your reply and yes,  it's a complex setup because of the
> > Neutron use (all installation needed).
> >
> > After explained the problem, I was expecting a help to "how better
> > debug", how see some other logs, activate another debug, another
> > configuration, and so on...
> > I'll try if the same problem happens without Neutron. Only using a
> > DNSMASQ with 2 different access interfaces/networks.
> >
> > Tanks.
> > --
> > Luis Kleber
> >
> >
> > Em sex, 30 de nov de 2018 às 16:33, Geert Stappers
> > mailto:stapp...@stappers.nl>> escreveu:
> >
> > On Wed, Nov 28, 2018 at 08:49:57AM -0200, Luis Kleber wrote:
> >  > Em ter, 27 de nov de 2018 às 20:12, Geert Stappers escreveu:
> >  > > On Mon, Nov 26, 2018 at 04:42:05PM -0200, Luis Kleber wrote:
> >  > > 
> >  > > >
> dhcp-range=set:infra-70-subnet,100.101.1.11,100.101.1.64,600s
> >  > > > dhcp-option=tag:infra-70-subnet,3,100.101.1.1
> >  > > >
> dhcp-range=set:infra-71-subnet,100.101.2.11,100.101.2.64,600s
> >  > > > dhcp-option=tag:infra-71-subnet,3,100.101.2.1
> >  > > >
> dhcp-range=set:infra-72-subnet,100.98.98.11,100.98.98.64,600s
> >  > > > dhcp-option=tag:infra-72-subnet,3,100.98.98.1
> >  > >  infra-73 ... infra-92 
> >  > > >
> dhcp-range=set:infra-93-subnet,100.103.8.11,100.103.8.64,600s
> >  > > > dhcp-option=tag:infra-93-subnet,3,100.103.8.1
> >  > > >
> dhcp-range=set:infra-94-subnet,100.104.1.11,100.104.1.64,600s
> >  > > > dhcp-option=tag:infra-94-subnet,3,100.104.1.1
> >  > > >
> dhcp-range=set:infra-95-subnet,100.96.96.11,100.96.96.64,600s
> >  > > > dhcp-option=tag:infra-95-subnet,3,100.96.96.1
> >  > >
> >  > > Why?
> >  > >
> >  >
> >  > "Why" what?
> >  > If the question is the all other dhcp-ranges (unused for this
> > scenario),
> >  > the answer is because in production case these other networks
> > for each dhcp
> >  > range exist. These other unused ranges for this test case,
> > this cannot be a
> >  > problem.
> >  >
> >  > Thanks
> >
> > No problem, no hardfeelings.
> >
> > It was me who should have wrote in his initial reply
> >
> >
> >Oops, that is a complex setup. Is really all the complexity
> > needed?
> >
> >
> > Anyway: Feel free to post, do known that it is been readed.
> >
> >
> > Groeten
> > Geert Stappers
> > --
> >  > this cannot be a problem.
> >
> > ___
> > Dnsmasq-discuss mailing list
> > Dnsmasq-discuss@lists.thekelleys.org.uk
> >

Re: [Dnsmasq-discuss] DNSMASQ wrong addresses allocated after changing DHCP Clients between Neutron vRouters

2018-12-06 Thread Brian Haley 

Luis,

You should probably file a bug against neutron 
(https://bugs.launchpad.net/neutron/) with the relevant info, along with 
the neutron commands you're running and debug from the dhcp-agent and 
/var/lib/neutron/dhcp/xxx/ files as necessary.  I don't exactly 
understand what you mean by "LAN changing", perhaps if I knew the 
commands you're using it would be clearer.


Thanks,

-Brian (from the Neutron team)

On 12/6/18 9:47 AM, Luis Kleber wrote:
Last days I install 2 servers, one with Centos7 and other with Debian8, 
without Openstack/Neutron. Both with the same DNSMASQ config I 
originally posted.
On both I was using version 2.76 and upgraded to 2.78, using the same 
ethernet interface changing the IP address between 100.97.97.1/24 
 and 100.98.98.1/24 , and 
everything works as expected. I also tested with 2 different interfaces 
ont each case and also worked fine.
The DHCP client always was the same in all cases (Debian8, Centos7, and 
Centos7 with Neutron).


It seems that the problem only happens when using DNSMAQ with Neutron 
routers.
How debug it better within Neutron?  Another cache table, or how see 
more detailed debug infos?


Thanks
--
Luis  Kleber


Em sex, 30 de nov de 2018 às 19:07, Luis Kleber > escreveu:


Hi Stappers!

No hardfeelings! There was only a question missing! :)
Thanks for your reply and yes,  it's a complex setup because of the
Neutron use (all installation needed).

After explained the problem, I was expecting a help to "how better
debug", how see some other logs, activate another debug, another
configuration, and so on...
I'll try if the same problem happens without Neutron. Only using a
DNSMASQ with 2 different access interfaces/networks.

Tanks.
--
Luis Kleber


Em sex, 30 de nov de 2018 às 16:33, Geert Stappers
mailto:stapp...@stappers.nl>> escreveu:

On Wed, Nov 28, 2018 at 08:49:57AM -0200, Luis Kleber wrote:
 > Em ter, 27 de nov de 2018 às 20:12, Geert Stappers escreveu:
 > > On Mon, Nov 26, 2018 at 04:42:05PM -0200, Luis Kleber wrote:
 > >     
 > > > dhcp-range=set:infra-70-subnet,100.101.1.11,100.101.1.64,600s
 > > > dhcp-option=tag:infra-70-subnet,3,100.101.1.1
 > > > dhcp-range=set:infra-71-subnet,100.101.2.11,100.101.2.64,600s
 > > > dhcp-option=tag:infra-71-subnet,3,100.101.2.1
 > > > dhcp-range=set:infra-72-subnet,100.98.98.11,100.98.98.64,600s
 > > > dhcp-option=tag:infra-72-subnet,3,100.98.98.1
 > >      infra-73 ... infra-92 
 > > > dhcp-range=set:infra-93-subnet,100.103.8.11,100.103.8.64,600s
 > > > dhcp-option=tag:infra-93-subnet,3,100.103.8.1
 > > > dhcp-range=set:infra-94-subnet,100.104.1.11,100.104.1.64,600s
 > > > dhcp-option=tag:infra-94-subnet,3,100.104.1.1
 > > > dhcp-range=set:infra-95-subnet,100.96.96.11,100.96.96.64,600s
 > > > dhcp-option=tag:infra-95-subnet,3,100.96.96.1
 > >
 > > Why?
 > >
 >
 > "Why" what?
 > If the question is the all other dhcp-ranges (unused for this
scenario),
 > the answer is because in production case these other networks
for each dhcp
 > range exist. These other unused ranges for this test case,
this cannot be a
 > problem.
 >
 > Thanks

No problem, no hardfeelings.

It was me who should have wrote in his initial reply


   Oops, that is a complex setup. Is really all the complexity
needed?


Anyway: Feel free to post, do known that it is been readed.


Groeten
Geert Stappers
-- 
 > this cannot be a problem.


___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk

http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss


___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss



___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Help with dnsmasq and vlans tags

2018-12-06 Thread Geert Stappers 
On Thu, Dec 06, 2018 at 06:52:11PM +0100, john doe wrote:
> On 12/6/2018 3:50 PM, jmperrote wrote:
>  dhcp-option=eth0,6,10.11.37.15 #dns primario
>  dhcp-option=eth0,1,255.255.255.0 # mascara de red
>  dhcp-option=eth0,option:router,10.11.37.1 # gateway
> 
>  dhcp-range=interface:eth1,set:VLAN_137,10.11.137.90,10.11.137.98,6h
>  dhcp-option=eth1,6,10.11.37.15 #dns primario
>  dhcp-option=eth1,1,255.255.255.0 # mascara de red
>  dhcp-option=eth1,option:router,10.11.137.1 # gateway
> 
>  dhcp-range=interface:eth2,set:VLAN_237,10.11.237.50,10.11.237.200,6h
>  dhcp-option=eth2,6,10.11.37.15 #dns primario
>  dhcp-option=eth2,1,255.255.255.0 # mascara de red
>  dhcp-option=eth2,option:router,10.11.237.1 # gateway
> 
> > 
> > Hello, ok trying a solution to resolv dnsmasq with vlans and one nic, I
> > do next
> > 
> > I reconfigured the dnsmasq with this and the mikrotik router with tagged
> > vlans.
> > 
> > dhcp-range=tag:eth0,set:eth0,10.11.37.50,10.11.37.200,6h
> > dhcp-range=tag:eth0,set:eth0,10.11.137.50,10.11.137.200,6h
> > dhcp-range=tag:eth0,set:eth0,10.11.237.50,10.11.237.200,6h
> > dhcp-option=tag:eth0,option:dns-server,10.11.37.15
> > dhcp-option=tag:eth0,option:dns-server,10.11.37.15
> > dhcp-option=tag:eth0,option:dns-server,10.11.37.15
> > dhcp-option=tag:eth0,option:router,10.11.137.1
> > dhcp-option=tag:eth0,option:router,10.11.37.1
> > dhcp-option=tag:eth0,option:router,10.11.237.1

Check the above config again.

| dhcp-range=tag:eth0.37,set:eth0,10.11.37.50,10.11.37.200,6h
| dhcp-range=tag:eth0.137,set:eth0,10.11.137.50,10.11.137.200,6h
| dhcp-range=tag:eth0.237,set:eth0,10.11.237.50,10.11.237.200,6h
| dhcp-option=tag:eth0.37,option:dns-server,10.11.37.15
| dhcp-option=tag:eth0.137,option:dns-server,10.11.37.15
| dhcp-option=tag:eth0.237,option:dns-server,10.11.37.15
| dhcp-option=tag:eth0.137,option:router,10.11.137.1
| dhcp-option=tag:eth0.37,option:router,10.11.37.1
| dhcp-option=tag:eth0.237,option:router,10.11.237.1

Is what I would expect.


> > The assign of ip work fine, each PC on each vlan pickup a IP on
> > corresponding vlan, but on 3 PCs allways assign the same gateway -->
> > 10.11.237.1
> > 
> 
> If it is working for most of the hosts,

If, only if.


> my guess is that you need to renew the lease on those hosts.
> 
> EG with dhclient:
> 
> $ dhclient -r  && dhclient 
> 
> Where  is the name of the interface on which the lease need to
> be released and acquired.


No, start with a static address at the clients.
Then check if connecting the "dnsmasq host with 3 VLANID" works.
Me and Murphy say that it doesn't work.
I say that the switch needs additional configuration.
Feel free to proof me wrong.


Groeten
Geert Stappers
-- 
Leven en laten leven

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Help with dnsmasq and vlans tags

2018-12-06 Thread john doe 
On 12/6/2018 3:50 PM, jmperrote wrote:
> El 2018-12-05 12:59, john doe escribió:
>> On 12/5/2018 1:58 PM, Geert Stappers wrote:
>>> On Wed, Dec 05, 2018 at 09:09:25AM -0300, jmperrote wrote:
 El 2018-12-04 12:26, john doe escribió:
> On 12/4/2018 12:02 PM, jmperrote wrote:
>>
>>  John Doe, sorry for my mistake, my actual configuration of dnsmasq
>> are:
>>
>> dhcp-range=interface:eth0,set:VLAN_37,10.11.37.50,10.11.37.200,6h
>> dhcp-option=eth0,6,10.11.37.15 #dns primario
>> dhcp-option=eth0,1,255.255.255.0 # mascara de red
>> dhcp-option=eth0,option:router,10.11.37.1 # gateway
>>
>> dhcp-range=interface:eth1,set:VLAN_137,10.11.137.90,10.11.137.98,6h
>>
>> dhcp-option=eth1,6,10.11.37.15 #dns primario
>> dhcp-option=eth1,1,255.255.255.0 # mascara de red
>> dhcp-option=eth1,option:router,10.11.137.1 # gateway
>>
>> dhcp-range=interface:eth2,set:VLAN_237,10.11.237.50,10.11.237.200,6h
>>
>> dhcp-option=eth2,6,10.11.37.15 #dns primario
>> dhcp-option=eth2,1,255.255.255.0 # mascara de red
>> dhcp-option=eth2,option:router,10.11.237.1 # gateway
>>
>> We have 3 nics on the system eth0/eth1/eth2, one for each VLAN, and
>> try to replace for one nic with VLANs tagged.
>>
>> We try the tag option and the dhcp assign ip on correct range for
>> each
>> PC on each vlan, but dnsmasq allways assign to the PC the same
>> gateway, that is the las vlan configured.
>>
>> For example on this configuraton assign the correct range to the PC,
>> but the gateway always assign 10.11.237.1 gateway, to all PC
>>
>> dhcp-range=interface:eth0.37,set:VLAN_37,10.11.37.90,10.11.37.98,6h
>> dhcp-option=eth0.37,6,10.11.37.15 #dns primario
>> dhcp-option=eth0.37,1,255.255.255.0 # mascara de red
>> dhcp-option=eth0.37,option:router,10.11.37.1 # gateway
>>
>> dhcp-range=interface:eth0.137,set:VLAN_137,10.11.137.90,10.11.137.98,6h
>>
>> dhcp-option=eth0.137,6,10.11.37.15 #dns primario
>> dhcp-option=eth0.137,1,255.255.255.0 # mascara de red
>> dhcp-option=eth0.137,option:router,10.11.137.1 # gateway
>>
>> dhcp-range=interface:eth0.237,set:VLAN_237,10.11.237.50,10.11.237.200,6h
>>
>> dhcp-option=eth0.237,6,10.11.37.15 #dns primario
>> dhcp-option=eth0.237,1,255.255.255.0 # mascara de red
>> dhcp-option=eth0.237,option:router,10.11.237.1 # gateway
>>
>>
>> It is necessary to use "vconfig" to configure virtual vlan interface
>> on the operating system, or can use tagged vlans from the router ?
>>
>
> To be able to answer your question I need to know the following:
>
>  - What hardware is the router (netgear, cisco ...)?
>  - What type of distribution (name and version) are you using
> 'vconfig'
> on (Linux, Oracle)?
>
> I can't answer your question without knowing your network topology,
> but
> if the router is VLAN tagging capable I would use it and also use the
> DHCP capability from that router.
>
> Also, to isolate whether it is a vlan configuration or a dnsmasq issue
> simply try the line I have provided, obviously you can change the Ip
> ranges to your liking.


 Hello john doe,
>>>
>>> Hello Mailinglist,
>>>

 Send the data:
  -- Router mikrotik RB1100 AH
  -- Ubuntu 16.04
  -- Using vconfig with 3 VLANs

 Yes, the router have capabilitie to dhcp,
 you recommend to use that instead of dnsmasq for dhcp ?.
>>>
>>> What I did read in the reply from john doe:
>>>
>>>   Other options might resolve the original problem.
>>>
>>>
>>> But, yes, it is possible to replace
>>> three NICs with single NIC plus three VLANs.  Surely for DHCP stuff.
>>> If three NICs were choose due high bandwidth usage,
>>> that can't be solved by "VLAN".
>>>
>>
>> I guess nick bonding could be used with VLAN.
> 
> Hello, ok trying a solution to resolv dnsmasq with vlans and one nic, I
> do next
> 
> I reconfigured the dnsmasq with this and the mikrotik router with tagged
> vlans.
> 
> dhcp-range=tag:eth0,set:eth0,10.11.37.50,10.11.37.200,6h
> dhcp-range=tag:eth0,set:eth0,10.11.137.50,10.11.137.200,6h
> dhcp-range=tag:eth0,set:eth0,10.11.237.50,10.11.237.200,6h
> dhcp-option=tag:eth0,option:dns-server,10.11.37.15
> dhcp-option=tag:eth0,option:dns-server,10.11.37.15
> dhcp-option=tag:eth0,option:dns-server,10.11.37.15
> dhcp-option=tag:eth0,option:router,10.11.137.1
> dhcp-option=tag:eth0,option:router,10.11.37.1
> dhcp-option=tag:eth0,option:router,10.11.237.1
> dhcp-option=tag:eth0,1,255.255.255.0
> 
> The assign of ip work fine, each PC on each vlan pickup a IP on
> corresponding vlan, but on 3 PCs allways assign the same gateway -->
> 10.11.237.1
> 

If it is working for most of the hosts, my guess is that you need to
renew the lease on those hosts.

EG with dhclient:

$ dhclient -r  && dhclient 

Wher

Re: [Dnsmasq-discuss] Help with dnsmasq and vlans tags

2018-12-06 Thread jmperrote 

El 2018-12-05 12:59, john doe escribió:

On 12/5/2018 1:58 PM, Geert Stappers wrote:

On Wed, Dec 05, 2018 at 09:09:25AM -0300, jmperrote wrote:

El 2018-12-04 12:26, john doe escribió:

On 12/4/2018 12:02 PM, jmperrote wrote:


 John Doe, sorry for my mistake, my actual configuration of dnsmasq
are:

dhcp-range=interface:eth0,set:VLAN_37,10.11.37.50,10.11.37.200,6h
dhcp-option=eth0,6,10.11.37.15 #dns primario
dhcp-option=eth0,1,255.255.255.0 # mascara de red
dhcp-option=eth0,option:router,10.11.37.1 # gateway

dhcp-range=interface:eth1,set:VLAN_137,10.11.137.90,10.11.137.98,6h
dhcp-option=eth1,6,10.11.37.15 #dns primario
dhcp-option=eth1,1,255.255.255.0 # mascara de red
dhcp-option=eth1,option:router,10.11.137.1 # gateway

dhcp-range=interface:eth2,set:VLAN_237,10.11.237.50,10.11.237.200,6h
dhcp-option=eth2,6,10.11.37.15 #dns primario
dhcp-option=eth2,1,255.255.255.0 # mascara de red
dhcp-option=eth2,option:router,10.11.237.1 # gateway

We have 3 nics on the system eth0/eth1/eth2, one for each VLAN, and
try to replace for one nic with VLANs tagged.

We try the tag option and the dhcp assign ip on correct range for 
each

PC on each vlan, but dnsmasq allways assign to the PC the same
gateway, that is the las vlan configured.

For example on this configuraton assign the correct range to the 
PC,

but the gateway always assign 10.11.237.1 gateway, to all PC

dhcp-range=interface:eth0.37,set:VLAN_37,10.11.37.90,10.11.37.98,6h
dhcp-option=eth0.37,6,10.11.37.15 #dns primario
dhcp-option=eth0.37,1,255.255.255.0 # mascara de red
dhcp-option=eth0.37,option:router,10.11.37.1 # gateway

dhcp-range=interface:eth0.137,set:VLAN_137,10.11.137.90,10.11.137.98,6h
dhcp-option=eth0.137,6,10.11.37.15 #dns primario
dhcp-option=eth0.137,1,255.255.255.0 # mascara de red
dhcp-option=eth0.137,option:router,10.11.137.1 # gateway

dhcp-range=interface:eth0.237,set:VLAN_237,10.11.237.50,10.11.237.200,6h
dhcp-option=eth0.237,6,10.11.37.15 #dns primario
dhcp-option=eth0.237,1,255.255.255.0 # mascara de red
dhcp-option=eth0.237,option:router,10.11.237.1 # gateway


It is necessary to use "vconfig" to configure virtual vlan 
interface

on the operating system, or can use tagged vlans from the router ?



To be able to answer your question I need to know the following:

 - What hardware is the router (netgear, cisco ...)?
 - What type of distribution (name and version) are you using 
'vconfig'

on (Linux, Oracle)?

I can't answer your question without knowing your network topology, 
but
if the router is VLAN tagging capable I would use it and also use 
the

DHCP capability from that router.

Also, to isolate whether it is a vlan configuration or a dnsmasq 
issue

simply try the line I have provided, obviously you can change the Ip
ranges to your liking.



Hello john doe,


Hello Mailinglist,



Send the data:
 -- Router mikrotik RB1100 AH
 -- Ubuntu 16.04
 -- Using vconfig with 3 VLANs

Yes, the router have capabilitie to dhcp,
you recommend to use that instead of dnsmasq for dhcp ?.


What I did read in the reply from john doe:

  Other options might resolve the original problem.


But, yes, it is possible to replace
three NICs with single NIC plus three VLANs.  Surely for DHCP stuff.
If three NICs were choose due high bandwidth usage,
that can't be solved by "VLAN".



I guess nick bonding could be used with VLAN.


Hello, ok trying a solution to resolv dnsmasq with vlans and one nic, I 
do next


I reconfigured the dnsmasq with this and the mikrotik router with tagged 
vlans.


dhcp-range=tag:eth0,set:eth0,10.11.37.50,10.11.37.200,6h
dhcp-range=tag:eth0,set:eth0,10.11.137.50,10.11.137.200,6h
dhcp-range=tag:eth0,set:eth0,10.11.237.50,10.11.237.200,6h
dhcp-option=tag:eth0,option:dns-server,10.11.37.15
dhcp-option=tag:eth0,option:dns-server,10.11.37.15
dhcp-option=tag:eth0,option:dns-server,10.11.37.15
dhcp-option=tag:eth0,option:router,10.11.137.1
dhcp-option=tag:eth0,option:router,10.11.37.1
dhcp-option=tag:eth0,option:router,10.11.237.1
dhcp-option=tag:eth0,1,255.255.255.0

The assign of ip work fine, each PC on each vlan pickup a IP on 
corresponding vlan, but on 3 PCs allways assign the same gateway --> 
10.11.237.1


Example
Dec  6 14:38:57 dnsmasq-dhcp[1717]: 4259865864 available DHCP range: 
10.11.137.50 -- 10.11.137.200
Dec  6 14:38:57 dnsmasq-dhcp[1717]: 4259865864 available DHCP range: 
10.11.237.50 -- 10.11.237.200
Dec  6 14:38:57 dnsmasq-dhcp[1717]: 4259865864 client provides name: 
networking3
Dec  6 14:38:57 dnsmasq-dhcp[1717]: 4259865864 DHCPREQUEST(eth0) 
10.11.137.96 10:78:d2:d7:b2:5c

Dec  6 14:38:57 dnsmasq-dhcp[1717]: 4259865864 tags: eth0
Dec  6 14:38:57 dnsmasq-dhcp[1717]: 4259865864 DHCPACK(eth0) 
10.11.137.96 10:78:d2:d7:b2:5c networking3
Dec  6 14:38:57 dnsmasq-dhcp[1717]: 4259865864 requested options: 
1:netmask, 28:broadcast, 2:time-offset, 3:router,
Dec  6 14:38:57 dnsmasq-dhcp[1717]: 4259865864 requested options: 
15:domain-name, 6:dns-server, 119:domain-sear

Re: [Dnsmasq-discuss] DNSMASQ wrong addresses allocated after changing DHCP Clients between Neutron vRouters

2018-12-06 Thread Luis Kleber 
Last days I install 2 servers, one with Centos7 and other with Debian8,
without Openstack/Neutron. Both with the same DNSMASQ config I originally
posted.
On both I was using version 2.76 and upgraded to 2.78, using the same
ethernet interface changing the IP address between 100.97.97.1/24 and
100.98.98.1/24, and everything works as expected. I also tested with 2
different interfaces ont each case and also worked fine.
The DHCP client always was the same in all cases (Debian8, Centos7, and
Centos7 with Neutron).

It seems that the problem only happens when using DNSMAQ with Neutron
routers.
How debug it better within Neutron?  Another cache table, or how see more
detailed debug infos?

Thanks
--
Luis  Kleber


Em sex, 30 de nov de 2018 às 19:07, Luis Kleber 
escreveu:

> Hi Stappers!
>
> No hardfeelings! There was only a question missing! :)
> Thanks for your reply and yes,  it's a complex setup because of the
> Neutron use (all installation needed).
>
> After explained the problem, I was expecting a help to "how better debug",
> how see some other logs, activate another debug, another configuration, and
> so on...
> I'll try if the same problem happens without Neutron. Only using a DNSMASQ
> with 2 different access interfaces/networks.
>
> Tanks.
> --
> Luis Kleber
>
>
> Em sex, 30 de nov de 2018 às 16:33, Geert Stappers 
> escreveu:
>
>> On Wed, Nov 28, 2018 at 08:49:57AM -0200, Luis Kleber wrote:
>> > Em ter, 27 de nov de 2018 às 20:12, Geert Stappers escreveu:
>> > > On Mon, Nov 26, 2018 at 04:42:05PM -0200, Luis Kleber wrote:
>> > > 
>> > > > dhcp-range=set:infra-70-subnet,100.101.1.11,100.101.1.64,600s
>> > > > dhcp-option=tag:infra-70-subnet,3,100.101.1.1
>> > > > dhcp-range=set:infra-71-subnet,100.101.2.11,100.101.2.64,600s
>> > > > dhcp-option=tag:infra-71-subnet,3,100.101.2.1
>> > > > dhcp-range=set:infra-72-subnet,100.98.98.11,100.98.98.64,600s
>> > > > dhcp-option=tag:infra-72-subnet,3,100.98.98.1
>> > >  infra-73 ... infra-92 
>> > > > dhcp-range=set:infra-93-subnet,100.103.8.11,100.103.8.64,600s
>> > > > dhcp-option=tag:infra-93-subnet,3,100.103.8.1
>> > > > dhcp-range=set:infra-94-subnet,100.104.1.11,100.104.1.64,600s
>> > > > dhcp-option=tag:infra-94-subnet,3,100.104.1.1
>> > > > dhcp-range=set:infra-95-subnet,100.96.96.11,100.96.96.64,600s
>> > > > dhcp-option=tag:infra-95-subnet,3,100.96.96.1
>> > >
>> > > Why?
>> > >
>> >
>> > "Why" what?
>> > If the question is the all other dhcp-ranges (unused for this scenario),
>> > the answer is because in production case these other networks for each
>> dhcp
>> > range exist. These other unused ranges for this test case, this cannot
>> be a
>> > problem.
>> >
>> > Thanks
>>
>> No problem, no hardfeelings.
>>
>> It was me who should have wrote in his initial reply
>>
>>
>>   Oops, that is a complex setup. Is really all the complexity needed?
>>
>>
>> Anyway: Feel free to post, do known that it is been readed.
>>
>>
>> Groeten
>> Geert Stappers
>> --
>> > this cannot be a problem.
>>
>> ___
>> Dnsmasq-discuss mailing list
>> Dnsmasq-discuss@lists.thekelleys.org.uk
>> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>>
>
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss