Hi Ondrej,
If you attach the no-export community in the pipe export filter, then it
is here before the export to the BGP protocol (MYPEER), therefore it
wouldn't be exported unless the protocol has 'interpret communities no'
set. If the BGP protocol has 'interpret communities no' set, it should
On Thu, May 20, 2010 at 04:41:04PM +0200, Simone Morandini wrote:
> Hi all,
>
> I need your help to understand what I'm missing...
> One of the rs clients sends a route with no-export community, so I have
> to strip it on ingress and re-attach it on egress. I thought I have two
> alternatives:
Hi Arnold,
actually I wouldn't do resp. interprete ist that way. If customer sets
no-export, then simply do not export that prefix.
yes, what I didn't mention is that I've been asked to strip the
no-export and then re-attach it...
If customer really wants to have no-export set to the o
Hi Simone,
On 20.05.2010 16:41 Simone Morandini wrote
> I need your help to understand what I'm missing... One of the rs
> clients sends a route with no-export community, so I have to strip it
> on ingress and re-attach it on egress.
actually I wouldn't do resp. interprete ist that way. If custo
Hi all,
I need your help to understand what I'm missing...
One of the rs clients sends a route with no-export community, so I have
to strip it on ingress and re-attach it on egress. I thought I have two
alternatives: using "interpret community no" in the bgp table of the
peer, or playing with
