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 Followed by this, repeatedly, forever: Jul 11 18:21:15 router-priamry bird6: OSPF: Received non-hello packet from unknown neighbor (src fe80::c67d:4fff:fe9f:945, iface em0) The relevant interface config: em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM> ether 00:0c:29:9c:5c:28 inet 70.32.199.66 netmask 0xffffffe0 broadcast 70.32.199.95 inet6 fe80::20c:29ff:fe9c:5c28%em0 prefixlen 64 scopeid 0x1 inet 70.32.199.65 netmask 0xffffffff broadcast 70.32.199.65 vhid 1 nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active carp: MASTER vhid 1 advbase 1 advskew 0 The bird config: log syslog all; debug protocols all; router id 70.32.199.66; protocol kernel { learn; # Learn all alien routes from the kernel # persist; # Don't remove routes on bird shutdown scan time 20; # Scan kernel routing table every 20 seconds import all; # Default is import all export all; # Default is export none # kernel table 5; # Kernel table to synchronize with (default: main) } # This pseudo-protocol watches all interface up/down events. protocol device { scan time 10; # Scan interfaces every 10 seconds } protocol ospf main { # tick 2; # rfc1583compat yes; import all; export all; area 900 { stub; nssa; interface "em0" { hello 1; dead 4; type broadcast; }; }; } And the config from the Cisco side: interface Vlan881 ip address 70.32.199.94 255.255.255.224 ip policy route-map LAB ipv6 enable ipv6 ospf hello-interval 1 ipv6 ospf 100 area 900 end ! route-map LAB permit 5 match ip address LAB set ip next-hop 10.120.0.93 ! ip access-list extended LAB permit ip 70.32.199.64 0.0.0.31 any ! ipv6 router ospf 100 router-id 10.120.9.1 area 900 nssa passive-interface default no passive-interface Vlan881 ... redistribute connected redistribute static ! Regards, Daniel
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.
Followed by this, repeatedly, forever:
Jul 11 18:21:15 router-priamry bird6: OSPF: Received non-hello packet from unknown neighbor (src fe80::c67d:4fff:fe9f:945, iface em0)
This is unrelated. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
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@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.
Ondrej Zajicek <santiago@crfreenet.org> writes:
On Fri, Jul 11, 2014 at 02:26:36PM -0400, Daniel Corbe wrote: When exporting external routes to NSSA areas, OSPF routers must have some global (preferably stub/loopback) addresses.
I turned off NSSA and stub support for the area in question and I still can't get the adjacency to come up. 10.120.9.1 1 exstart/other 00:01 em0 fe80::c67d:4fff:fe9f:945
participants (3)
-
Daniel Corbe -
Olivier Benghozi -
Ondrej Zajicek