Hi Maria, Thanks for the review. This version keeps the diagnostic change, covers the other community constructors, and adds focused unit tests. Community constructors can reject values that are only known during filter evaluation. Include the values that determine these range failures so the failing route-dependent input can be identified from the existing runtime log. Changes since v1: - drop the channel statistics, CLI output, and route-trace changes; - report both pair components and the relevant extended-community key and value; - audit Large Community construction and test its full 32-bit field range; - add exact-message tests for the pair and extended-community failures, including both IP and quad inputs to the IPv4-key form; - align the commit subjects and bodies with recent upstream style. The series does not change log rate limits or add another error-log source. Base: thread-next 06ca9bf5c588df6c0587eb64bd375eb0ade526ab Validation: - autoreconf, configure, full build, and make check; - BIRD user and programmer HTML documentation; - clean-base application of the packaged v2 series. A BIRD 2 follow-up can be prepared if this should also land on master. Alice39s (3): Filter: Include values in community constructor errors Filter: Test community constructor runtime errors Doc: Explain pair constructor range checks Thanks, Alice39s alice39s@xmsl.dev