On Fri, 2020-05-01 at 16:52 +0200, Harald Jensas wrote:
> On Fri, 1 May 2020, 16:28 Petr Menšík, wrote:
> > Hi Harald and Geert,
> >
> > I looked at it and it is quite confusing what it does. Not quite
> > simple
> > to understand. I think it is not uncommon for dnsmasq code, but
> > this
> >
On Fri, 1 May 2020, 16:28 Petr Menšík, wrote:
> Hi Harald and Geert,
>
> I looked at it and it is quite confusing what it does. Not quite simple
> to understand. I think it is not uncommon for dnsmasq code, but this
> brings more knobs to make it more complicated.
>
> I tried to rewrite it
Hi Harald and Geert,
I looked at it and it is quite confusing what it does. Not quite simple
to understand. I think it is not uncommon for dnsmasq code, but this
brings more knobs to make it more complicated.
I tried to rewrite it hopefully with less repetitions and cleaner code.
However when I
Summary: Some one did have a look at the patch
On Thu, Apr 30, 2020 at 11:07:40AM +0200, Harald Jensås wrote:
>
> An attempt for a fix, preferring dhcp-host entries with CONFIG_ADDR or
> CONFIG_ADDR6 flag set. With this change I can use these two configs
> successfully:
>
>
On Wed, 2020-04-29 at 16:18 +0200, Harald Jensås wrote:
> Hi,
>
> We discovered an issue introduced in this commit:
> 137286e9baecf6a3ba97722ef1b49c851b531810
>
> Prior to this commit one could have two dhcp-host entries, one for
> IPv4
> and another for IPv6, for example:
>
>
