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 18/09/18 16:59, Bernard CLABOTS wrote:
> Hi all,
> I have been trying to replicate an issue of IP conflict on Open-WRT,
> the issue is randomly seen, and I expect in real life, it is related to
> a de-sync of the lease data base with the actual situation (in case a
> switch is between the cli
On 18/09/18 11:28, Kristian Evensen wrote:
> Hello,
>
> I recently updated one of my x86-based OpenWRT-routers to the latest
> nightly, which bumped dnsmasq to 2.80test6. After the update, I see
> that dnsmasq sometimes enters a crash loop. The crash occurs right
> startup (SIGSEV), and the backtr
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
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 only IPv6 address assigned via DHCP. The SLAAC-based
>> IPv6
Hi all, I have been trying to replicate an issue of IP conflict on Open-WRT,
the issue is randomly seen, and I expect in real life, it is related to a
de-sync of the lease data base with the actual situation (in case a switch is
between the client and the server and the server is rebooted e.g
Hello,
I recently updated one of my x86-based OpenWRT-routers to the latest
nightly, which bumped dnsmasq to 2.80test6. After the update, I see
that dnsmasq sometimes enters a crash loop. The crash occurs right
startup (SIGSEV), and the backtrace, looks as follows:
0x00406a78 in make_non_
