On Mon, Aug 26, 2019 at 8:33 PM Frank Bulk <fbulk@mypremieronline.com> wrote:

FYI, saw it again this morning:

Aug 26 05:42:02 207.32.15.28 Rib: mpbgp_recv_mpreach: peer 2001:504:27::d1af:0:1 (AS 53679) link-local next hop fe80::e2ac:f1ef:fe4b:d93b%10000 improper, ignoring this next-hop
Aug 26 05:42:02 207.32.15.28 Rib: mpbgp_recv_mpreach: peer 2001:504:27::d1af:0:2 (AS 53679) link-local next hop fe80::e2ac:f1ef:fe4b:d93b%10000 improper, ignoring this next-hop

Frank

-----Original Message-----
From: MICE Discuss <MICE-DISCUSS@LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk
Sent: Wednesday, August 21, 2019 8:00 AM
To: MICE-DISCUSS@LISTS.IPHOUSE.NET
Subject: [MICE-DISCUSS] Of minor note

Our route logged these two items Monday morning with MICE's AS:

Aug 19 10:35:41 207.32.15.28 Rib: mpbgp_recv_mpreach: peer 2001:504:27::d1af:0:2 (AS 53679) link-local next hop fe80::e2ac:f1ef:fe4b:d93b%10000 improper, ignoring this next-hop
Aug 19 11:08:50 207.32.15.28 Rib: mpbgp_recv_mpreach: peer 2001:504:27::d1af:0:2 (AS 53679) link-local next hop fe80::e2ac:f1ef:fe4b:d93b%10000 improper, ignoring this next-hop

Not sure what that was about.

Frank