-----Mensaje original-----
De: "Jonathan Stewart" <jonathan.stewart@gmail.com>
A: Angel <angel@bitnap.net>
Cc: bird <bird-users@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@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