On Fri, May 25, 2018 at 03:34:08PM +0200, Oliver Freyermuth wrote:
> Am 25.05.2018 um 15:30 schrieb Kevin Darbyshire-Bryant:
> >> On 25 May 2018, at 13:07, Oliver Freyermuth wrote:
> >>
> >> Dear dnsmasqers,
> >>
> >> I fear the following is a design issue of DHCPv6, but I wonder if there's
> >>
Am 25.05.2018 um 15:30 schrieb Kevin Darbyshire-Bryant:
>
>
>> On 25 May 2018, at 13:07, Oliver Freyermuth
>> wrote:
>>
>> Dear dnsmasqers,
>>
>> I fear the following is a design issue of DHCPv6, but I wonder if there's a
>> way to overcome it with dnsmasq...
>
>
> On 25 May 2018, at 13:07, Oliver Freyermuth
> wrote:
>
> Dear dnsmasqers,
>
> I fear the following is a design issue of DHCPv6, but I wonder if there's a
> way to overcome it with dnsmasq...
Hi Oliver,
I’ve a similar/same problem when rebooting some QNAP
On Friday 25 May 2018 14:07:34 Oliver Freyermuth wrote:
> Dear dnsmasqers,
>
> I fear the following is a design issue of DHCPv6, but I wonder if there's a
> way to overcome it with dnsmasq...
>
> When automatically deploying machines via PXE / network installer, there's
> usually first a
Dear dnsmasqers,
I fear the following is a design issue of DHCPv6, but I wonder if there's a way
to overcome it with dnsmasq...
When automatically deploying machines via PXE / network installer, there's
usually first a DHCPv6 client running in the installer,
and afterwards (when the machine