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

[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

[Geert Stappers]

On Thu, Dec 06, 2018 at 08:00:24PM -0200, Luis Kleber wrote:
> Em qui, 6 de dez de 2018 às 17:47, Brian Haley escreveu:
> > 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?
> > >
> >
> > 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)
>
> Hi Brian,
> 
> Ok, I'll file a bug there.

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

Re: [Dnsmasq-discuss] [DHCPV4] android devices issue makes able to use a reserved ipv4 address in dnsmasq

[Geert Stappers]

On Mon, Dec 10, 2018 at 12:21:00PM +, Inigo de la Fuente wrote:
> Hi all,
> 
> I have a question regarding to DHCPv4 leases.
> Doing some tests I have faced a possible android issue
> that I want to share with you.
> 
> 1.- I set the DHCP range of ipv4 address from 192.168.72.51 to 192.168.72.150
> in dnsmasq.conf.
> 2.- One windows pc is connected and get an ipv4 lease (192.168.72.65)
> 3.- One android device is connected and get an ipv4 lease (192.168.72.133)
> 4.- stop dnsmasq and remove all entries in dhcp.leases
> 5.- add dummy entries to dhcp.leases file till there is not any address
> available in the dhcp range and start dnsmasq again.
> 6.- windows pc is not able to obtain an ipv4 lease because all are occupied.
> Ping is not possible
> 7.- android device 'seems' to be able to use the saved leased ipv4 
> (192.168.72.133).
> Ping is possible
> 
> Here the output of dnsmasq at step 7:
> dnsmasq-dhcp: 93920162 available DHCP range: 10.173.190.51 -- 10.173.190.150
> dnsmasq-dhcp: 93920162 vendor class: HUAWEI:android:ANE
> dnsmasq-dhcp: 93920162 client provides name: HUAWEI_P20_lite-9a7e63d7d
> dnsmasq-dhcp: 93920162 DHCPDISCOVER(eth1) 00:be:3b:02:c1:02 no address 
> available
> dnsmasq-dhcp: 93920162 available DHCP range: 10.173.190.51 -- 10.173.190.150
> dnsmasq-dhcp: 93920162 vendor class: HUAWEI:android:ANE
> dnsmasq-dhcp: 93920162 client provides name: HUAWEI_P20_lite-9a7e63d7d
> dnsmasq-dhcp: 93920162 DHCPDISCOVER(eth1) 00:be:3b:02:c1:02 no address 
> available
> dnsmasq-dhcp: 93920162 available DHCP range: 10.173.190.51 -- 10.173.190.150
> 
> Why my device is able to ping with the last saved leased ipv4 address
> even if this address is reserved in dhcp.leases file?
 
Imaginary problem


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

[jmperrote]

El 2018-12-06 15:56, Geert Stappers escribió:

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




Finally we find a solution for dnsmasq with vlans

interface=eth0

#propiedades genericas
dhcp-option=6,10.11.37.15 #dns primario
dhcp-option=1,255.255.255.0 # mascara de red

dhcp-range=interface:eth0,set:vlan37,10.11.37.50,10.11.37.200,8h
dhcp-option=tag:vlan37,3,10.11.37.1 # #gateway/router
dhcp-option=tag:vlan37,28,10.11.37.255 # broadcast

dhcp-range=set:vlan137,10.11.137.50,10.11.137.200,8h
dhcp-option=tag:vlan137,3,10.11.137.1 #gateway/router
dhcp-option=tag:vlan137,28,10.11.137.255 #broadcast

dhcp-range=set:vlan237,10.11.237.50,10.11.237.200,8h
dhcp-option=tag:vlan237,3,10.11.237.1 #gateway/router
dhcp-option=tag:vlan237,28,10.11.237.255 #broadcast


The last problem was "dnmasq allways assign the same router for all 
clients" the solution was use the tag: option on dnsmasq.conf to 
identified the vlan comming the request. On the dnsmasq log Just next on 
the request we found -->


dnsmasq-dhcp[7800]: 2756951124 DHCPREQUEST(eth0) 10.11.237.95 
00:0a:e6:bf:1c:5d

Dec 10 12:30:59 dnsmasq-dhcp[7800]: 2756951124 tags: vlan237, eth0

The tag entry mark the vlans where become the request, so we to adjust 
the dnsmasq.conf to tell that use tag option on each option we want, for 
example on the roiter option.


Ragards



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

[Dnsmasq-discuss] [DHCPV4] ANDROID DEVICES ISSUE MAKES ABLE TO USE A RESERVED IPV4 ADDRESS IN DNSMASQ

[Inigo de la Fuente]

Hi all,

I have a question regarding to DHCPv4 leases.
Doing some tests I have faced a possible android issue that I want to share 
with you.

1.- I set the DHCP range of ipv4 address from 192.168.72.51 to 192.168.72.150 
in dnsmasq.conf.
2.- One windows pc is connected and get an ipv4 lease (192.168.72.65)
3.- One android device is connected and get an ipv4 lease (192.168.72.133)
4.- stop dnsmasq and remove all entries in dhcp.leases
5.- add dummy entries to dhcp.leases file till there is not any address 
available in the dhcp range and start dnsmasq again.
6.-  windows pc is not able to obtain an ipv4 lease because all are occupied. 
Ping is not possible
7.- android device 'seems' to be able to use the saved leased ipv4 
(192.168.72.133). Ping is possible

Here the output of dnsmasq at step 7:
"dnsmasq-dhcp: 93920162 available DHCP range: 10.173.190.51 -- 10.173.190.150
dnsmasq-dhcp: 93920162 vendor class: HUAWEI:android:ANE
dnsmasq-dhcp: 93920162 client provides name: HUAWEI_P20_lite-9a7e63d7d
dnsmasq-dhcp: 93920162 DHCPDISCOVER(eth1) 00:be:3b:02:c1:02 no address available
dnsmasq-dhcp: 93920162 available DHCP range: 10.173.190.51 -- 10.173.190.150
dnsmasq-dhcp: 93920162 vendor class: HUAWEI:android:ANE
dnsmasq-dhcp: 93920162 client provides name: HUAWEI_P20_lite-9a7e63d7d
dnsmasq-dhcp: 93920162 DHCPDISCOVER(eth1) 00:be:3b:02:c1:02 no address available
dnsmasq-dhcp: 93920162 available DHCP range: 10.173.190.51 -- 10.173.190.150"

Why my device is able to ping with the last saved leased ipv4 address even if 
this address is reserved in dhcp.leases file?

Best Regards




 Disclaimer 
This email and any files transmitted may contain proprietary and confidential 
information of ICT Group N.V. or any of its subsidiaries ("ICT") and is 
intended only for the (use of the) named recipient(s) above. If you have 
received this message in error or are not the intended or named recipient(s) of 
this message, please immediately notify the sender by return and delete this 
email message from your computer. Any views or opinions presented are solely 
those of its author and do not necessarily represent those of ICT. You are 
hereby notified that unauthorized disclosure, use, dissemination, forwarding, 
printing or copying of this e-mail and its attachments either whole or partial 
of its contents is strictly prohibited. ICT cannot guarantee that email 
communications are secured and error-free and does not accept any liability for 
damages resulting from the use of email. The general terms and conditions of 
purchase respectively sale and delivery of ICT are applicable to all 
transactions and undertakings resulting therefrom.

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

[Dnsmasq-discuss] build failure on master with NO_DHCPv6 and fix....

[Kevin Darbyshire-Bryant]

Hi Simon,

master has a build error when building without HAVE_DHCPv6

option.c: In function 'dhcp_context_free':
option.c:1042:15: error: 'struct dhcp_context' has no member named 
'template_interface'
   free(ctx->template_interface);

Sadly, need to put in a little conditional compilation ifdef'erey

Simplest patch in the world attached



Cheers,

Kevin D-B

012C ACB2 28C6 C53E 9775  9123 B3A2 389B 9DE2 334A


0001-option-fix-non-DHCPv6-build-error.patch
Description: 0001-option-fix-non-DHCPv6-build-error.patch
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

[Dnsmasq-discuss] DHCP DOS caused by malformed dhcp discover packet

[P, Sreelakshmi]

Hi All,

A malformed dhcp discover packet can cause dnsmasq to be unresponsive for a 
small amount of time.  If this was repeated over time an attacker could make 
the dhcp service unresponsive DOSing the box.

Does dnsmasq validate the incoming DHCP packet? We are using v2.78. Are there 
any fixes related to handling malformed DHCP packet?

Thanks!

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

Re: [Dnsmasq-discuss] Validation for malformed DHCP packets in dnsmasq

[September 1993]

On Mon, Dec 10, 2018 at 05:59:11AM +, P, Sreelakshmi wrote:
> Hi All,
> 
> Does anyone has any update on this?

Understanding http://www.catb.org/~esr/faqs/smart-questions.html
is a good start.
 
> Thanks!

For making it possible to read in the discussion order.

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