Re: [Dnsmasq-discuss] [PATCH] DHCPv6: Honor assigning IPv6 address based on MAC address

2019-11-24 Thread Geert Stappers 
On Thu, Nov 21, 2019 at 03:12:00PM +0100, Harald Jensås wrote:
> Bumping this patch again: 
> http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2018q4/012707.html
> 
> I see there have been several request to include this on the list:
> http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2019q1/012895.html 
> (and others ...)
> afaict there has not been any objections to the patch.
> 
> 
> We are trying to make Openstack Ironic deploy baremetal servers in a
> setup where Openstack Neutron is used. Neutron uses dnsmasq and the MAC
> address as identifier to assign IPv6 addresses in a static only setup,
> config details at bottom of this mail.
> 
> The problem with DUID/IAID changes as the baremetal node is moving
> trough the deployment phases UEFI->iPXE->Deploy Ramdisk resulting in
> "no address available" has always been a blocker for this to work. (The
> issue was discussed on this list a some time ago, 
> http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2017q1/thread.html#11267
> )
> 
> This patch solves this problem of changing DUID/IAID's.
> 
>  Is there a reason not to merge the patch?

A better question would be:

  What is needed to get this, reported as working, patch merged?


> 
> 
> 
> /usr/sbin/dnsmasq \
>  -k \
>  --no-hosts \
>  --no-resolv \
>  --pid-file=/var/lib/neutron/dhcp/6c9c3845-a101-47fa-a491-52e1ecb11e65/pid \
>  
> --dhcp-hostsfile=/var/lib/neutron/dhcp/6c9c3845-a101-47fa-a491-52e1ecb11e65/host
>  \
>  
> --addn-hosts=/var/lib/neutron/dhcp/6c9c3845-a101-47fa-a491-52e1ecb11e65/addn_hosts
>  \
>  
> --dhcp-optsfile=/var/lib/neutron/dhcp/6c9c3845-a101-47fa-a491-52e1ecb11e65/opts
>  \
>  
> --dhcp-leasefile=/var/lib/neutron/dhcp/6c9c3845-a101-47fa-a491-52e1ecb11e65/leases
>  \
>  --dhcp-match=set:ipxe,175 \
>  --dhcp-userclass=set:ipxe6,iPXE \
>  --local-service \
>  --bind-dynamic \
>  
> --dhcp-range=set:subnet-2b009f45-e0e2-4888-bb19-8d46e51717b8,fd12:3456:789a:1::,static,64,86400s
>  \
>  --dhcp-option-force=option:mtu,1450 \
>  --dhcp-lease-max=16777216 \
>  --conf-file= \
>  --domain=localdomain
> 
> $ cat /var/lib/neutron/dhcp/6c9c3845-a101-47fa-a491-52e1ecb11e65/host
> fa:16:3e:8b:07:9f,host-fd12-3456-789a-1--4.localdomain,[fd12:3456:789a:1::4]
> fa:16:3e:9f:b7:e3,host-fd12-3456-789a-1--ed.localdomain,[fd12:3456:789a:1::ed]
> 
> 

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] Domain name wildcard match in the --server option

2019-11-24 Thread Geert Stappers 
On Sun, Nov 24, 2019 at 09:09:20AM +0800, Top Quoter wrote:
> On Sun, Nov 24, 2019 at 1:10 AM Geert Stappers wrote:
> > On Sat, Nov 23, 2019 at 11:48:45PM +0800, New to Mailinglists wrote:
> > > In the config file, I have to write several lines for all domains .
> > > google.com.ar, .google.com.jp, etc. For example,
> > >
> > > server=/.google.com.ar/127.0.0.1#5053
> > > server=/.google.com.jp/127.0.0.1#5053
> > >
> > > I just wonder it may be more friendly to use only one line, as follows,
> > >
> > >server=/.google.com./127.0.0.1#5053
> > >
> > > to match any .google.com.XX
> > >
> >
> > Please report back if
> >
> > server=/.google.com.*/127.0.0.1#5053
> >
> > fits your needs.
> >
> >
> No.
> 
> server=/.google.com.*/127.0.0.1#5053
> 
> will not match .google.com.XX


Acknowledge.

Time will tell which other possiblities exist.


Regards
Geert Stappers

P.S.
Make reading in the discussion order possible.
Example given
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2019q4/013526.html
Reply below the text.

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