dnarenderreddy at gmail
May 5, 2012, 6:21 AM
Post #3 of 3
Thanks for the Reply AI,
Re: Reg: Inter Area routes into non-back bone areas in OSPFv3
[In reply to]
I dont thing quagga has implemented RFC 3509.
I have fixed quagga ospf6d from sending the INTER Area routes from non back
bone areas into other non -backbone areas.
ospf6_abr.c (quagga version : 0.99.20)
> if ((route->path.area_id != BACKBONE_AREA_ID) &&
> if (is_debug)
> zlog_debug ("Not a BB route, cannot be originated to
> if (summary)
> ospf6_route_remove (summary, summary_table);
> if (old)
> ospf6_lsa_purge (old);
Can anyone let me know if this is fine.
How can I make quagga ignore the received inter area routes from non-back
On Sat, May 5, 2012 at 2:02 AM, Al <aas02929 [at] gmail> wrote:
> I don't have knowledge of the Quagga OSPF implementation but it sounds
> this could be related to RFC3509 (Alternative Implementations of OSPF
> Area Border Routers) even thou it's Informational (not standard).
> On Fri, May 4, 2012 at 6:17 AM, narender <dnarenderreddy [at] gmail> wrote:
> > Phil <phillaverdiere <at> yahoo.com> writes:
> >> Hi Narender,
> >> The virtual link is used to connect areas to the backbone, to prevent a
> > partitioned backbone. Every ospf are must be connected to the
> backbone. Say
> > area 2 is connected only to area 1. area 2 would need to create a
> virtual link
> > through area 1 to the backbone.
> >> Hope this helps,
> >> Phil
> > Thanks Phil.
> > My Expectation is also same.
> > But When I connect quagga OSPFv3 routers
> > -------[R1]------- [R2]--------- [R3]----------[R4]
> > Area 0 Area 0 Area 23 Area 34
> > I should be seeing Area 0 routes in R3 but not R3 should no be
> forwarding the
> > routes related to R1 into R4.
> > Only when there is a virtual link configured between R3 and R2 through
> > 23', we should be seeing R1 Routes in R4.
> > But What I ACTUALLY see is without even a virtual link, the routes of R1
> > seen in R4.
> > Isn't it wrong.
> > Where might the issue be.
> > Regards
> > Narender
> > _______________________________________________
> > Quagga-dev mailing list
> > Quagga-dev [at] lists
> > http://lists.quagga.net/mailman/listinfo/quagga-dev