Rayhaan JaufeerallyandClaude Opus 5.5 efb2d81a50 Reject blackhole requests with a reason of their own ...

A route with the BLACKHOLE community (RFC 7999) asks for the traffic to
its prefix to be dropped. Exchange route servers pass these on as host
routes with the exchange's blackhole address as next hop, and they were
rejected as "prefix too specific", which hid what they are.

Routes from EBGP neighbors with BLACKHOLE are now rejected as "blackhole
request", whatever their length. One short enough to pass would have
been taken as an ordinary route, sending the traffic to the blackhole
next hop: the request honoured without anyone having chosen to. Acting
on blackhole requests is not supported; the import policy page and the
standards list say so.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-04 01:03:16 +02:00

..

proto

Pass learned routes on to peers, with marks and control communities

2026-10-02 23:48:08 +02:00

src

Reject blackhole requests with a reason of their own

2026-10-04 01:03:16 +02:00

tests

Add a documentation website, built with Zola

2026-10-03 15:12:43 +02:00

build.rs

Rework the speaker: sans-I/O FSM, sharded table, RFC 7606, ADD-PATH

2026-10-02 12:35:54 +02:00

Cargo.toml

Remove policy scripts

2026-10-02 22:47:57 +02:00