Thanks Pavlin! A couple more questions below ...<br><br><div class="gmail_quote">On Feb 11, 2008 2:19 PM, Pavlin Radoslavov <<a href="mailto:pavlin@icsi.berkeley.edu">pavlin@icsi.berkeley.edu</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
A small piece of information that might be helpful for you: for<br>export policy the "from" block must have the "protocol" set. I.e.,<br>you can't export routes if the protocol is not specified.</blockquote>
<div><br>Is the "protocol" attribute required in the "from" clause in every export policy, or only in those which are redistributing routes from another protocol? <br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>For example, "from {} to {neighbor: <a href="http://192.168.1.2" target="_blank">192.168.1.2</a>} then {accept}"<br>can't be used as an export policy, but can be used as an import<br>policy. As an import policy, when the routes reach the outbound<br>
evaluation, only the routes to neighbor <a href="http://192.168.1.2" target="_blank">192.168.1.2</a> will be<br>accepted (i.e., transmitted).</blockquote><div><br>I am still a bit confused. Would it be a valid export policy if it had a protocol attribute in the from clause, i.e. if it was like this: "from {protocol: bgp} to {neighbor: <a href="http://192.168.1.2">192.168.1.2</a>} then {accept}"?<br>
<br>If I understand you correctly, you are saying that if "from {} to {neighbor: <a href="http://192.168.1.2/" target="_blank">192.168.1.2</a>} then {accept}" were an IMPORT policy, then it would be equivalent to the following EXPORT policy "from {protocol: bgp} to {neighbor: <a href="http://192.168.1.2">192.168.1.2</a>} then {accept}"?<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Similarly, "from {neighbor: <a href="http://192.168.1.2" target="_blank">192.168.1.2</a>} to {} then {accept}" also<br>
cannot be used as an export policy. As an import policy it will<br>accept only the routes coming from neighbor <a href="http://192.168.1.2" target="_blank">192.168.1.2</a>.<br></blockquote><div><br>Again, would it be a valid export policy if it were modified to "from {protocol: bgp; neighbor: <a href="http://192.168.1.2/" target="_blank">192.168.1.2</a>} to {} then {accept}"?<br>
<br>-Andreas</div></div><br>