Mailing List Archive

[Bug 374] New: OSPF routes from new neighbor set inactive by zebra because neighbor "inactive"
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug
report.

http://bugzilla.quagga.net/show_bug.cgi?id=374

Summary: OSPF routes from new neighbor set inactive by zebra
because neighbor "inactive"
Product: Quagga
Version: 0.99.6
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: Very High
Component: zebra
AssignedTo: maintainers@quagga.net
ReportedBy: virginb@oslo.westerngeco.slb.com


I am running ospfd/zebra on the following router setup:
+--+ +--+ +--+--- If0
|R1|---|R2|---|R3|--- If1
+--+ +--+ +--+--- If2

R1: Fedora core 6 PC (2.6.20-1.2933.fc6)
R2/3: MontaVista Linux 4.0.1 (2.6.10_mvl401-pq2fads)

All routers are configured to redistribute static/connected routes. All relevant
interfaces belong to the backbone. There are no misconfigured interval timers.
When R2 and R3 peer, the static/connected OSPF routes received by R2 from R3 are
set inactive by zebra on R2 (because R3 is not yet considered active, e.g.
nexthop_active_ipv4() fails) and never added to the kernel routing table. R1
does (correctly) add them however.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
Quagga-bugs mailing list
Quagga-bugs@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-bugs