On Fri, Mar 24, 2017 at 03:29:28PM +0100, Martin Pieuchot wrote:
>
> Could you tell me if the diff below solve the issue?
Yes it solves it.
The router entry isn't marked as expired on timeout, but renewed, and
inet6 connectivity still works after 1 day of inactivity.
05:36:46.725925 2001:41d0:f
On Fri, Mar 24, 2017 at 03:29:28PM +0100, Martin Pieuchot wrote:
| I believe this is a regression introduced in r1.206 of netinet6/nd6.c.
That was a change made for a problem I reported, so I checked this new
diff too. Works for me (but I wasn't experiencing Sebastien's
problem).
Thanks Martin!
On Fri, Mar 24, 2017 at 03:29:28PM +0100, Martin Pieuchot wrote:
> It's wrong to call nd6_invalidate() at the beginning of nd6_free() since
> the default router selection logic check for the ND state of the entry.
Make sense. We did not intend to change default router selection.
It was introduced
On 24/03/17(Fri) 12:30, Sebastien Marie wrote:
> Hi,
>
> First, I am unsure to properly report the problem, so sorry about that.
> Feel free to require additionnal commands output...
>
> Since approx 1 mounth, I experiment ipv6 connectivity failure on
> localnet.
>
> Symptoms are simple:
>
> cl
Hi,
First, I am unsure to properly report the problem, so sorry about that.
Feel free to require additionnal commands output...
Since approx 1 mounth, I experiment ipv6 connectivity failure on
localnet.
Symptoms are simple:
clyde$ ping6 bert
PING bert (2001:41d0:fe39:c05c:215:c5ff:fe0b:8b7a): 5
