[Xorp-hackers] ospf4 and ospf6 can not apply export policy at the same time

Li Zhao lizhaous2000 at yahoo.com
Thu Dec 17 10:03:35 PST 2009


Now I can understand that part. Basically, the policy generates the code whenever
new pilicy is exported. In the function SourceMatchCodeGenerator::do_term,
action "<=" means "check that the route's tags are subset of this protocol tags".
I am even more closer to the root cause now. Stay tuned.

--- On Thu, 12/17/09, Bruce Simpson <bms at incunabulum.net> wrote:

> From: Bruce Simpson <bms at incunabulum.net>
> Subject: Re: [Xorp-hackers] ospf4 and ospf6 can not apply export policy at the same time
> To: "Li Zhao" <lizhaous2000 at yahoo.com>
> Cc: xorp-hackers at xorp.org
> Date: Thursday, December 17, 2009, 11:56 AM
> Li Zhao wrote:
> > Now can anybody tell me why tags are compared when
> policy terms are processed? Because ospf4 tag is greater
> than ospf6 policy tag. That is why
> > ospf4 tag is left out?
> >   
> 
> I'm not a great expert on the policy code; Andrea Bittau is
> the original author. He is sometimes around, I would try
> contacting him about the issue you've found.
> 
> Thanks for really drilling down into this issue. I may be
> able to pick up on it in the new year.
> 
> regards,
> BMS
> 


      



More information about the Xorp-hackers mailing list