21 Jul
2015
21 Jul
'15
6:26 p.m.
On 2015-07-21, Ondrej Zajicek <santiago@crfreenet.org> sent:
On Tue, Jul 21, 2015 at 01:19:56PM -0400, Chip Marshall wrote:
bird6: edge1 < rejected by protocol 2407:dc20::/27 via [removed] on eth0
'rejected by protocol' covers plenty of cases - not forwarding route back, not forwarding between IBGP sessions, avoiding RR loops and default community handling. Perhaps these routes have NO_EXPORT or NO_ADVERTISE community set? In that case see 'interpret communities' option.
Ugh, yeah, that was it. I knew it was going to be something simple that I was overlooking. Thanks for the pointer on 'interpret communities', that's exactly what I needed. -- Chip Marshall <chip@2bithacker.net> http://2bithacker.net/