On Fri, Aug 03, 2018 at 08:11:46AM +0200, Florian Obser wrote:
> Anyone brave enough to OK this? I haven't heard from anyone that it
> breaks their internet...
No regressions so far on both my daily machine and gateway at home.
OK kn
Anyone brave enough to OK this? I haven't heard from anyone that it
breaks their internet...
On Wed, Aug 01, 2018 at 11:18:02PM +0200, Florian Obser wrote:
> I'm chasing a bug in IPv6 where ndp reports an entry as (incomplete)
> but when you try to reach that target no neighbor solicitation is
> s
Note that the neighbor entry is in state S (stale).
Whatever that means...
On Thu, Aug 02, 2018 at 04:44:57PM +0100, Stuart Henderson wrote:
> On 2018/08/01 23:18, Florian Obser wrote:
> > I'm chasing a bug in IPv6 where ndp reports an entry as (incomplete)
> > but when you try to reach that targe
On 2018/08/01 23:18, Florian Obser wrote:
> I'm chasing a bug in IPv6 where ndp reports an entry as (incomplete)
> but when you try to reach that target no neighbor solicitation is
> send.
Not sure if it's related or not but I've seen weird v6 behaviour on
my workstation for a while which I've bee
Running your diff on both my APU2 and X250, I no longer see NDP entries
staying expired, so this is an improvement!
More tests and review tomorrow, thanks for looking into this.
I'm chasing a bug in IPv6 where ndp reports an entry as (incomplete)
but when you try to reach that target no neighbor solicitation is
send.
I think the reason for that is that no new nd6_timer is scheduled
because the code thinks it is already scheduled. Maybe. I'm having a
hard time reproducing
