Hello, I'm attempting to use BIRD to redistribute routes from a couple of interesting BGP feed services (Cymru bogons and UTRS) to a bunch of our edge routers, but I'm hitting an issue where BIRD isn't exporting the routes to our edge, every prefix is getting a "rejected by protocol" message in the log. bird6: edge1 < rejected by protocol 2407:dc20::/27 via [removed] on eth0 Here's a copy of my config with sensitive bits removed: https://gist.github.com/2bithacker/6561aa4484507c8f2d9d I think the problem might be related to talking to some peers from one AS and others from an internal AS, but I've tried changing them all to the same AS and it didn't help. Any pointers would be appreciated. I just wish "rejected by protocol" would provide a bit more detail on why it was rejected. -- Chip Marshall <chip@2bithacker.net> http://2bithacker.net/
On Tue, Jul 21, 2015 at 01:19:56PM -0400, Chip Marshall wrote:
Hello,
I'm attempting to use BIRD to redistribute routes from a couple of interesting BGP feed services (Cymru bogons and UTRS) to a bunch of our edge routers, but I'm hitting an issue where BIRD isn't exporting the routes to our edge, every prefix is getting a "rejected by protocol" message in the log.
bird6: edge1 < rejected by protocol 2407:dc20::/27 via [removed] on eth0
Any pointers would be appreciated. I just wish "rejected by protocol" would provide a bit more detail on why it was rejected.
Hello '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. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@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."
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/
participants (2)
-
Chip Marshall -
Ondrej Zajicek