rejected by protocol <prefix> unicast

[Ondrej Zajicek]

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. That just means pe1
reject it back - no need to send the route back to the peer.

> This means that they are visible using the "show route protocol
> <protocol>"  but not
> "show route all" (and therefore impossible to push them to the kernel
> routing table).

No, the reason why the route is shown in 'show route protocol' but not
regular 'show route' is that BGP is connected to table t_pe1, while
Kernel is connected to (default) table master4. The first command shows
by default routes in table attached to the specified protocol, while the
second one shows routes in default table. But you do not have connection
between these tables (using pipe protocol), so BGP routes stay in t_pe1
and are not in master4, so that is another reason why they are not
exported to the kernel.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."