[Xorp-users] Fwd: from and to blocks of policy terms

[Andreas Voellmy]

Yes, the import policy "from {neighbor: X} then {accept}" makes sense.
I am actually glad Xorp does not accept "to {neighbor: X} then
{accept}" as an import policy - I don't know what this policy would
mean.

--Andreas

On Mon, Mar 10, 2008 at 3:47 PM, Pavlin Radoslavov
<pavlin at icsi.berkeley.edu> wrote:
>
> > >  > > For example, "from {} to {neighbor: 192.168.1.2} then {accept}"
>  > >  > > can't be used as an export policy, but can be used as an import
>  > >  > > policy. As an import policy, when the routes reach the outbound
>  > >  > > evaluation, only the routes to neighbor 192.168.1.2 will be
>  > >  > > accepted (i.e., transmitted).
>  > >  >
>  > >  >
>  > >  > If I understand you correctly, you are saying that if "from {} to {neighbor:
>  > >  > 192.168.1.2} then {accept}" were an IMPORT policy, then it would be
>  > >  > equivalent to the following EXPORT policy "from {protocol: bgp} to
>  > >  > {neighbor: 192.168.1.2} then {accept}"?
>  > >
>  > >  I believe the answer is yes.
>  > >  However, I should also say that it has been a while since I looked
>  > >  into the policy framework details so I could be wrong.
>  >
>  > I tried the policy "from {} to {neighbor: X} then {accept}" as an
>  > import policy and it turns out that it is illegal, that is Xorp (1.4)
>  > rejects it and quits.
>
>  I am slowly starting to remember things...
>  Please try "from {neighbor: X} then {accept}" as an import policy.
>  The "to {}" block should apply to the outgoing branch of the control
>  path (inside BGP), and this information is not available when the
>  import policy is applied.
>
>  Pavlin
>