Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Apr 2022 05:50:54 +0000
From:      bugzilla-noreply@freebsd.org
To:        net@FreeBSD.org
Subject:   [Bug 263288] IPv6 system not responding to Neighbor Solicitation
Message-ID:  <bug-263288-7501-yj4E7Tr7qh@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-263288-7501@https.bugs.freebsd.org/bugzilla/>
References:  <bug-263288-7501@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263288

--- Comment #10 from wcarson.bugzilla@disillusion.net ---
I=E2=80=99m not sure what to make of this, but it does seem to be what I de=
scribed
originally:

Apr 21 00:39:53 roast kernel: nd6_ns_input: NS packet from non-neighbor
Apr 21 00:39:53 roast kernel: nd6_ns_input: src=3D2600:3c00::8678:acff:fe1c=
:ec41
Apr 21 00:39:53 roast kernel: nd6_ns_input: dst=3Dff02:1::1:ffb0:a56f
Apr 21 00:39:53 roast kernel: nd6_ns_input: tgt=3D2600:3c00::f03c:91ff:feb0=
:a56f

However in the above debug message it added an extra :1 after ff02 in the
destination that does not appear in the tcpdump. Is that normal?

Also how does it decide what is a non-neighbor? The src & tgt look to be on=
 the
same /64 to me.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263288-7501-yj4E7Tr7qh>