Hello Simon,
>> I've reactivated the patch locally and observing it since 4 days. Todays
>> night associated
>> IPv6 names got lost again directly during IP prefix change process, the log
>> shows it clearly
>> (see log 1). So I would vote again for retrying during some extended
>> timeframe e
Hello Simon,
>>> FWIW the strategy in the code is to continue trying to ping putative
>>> addresses more-or-less forever, with increasing backoff, _except_
>>> when a call to sendto()
>>> returns EHOSTUNREACH (no route to host) which causes the code to give up.
>>
>> Is it possible that it coll
Hello Simon,
> If you look, lots of things are different between the two logs. In the
second one,
> dhcpcd is doing routing table changes, for instance. That could explain
why dnsmasq
> gives up trying to confirm SLAAC addresses because it gets transient "no
route to host"
> returns. (see previ
On 18/09/18 23:03, line wrap clean up wrote:
> On Tue, Sep 18, 2018 at 11:13:27PM +0200, Andrey Vakhitov wrote:
> Hi Simon,
>
>>> I've set it up as you suggested, initially name resolution seems
>>> to work fine. But after some days of operation (and some nightly
>>> reconnects) dnsmasq seems to l
On 18/09/18 23:03, line wrap clean up wrote:
> Strange thing: sometimes after reconnect I can observe expected behaviour
> (like you described it, see log 1), sometimes not (SLAAC-CONFIRM is missing,
> see log 2)
>
> -- log1
> Sep 17 20:22:45 rtr dnsmasq-dhcp[7855]: DHCPv6 statel
On Tue, Sep 18, 2018 at 11:13:27PM +0200, Andrey Vakhitov wrote:
Hi Simon,
>> I've set it up as you suggested, initially name resolution seems
>> to work fine. But after some days of operation (and some nightly
>> reconnects) dnsmasq seems to loose associated IPv6 adresses: DNS
>> request reports
On 10/09/18 19:51, Andrey Vakhitov wrote:
> Hello Simon & Uwe,
>
>> unfortunately that problem is seen often with providers in Germany, although
>> the large ones no longer
>> do it (or allow to disable the disconnect). The problem is that German
>> providers automatically
>> disconnect the PPP
Hello Simon & Uwe,
> unfortunately that problem is seen often with providers in Germany, although
> the large ones no longer
> do it (or allow to disable the disconnect). The problem is that German
> providers automatically
> disconnect the PPPoE connection every 24 hrs. After reconnecting you
> Subject: Re: [Dnsmasq-discuss] clients of DHCPv6 with constructed IPv6
> address range are not notified on address range change
>
> Dnsmasq doesn't implement RECONFIGURE. It probably should. The main
> problem, from a quick look at the RFC, is that RECONFIGURE mandates use
> of sec
Dnsmasq doesn't implement RECONFIGURE. It probably should. The main
problem, from a quick look at the RFC, is that RECONFIGURE mandates use
of security mechanism, and dnsmasq doesn't implement that either!
The intention is that address change is a gradual process. The old
address gets deprecated w
Thanks for a great dnsmasq software.
I'm using dnsmasq 2.79 in combination with IPv6 prefix delegation. The
prefixes are changing daily due to daily reconnect of upstream router.
Dhcpcd is used to handle prefix delegation on external interface and apply
new address to internal interface (dmz0).
11 matches
Mail list logo
