[dev] fd80 prefix allocation

Brandon Jackson bjackson at napshome.net
Tue Apr 21 16:04:38 EDT 2020


If I'm not mistaken you already received a response in the FROG mailing
list explaining what you're seeing.

And what it was you were seeing is the Next hop addresses being displayed
as the link local of the neighbor. Which is totally fine.


Brandon Jackson

On Tue, Apr 21, 2020, 13:40 Tran (US), Katherine K <
katherine.k.tran at boeing.com> wrote:

> Hello,
>
>
>
> I asked this question to the FROG mailing list. But, I was wondering if it
> might be more of a developer question. I am trying to switch from Quagga to
> FRR.
>
>
>
> Would anyone know how FRR treats “fd80” prefixes?
>
>
>
> My configuration assigns “fd80” prefixes as Unique Local IPv6 Unicast
> Addresses (IETF RFC 4193), which can be routed. But, when looking at the
> added BGP routes, FRR shows “fe80” prefixes as the next-hop address.  The
> next-hop address should have a “fd80” prefix.
>
>
>
> Note: Quagga displays the correct “fd80” prefix whereas FRR does not.
>
>
>
>
>
> Thank you,
>
> Katherine
> _______________________________________________
> dev mailing list
> dev at lists.frrouting.org
> https://lists.frrouting.org/listinfo/dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20200421/489d41f0/attachment.html>


More information about the dev mailing list