reject debug messages

[Jonathan Stewart]

http://bird.network.cz/pipermail/bird-users/2010-May/006170.html

Hey Angel,

Look at this message above.

I understand the error to mean that BIRD tried to sent the route for
193.148.120.0/24 to protocol AS174Transit, but the logic for that protocol
refused to send that route because it was the same source that it came from.

This is normal and expected, which is why Ondrej said they might remove
this warning in the future. It sounds like an error, but it's normal
operation -- Don't send routes back to the same peer you learned them from.

Jonathan

On Mon, May 23, 2016 at 2:11 AM, Angel <angel at bitnap.net> wrote:

> Hello Jonathan,
>
> We have a fullrouting bgp with a carrier and we configure it with
> AS174transit bpg protocol. This routes are not from our AS, they come from
> carrier's bgp session.
>
> What we could not understand is why all added messages have their own
> rejected by protocol messages, what they mean? we disable all filters and
> it appears again.
>
> Regards,
>
> ------------------------------
> -----Mensaje original-----
> De: "Jonathan Stewart" <jonathan.stewart at gmail.com>
> A: Angel <angel at bitnap.net>
> Cc: bird <bird-users at network.cz>
> Fecha: 23-05-2016 08:41
> Asunto: Re: reject debug messages
>
> Are those routes part of your own AS? Is there anything special about the
> rejected routes?
>
> On Thu, May 19, 2016 at 2:05 AM, Angel < angel at bitnap.net> wrote:
>
>> Hello,
>>
>> We are configuring a new bird router, and after configure a carrier, we
>> can see following messages on debug every minute:
>>
>> ------------
>> >>> AS174transit > added [best] 193.148.120.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 193.148.120.0/24 via
>> 149.6.130.137 on ix0
>> >>> AS174transit > added [best] 193.148.126.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 193.148.126.0/24 via
>> 149.6.130.137 on ix0
>> >>> AS174transit > added [best] 193.148.125.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 193.148.125.0/24 via
>> 149.6.130.137 on ix0
>> >>> AS174transit > added [best] 193.148.121.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 193.148.121.0/24 via
>> 149.6.130.137 on ix0
>> >>> AS174transit > added [best] 81.17.142.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 81.17.142.0/24 via 149.6.130.137
>> on ix0
>> >>> AS174transit > added [best] 91.198.226.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 91.198.226.0/24 via
>> 149.6.130.137 on ix0
>> >>> AS174transit > added [best] 85.140.116.0/22 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 85.140.116.0/22 via
>> 149.6.130.137 on ix0
>> >>> AS174transit > added [best] 195.128.159.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 195.128.159.0/24 via
>> 149.6.130.137 on ix0
>> >>> AS174transit > added [best] 46.225.128.0/19 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 46.225.128.0/19 via
>> 149.6.130.137 on ix0
>> >>> AS174transit > added [best] 46.225.96.0/19 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 46.225.96.0/19 via 149.6.130.137
>> on ix0
>> >>> AS174transit > added [best] 46.224.7.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 46.224.7.0/24 via 149.6.130.137
>> on ix0
>> >>> AS174transit > added [best] 46.225.224.0/19 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 46.225.224.0/19 via
>> 149.6.130.137 on ix0
>> >>> AS174transit > added [best] 46.225.0.0/19 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 46.225.0.0/19 via 149.6.130.137
>> on ix0
>> >>> AS174transit > added [best] 46.224.96.0/19 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 46.224.96.0/19 via 149.6.130.137
>> on ix0
>> >>> AS174transit > added [best] 46.225.32.0/19 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 46.225.32.0/19 via 149.6.130.137
>> on ix0
>> >>> AS174transit > added [best] 46.224.128.0/19 via 149.6.130.137 on ix0
>> >>> AS174transit < rejected by protocol 46.224.128.0/19 via
>> 149.6.130.137 on ix0
>> >>> AS174transit > ignored 109.72.148.0/22 via 149.6.130.137 on ix0
>> >>> AS174transit > ignored 109.72.147.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit > ignored 109.72.146.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit > ignored 109.72.145.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit > ignored 109.72.144.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit > ignored 37.46.114.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit > ignored 109.248.240.0/22 via 149.6.130.137 on ix0
>> >>> AS174transit > ignored 109.248.242.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit > ignored 109.248.241.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit > ignored 109.248.240.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit > ignored 109.248.225.0/24 via 149.6.130.137 on ix0
>> >>> AS174transit > ignored 109.248.224.0/24 via 149.6.130.137 on ix0
>>
>> ------------
>>
>> We understand that added messages is because carrier sent us new routes,
>> ignored looks like that we know this route, so we do not need to add to our
>> table, but what about rejected messages? How could we fix it? What could be
>> our misconfiguration?
>>
>> Regards,
>>
>
>
>
> --
> Jonathan
>
>


-- 
     Jonathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20160523/c426e61c/attachment.html>