On 2/19/2019 4:08 PM, Bjørn Mork wrote:
Brian Rak writes:
They both negotiate the Extended next hop capability, and JunOS
accepts the routes just fine if I make Cumulus only send 16 byte
nexthops (still IPv6, just not containing a link-local address)
Ah, right. And the RFC2545 requirements
Brian Rak writes:
> They both negotiate the Extended next hop capability, and JunOS
> accepts the routes just fine if I make Cumulus only send 16 byte
> nexthops (still IPv6, just not containing a link-local address)
Ah, right. And the RFC2545 requirements are also fulfilled?:
The link-loca
On 2/19/2019 3:19 PM, Bjørn Mork wrote:
Brian Rak writes:
I'm running into an issue where JunOS will not accept BGP updates
containing a MP_REACH_NLRI attribute with a 32 byte nexthop. As soon
as I send one, the session gets closed and the following logged:
rpd[16187]: bgp_read_v4_update:12
Brian Rak writes:
> I'm running into an issue where JunOS will not accept BGP updates
> containing a MP_REACH_NLRI attribute with a 32 byte nexthop. As soon
> as I send one, the session gets closed and the following logged:
>
> rpd[16187]: bgp_read_v4_update:12111: NOTIFICATION sent to
> fe80::a
I'm running into an issue where JunOS will not accept BGP updates
containing a MP_REACH_NLRI attribute with a 32 byte nexthop. As soon as
I send one, the session gets closed and the following logged:
rpd[16187]: bgp_read_v4_update:12111: NOTIFICATION sent to
fe80::ae1f:6bff:fe8a:435d (Externa
5 matches
Mail list logo