Getting started with OSPFv3

[Olivier Benghozi]

Hi Ondrej,

While this is not really related, I've also seen such logs in OSPFv2.
I use bird to announce NSSA N2 public /32 prefixes from the loopback interface lo (from protocol direct, using lo:xx aliases for IPv4 on Linux, and included interface "lo" in bird, protocol direct), and I've also noticed those kind of logs (but no issue: the routes are there and proper LSA type 7 are announced, anyway):

bird: WifOSPFUnsec: Cannot find forwarding address for NSSA-LSA X.Y.Z.130/32

However I announce several /32 like this and only this one triggers this log line at each daemon start (however this one has the first alias in the linux, is the first to be generated in the filter from-direct-to-ospf, and is also used in a filter defaultroute-from-ospf-to-kernel as krt_prefsrc=thisip).


No functional issue seen here, but it's still an error log...

For more information, in show ospf state, those loopback prefixes are all indicated with a "via" pointing to the local IP of the ethernet physical interface doing OSPF, and the forwarding address in the type 7 LSAs points to it (which is the right thing to do).


Olivier



Le 21 juil. 2014 à 11:33, Ondrej Zajicek <santiago at crfreenet.org> a écrit :
> On Fri, Jul 11, 2014 at 02:26:36PM -0400, Daniel Corbe wrote:
>> I'm trying to get an IPv6 adjacency up and running and I'm having
>> issues.  I'm hoping someone can point me in the right direction here.
>> When I bring up bird6 I get this:
>> 
>> Jul 11 18:08:38 router-priamry bird6: main: Cannot find forwarding address for NSSA-LSA ::/96
>> Jul 11 18:08:38 router-priamry bird6: main: Cannot find forwarding address for NSSA-LSA ::/0
>> Jul 11 18:08:38 router-priamry bird6: main: Cannot find forwarding address for NSSA-LSA ::ffff:0.0.0.0/96
> 
> When exporting external routes to NSSA areas, OSPF routers must have some
> global (preferably stub/loopback) addresses.