Got it, thanks for your help guys.
On Wed, Dec 11, 2019 at 1:54 PM Ondrej Zajicek
wrote:
> On Wed, Dec 11, 2019 at 09:06:15AM +0100, Eric GITAU wrote:
> > On Wed, Dec 11, 2019 at 3:19 AM Ondrej Zajicek
> > > Hi
> > >
> > > This 'rejected by protocol' is completely harmless. That just means pe1
On Wed, Dec 11, 2019 at 09:06:15AM +0100, Eric GITAU wrote:
> On Wed, Dec 11, 2019 at 3:19 AM Ondrej Zajicek
> > Hi
> >
> > This 'rejected by protocol' is completely harmless. That just means pe1
> > reject it back - no need to send the route back to the peer.
>
>
> Thanks for the explanation, a
On Tue, Dec 10, 2019 at 10:09:06PM +0100, wax xitau wrote:
> Hi,
>
> Prefixes sent over a eBGP session are getting rejected "by protocol" as can
> be seen in the logs below.
> The prefixes are "added" and then get "rejected" by protocol.
Hi
This 'rejected by protocol' is completely harmless. Th
Because in kernel protocol you shall write export filter. Also overlooked this
at the first sight.
To accept routes from bgp to table, you write import filter, to send routes
from table to kernel, you write export filter. The import/export semantics is
table-centric.
Maria
On December 10, 201
