Re: [Dnsmasq-discuss] Determine wireless SSID

2019-01-23 Thread Luis Kleber 
If you can enable "DHCP option 82" on your Netgear Wifi then I think Yes.
When enabled, look for DHCP packets on dnsmasq server  "tcpdump -i ethx
-nnvvvN port 67"

Something like this should appear:
Circuit-ID SubOption 1 :  "Netgear wifi guest ..."

In dnsmasq config file:
dhcp-circuitid=set:TEST1,"Netgear wifi guest ..."
dhcp-range=net:TEST1,192.168.31.171,192.168.31.179,86400s
dhcp-option=tag:TEST1,3,192.168.31.1
dhcp-option=tag:TEST1,option:dns-server,8.8.8.8



Em qua, 23 de jan de 2019 às 17:51, Donald Muller 
escreveu:

> Since no one responded I am assuming this is not possible.
>
>
>
> *From:* Dnsmasq-discuss  *On
> Behalf Of *Donald Muller
> *Sent:* Friday, January 11, 2019 4:58 PM
> *To:* dnsmasq-discuss@lists.thekelleys.org.uk
> *Subject:* [Dnsmasq-discuss] Determine wireless SSID
>
>
>
> This is probably not possible but I thought I would ask.
>
>
>
> Is it possible for DNSMASQ to determine the SSID for a DHCP request? I
> would like to be able to assign different values for devices using the
> guest network. DNSMASQ is running on my QNAP NAS while I have a Netgear
> wireless router providing the wireless connectivity.
>
>
>
> Thanks
>
>
>
> -
>
> “Everyone is entitled to his own opinion, but not to his own facts.” -
> Daniel Patrick Moynihan
>
>
> ___
> 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] DNSMASQ wrong addresses allocated after changing DHCP Clients between Neutron vRouters

2018-12-10 Thread Luis Kleber 
Hi.
https://bugs.launchpad.net/neutron/+bug/1807382

--
Luis Kleber

>
>
> What became the URL of that bug report?
>
>
> 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
>
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

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
> > <http://100.97.97.1/24> and 100.98.98.1/24 <http://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  > <mailto:luis.kle...@gmail.com>> 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
> &g

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

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

2018-11-30 Thread Luis Kleber 
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

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

2018-11-28 Thread Luis Kleber 
Hi Stappers.

"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

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?
>
> ___
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss@lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>


-- 

Luís Henrique Kleber
Smart6 Tecnologia em Internet

Av. Senador Tarso Dutra 161, sala 1607

Petrópolis  - Porto Alegre/RS  90690-140

(51) 4042-1284

www.smart6.com.br

E-mail: l...@smart6.com.br
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

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

2018-11-26 Thread Luis Kleber 
47283 available DHCP range:
100.101.8.11 -- 100.101.8.64
Nov 26 11:12:10 dnsmasq-dhcp[3975]: 1712147283 available DHCP range:
100.102.1.11 -- 100.102.1.64
Nov 26 11:12:10 dnsmasq-dhcp[3975]: 1712147283 available DHCP range:
100.102.2.11 -- 100.102.2.64


Thanks any help
--
Luis Kleber
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

[Dnsmasq-discuss] DNSMASQ wrong network DHCPOFFERs

2018-11-09 Thread Luis Kleber 
I'm using Dnsmasq like DHCP server for multi networks with Neutron and each
network in a VLAN.
Everything works fine, but sometimes DNSMASK offers wrong addresses.

It seems to be related to neutron-dhcp-agent restart, broadcast dhcp
request flag, and a server with many addresses allocated to clientes, but
i'm not sure.

Below more details. It's not easy to reproduce.

> Linux Namespace used by Neutron as DHCP server.
*[root@devel91 ~] ip netns exec qdhcp-3a07cc53-9944-4420-9b76-fa32e41922f5
ifconfig*
*lo: flags=73  mtu 65536*
*inet 127.0.0.1  netmask 255.0.0.0*
*inet6 ::1  prefixlen 128  scopeid 0x10*
*loop  txqueuelen 1000  (Local Loopback)*
*RX packets 804  bytes 61104 (59.6 KiB)*
*RX errors 0  dropped 0  overruns 0  frame 0*
*TX packets 804  bytes 61104 (59.6 KiB)*
*TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0*

*tape56ef56c-66: flags=4163  mtu 1500*
*inet 100.97.97.3  netmask 255.255.255.0  broadcast 100.97.97.255*
*inet6 fe80::f816:3eff:fe94:ee91  prefixlen 64  scopeid 0x20*
*ether fa:16:3e:94:ee:91  txqueuelen 1000  (Ethernet)*
*RX packets 174520  bytes 49840349 (47.5 MiB)*
*RX errors 0  dropped 0  overruns 0  frame 0*
*TX packets 176548  bytes 57602628 (54.9 MiB)*
*TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0*


Dnsmasq version 2.78  Copyright (c) 2000-2017 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus no-i18n IDN2 DHCP DHCPv6 no-Lua
TFTP no-conntrack ipset auth DNSSEC loop-detect inotify
It happens with version 2.76 too.


I'm using a script to generate a limited number of MACs (60) for DHCP
Requests. I have a DNSMASK pool with 54 addresses to be offered.
*loop do*
*  XX=$(printf "%02X\n" $(shuf -i 11-70 -n 1))*
*  sleep 1*
*  dhtest -i em2 -f -m A0:11:$XX:33:44:$XX   #The "-f" FLAG is for
broadcast DHCP request used by TP-LINK and other vendors CPE's*
*done*


The DHCP namespace IP address is *100.97.97.3/24 *.
The dnsmasq config for this network should give addresses in the range
 *100.97.97.11
- 100.97.97.64*, and gateway *100.97.97.1* and 2 DNS.
There is another namespace with IP 100.97.97.2 and 2 other namespaces
working with HA (VRRP with IP 100.97.97.1) all in the same LAN
(network/subnet).

Bellow are some logs to try to find the problem point.

> MAC* a0:11:2c:33:44:2c *got IP *100.97.97.61* address while DNSMASQ was
running with OLD PID 12128 (PID before Dnsmasq proccess restart).
Nov  7 14:22:25 dnsmasq-dhcp[12128]: 1914494840
DHCPDISCOVER(tape56ef56c-66) a0:11:2c:33:44:2c
Nov  7 14:22:26 dnsmasq-dhcp[12128]: 1914494840 DHCPOFFER(tape56ef56c-66)
100.97.97.61 a0:11:2c:33:44:2c
Nov  7 14:22:26 dnsmasq-dhcp[12128]: 1914494840 DHCPREQUEST(tape56ef56c-66)
100.97.97.61 a0:11:2c:33:44:2c
Nov  7 14:22:26 dnsmasq-dhcp[12128]: 1914494840 DHCPACK(tape56ef56c-66)
100.97.97.61 a0:11:2c:33:44:2c
Nov  7 14:23:39 dnsmasq-dhcp[12128]: 958193258 DHCPDISCOVER(tape56ef56c-66)
a0:11:2c:33:44:2c
Nov  7 14:23:40 dnsmasq-dhcp[12128]: 958193258 DHCPOFFER(tape56ef56c-66)
100.97.97.61 a0:11:2c:33:44:2c
Nov  7 14:23:40 dnsmasq-dhcp[12128]: 958193258 DHCPREQUEST(tape56ef56c-66)
100.97.97.61 a0:11:2c:33:44:2c
Nov  7 14:23:40 dnsmasq-dhcp[12128]: 958193258 DHCPACK(tape56ef56c-66)
100.97.97.61 a0:11:2c:33:44:2c

> systemctl restart neutron-dhcp-agent.service (this was at 14:23:xx)

> MAC *a0:11:11:33:44:11* got IP *100.97.97.61* address while DNSMASQ was
running with NEW PID 39632 (PID after Dnsmasq restart).
Nov  7 14:24:16 dnsmasq-dhcp[39632]: 131303615 DHCPDISCOVER(tape56ef56c-66)
a0:11:11:33:44:11
Nov  7 14:24:16 dnsmasq-dhcp[39632]: 131303615 DHCPOFFER(tape56ef56c-66)
100.97.97.61 a0:11:11:33:44:11
Nov  7 14:24:16 dnsmasq-dhcp[39632]: 131303615 DHCPREQUEST(tape56ef56c-66)
100.97.97.61 a0:11:11:33:44:11
Nov  7 14:24:16 dnsmasq-dhcp[39632]: 131303615 DHCPACK(tape56ef56c-66)
100.97.97.61 a0:11:11:33:44:11
Nov  7 14:27:12 dnsmasq-dhcp[39632]: 825015409 DHCPDISCOVER(tape56ef56c-66)
a0:11:11:33:44:11
Nov  7 14:27:13 dnsmasq-dhcp[39632]: 825015409 DHCPOFFER(tape56ef56c-66)
100.97.97.61 a0:11:11:33:44:11
Nov  7 14:27:13 dnsmasq-dhcp[39632]: 825015409 DHCPREQUEST(tape56ef56c-66)
100.97.97.61 a0:11:11:33:44:11
Nov  7 14:27:13 dnsmasq-dhcp[39632]: 825015409 DHCPACK(tape56ef56c-66)
100.97.97.61 a0:11:11:33:44:11
Nov  7 14:27:32 dnsmasq-dhcp[39632]: 1448165127
DHCPDISCOVER(tape56ef56c-66) a0:11:11:33:44:11
Nov  7 14:27:33 dnsmasq-dhcp[39632]: 1448165127 DHCPOFFER(tape56ef56c-66)
100.97.97.61 a0:11:11:33:44:11
Nov  7 14:27:33 dnsmasq-dhcp[39632]: 1448165127 DHCPREQUEST(tape56ef56c-66)
100.97.97.61 a0:11:11:33:44:11
Nov  7 14:27:33 dnsmasq-dhcp[39632]: 1448165127 DHCPACK(tape56ef56c-66)
100.97.97.61 a0:11:11:33:44:11

> MAC* a0:11:2c:33:44:2c*  got IP *100.101.1.59* address while DNSMASQ was
running with new PID 39632.
> The problem was this address that doesn't belong to this network. But
this address offered  exist on dnsmasq config (config bellow).
Nov