[dev] fd80 prefix allocation
Tran (US), Katherine K
katherine.k.tran at boeing.com
Tue Apr 21 16:42:03 EDT 2020
I did see that response. But, I wanted to know if there was a change made in FRR from Quagga. Since with Quagga, the routes displayed the Unique Local address – not the Link Local. We need the addresses to be routable Unique Local addresses (with the fd80 prefix), but link local addresses are not. Someone did explain to me that I could set route maps for “prefer global”. But, the scenario still does not seem to be working.
I was just trying to see if someone else had any other insight between the difference of Quagga and FRR regarding this matter.
From: Brandon Jackson [mailto:bjackson at napshome.net]
Sent: Tuesday, April 21, 2020 1:05 PM
To: dev at lists.frrouting.org
Subject: Re: [dev] fd80 prefix allocation
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.
On Tue, Apr 21, 2020, 13:40 Tran (US), Katherine K <katherine.k.tran at boeing.com<mailto:katherine.k.tran at boeing.com>> wrote:
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.
dev mailing list
dev at lists.frrouting.org<mailto:dev at lists.frrouting.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dev