Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Sep 2024 12:15:52 +0200
From:      DutchDaemon - FreeBSD Forums Administrator <DutchDaemon@FreeBSD.org>
To:        freebsd-net@freebsd.org
Subject:   Re: IPv6 neighbor flaps for ISP router are occurring frequently
Message-ID:  <380a4641-9300-4803-bd38-819beb77ed21@FreeBSD.org>
In-Reply-To: <80124FC7-3C96-489C-803D-D0310FBA3D05@distal.com>
References:  <89F4F5A4-E3D9-4A43-84F6-908E3FA221A6@distal.com> <83BCC913-3375-4847-B720-5F06D76F6646@distal.com> <c26dc20a-c6c9-454c-8763-ae21d8b68b20@denninger.net> <6CFC398B-BC5C-4CFC-8733-8D9732B121CA@distal.com> <C9F6C11F-A0E9-4E39-B56E-5F5D564D0021@distal.com> <80124FC7-3C96-489C-803D-D0310FBA3D05@distal.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------------jMIOUNCI1ujl0Or9x3WtwTId
Content-Type: multipart/mixed; boundary="------------EF8EhzaI0M5dfD0BCoAsNM7J";
 protected-headers="v1"
From: DutchDaemon - FreeBSD Forums Administrator <DutchDaemon@FreeBSD.org>
To: freebsd-net@freebsd.org
Message-ID: <380a4641-9300-4803-bd38-819beb77ed21@FreeBSD.org>
Subject: Re: IPv6 neighbor flaps for ISP router are occurring frequently
References: <89F4F5A4-E3D9-4A43-84F6-908E3FA221A6@distal.com>
 <83BCC913-3375-4847-B720-5F06D76F6646@distal.com>
 <c26dc20a-c6c9-454c-8763-ae21d8b68b20@denninger.net>
 <6CFC398B-BC5C-4CFC-8733-8D9732B121CA@distal.com>
 <C9F6C11F-A0E9-4E39-B56E-5F5D564D0021@distal.com>
 <80124FC7-3C96-489C-803D-D0310FBA3D05@distal.com>
In-Reply-To: <80124FC7-3C96-489C-803D-D0310FBA3D05@distal.com>

--------------EF8EhzaI0M5dfD0BCoAsNM7J
Content-Type: multipart/alternative;
 boundary="------------rHFVdi1ebvQZ5Buwb1p3hxna"

--------------rHFVdi1ebvQZ5Buwb1p3hxna
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: base64

T24gMTktOS0yMDI0IDE5OjQzLCBDaHJpcyBSb3NzIHdyb3RlOg0KPg0KPj4gT24gU2VwIDE3
LCAyMDI0LCBhdCAxNDo0NiwgQ2hyaXMgUm9zczxjcm9zcytmcmVlYnNkQGRpc3RhbC5jb20+
ICB3cm90ZToNCj4+DQo+PiBIbW0uICBXZWxsLCBJIHVwZGF0ZWQgbXkgcmVsZW5nLzE0LjEg
dHJlZSBhbmQgYnVpbHQgYSBuZXcga2VybmVsIGxhc3QgbmlnaHQuDQo+PiBJIHJlYm9vdGVk
IGFuZCBhZnRlciBkaGNwY2Qgc3RhcnRlZCB1cCBpdCB3YXMgZW1pdHRpbmcgdGhlIHNhbWUg
bm90aWNlcw0KPj4gZm9yIG1hbnkgaG91cnMuICBCdXQsIGF0IGFib3V0IDA3OjMwIHRoaXMg
bW9ybmluZyBpdCBzdG9wcGVkLiAgSXTigJlzIG5vdyBiZWVuDQo+PiA3IGhvdXJzIHNpbmNl
IHRoZXJlIGhhdmUgYmVlbiBhbnkgc3VjaCBub3RpY2VzIGZyb20gZGhjcGNkLiAgQW5kLCBJ
IGNhbuKAmXQNCj4+IHRoaW5rIG9mIHdoYXQgY291cGxlLiBoYW5nZWQuIGRoY3BjZCBoYXMg
YmVlbiBydW5uaW5nIGZvciAxNSsgaG91cnMsDQo+PiBjb21wbGFpbmVkIGZvciA4IGhvdXJz
LCB0aGVuIHN0b3BwZWQgZm9yIDcuICBJ4oCZbGwga2VlcCBhbiBleWUgb24gaXQsIGJ1dA0K
Pj4gc3VmZmljZSB0byBzYXkgSeKAmW0gcGVycGxleGVkLg0KPiBBbHJpZ2h0LiAgQ29taW5n
IGJhY2sgdG8gdGhpcywgSSB3YXMgY2xlYXJseSBub3QgcGF5aW5nIGF0dGVudGlvbi4gIEF0
IHRoZQ0KPiB0aW1lIEkgc3RvcHBlZCBzZWVpbmcgdGhlIGFmb3JlbWVudGlvbmVkIHByb2Js
ZW0sIGEgbmV3IG9uZSBzdGFydGVkLiAgVGhlcmUNCj4gc2VlbWVkIHRvIGJlIHNvbWUgc29y
dCBvZiBsaW5rIGZsYXAgb24gbXkgbG9jYWwgaW50ZXJmYWNlcyBhIGNvdXBsZQ0KPiBvZiB0
aW1lcyB0aGUgbW9ybmluZyBvZiBTZXB0IDE3LCBhbmQgYWZ0ZXIgdGhhdCBJUHY2IHdhc27i
gJl0IHdvcmtpbmcuDQo+IFRoZSBuZXh0LWhvcCBhbmQgcm91dGVyIHNlZW1zIHRvIGJlIHVu
cmVhY2hhYmxlIG5vdy4NCkFyZSB5b3UgdXNpbmcgcGY/IEZyZWVCU0QtRU4tMjQ6MTYucGYN
Cg==
--------------rHFVdi1ebvQZ5Buwb1p3hxna
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF=
-8">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div class=3D"moz-cite-prefix">On 19-9-2024 19:43, Chris Ross wrote:<=
br>
    </div>
    <blockquote type=3D"cite"
      cite=3D"mid:80124FC7-3C96-489C-803D-D0310FBA3D05@distal.com">
      <pre class=3D"moz-quote-pre" wrap=3D"">

</pre>
      <blockquote type=3D"cite">
        <pre class=3D"moz-quote-pre" wrap=3D"">On Sep 17, 2024, at 14:46,=
 Chris Ross <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:cross+freeb=
sd@distal.com">&lt;cross+freebsd@distal.com&gt;</a> wrote:

Hmm.  Well, I updated my releng/14.1 tree and built a new kernel last nig=
ht.
I rebooted and after dhcpcd started up it was emitting the same notices
for many hours.  But, at about 07:30 this morning it stopped.  It=E2=80=99=
s now been
7 hours since there have been any such notices from dhcpcd.  And, I can=E2=
=80=99t
think of what couple. hanged. dhcpcd has been running for 15+ hours,
complained for 8 hours, then stopped for 7.  I=E2=80=99ll keep an eye on =
it, but
suffice to say I=E2=80=99m perplexed.
</pre>
      </blockquote>
      <pre class=3D"moz-quote-pre" wrap=3D"">
Alright.  Coming back to this, I was clearly not paying attention.  At th=
e
time I stopped seeing the aforementioned problem, a new one started.  The=
re
seemed to be some sort of link flap on my local interfaces a couple
of times the morning of Sept 17, and after that IPv6 wasn=E2=80=99t worki=
ng.
The next-hop and router seems to be unreachable now.</pre>
    </blockquote>
    Are you using pf? FreeBSD-EN-24:16.pf<span
    style=3D"white-space: pre-wrap">
</span>
  </body>
</html>

--------------rHFVdi1ebvQZ5Buwb1p3hxna--

--------------EF8EhzaI0M5dfD0BCoAsNM7J--

--------------jMIOUNCI1ujl0Or9x3WtwTId
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature.asc"

-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQSDIpfQllw48uFsWk/r4FMJZEPckQUCZu1LWAUDAAAAAAAKCRDr4FMJZEPckW1X
AQDxk33wWe6yvgQcKxelVUJVoQthbLjxK7lc9UbfMHRZHAEAy2KPCbZNIiMl2imgxaP6cmYAnzjd
UtaCL0ukglWNlAI=
=aZM6
-----END PGP SIGNATURE-----

--------------jMIOUNCI1ujl0Or9x3WtwTId--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?380a4641-9300-4803-bd38-819beb77ed21>