search

haylinmoore / bgp.exposed

1 stars 0 forks source link

Add more options for announced routes #2

Open forkwhilefork opened 2 years ago

forkwhilefork commented 2 years ago

Currently, all server-advertised routes must be configured manually, with the exception of the full table option. It would be good to allow a few other canned options for route sets. I envision a radio selection between the following: -full table -peer bilat/PNI -IX route server -custom only

where the custom routes are always announced, but optionally you can layer one of the above presets on it.

haylinmoore commented 2 years ago

How would the "peer bilat/PNI" and "IX route server" routeset work? Like what would the contents be?

Also an option like "transit leak" would be nice where it just has one route from each transit provider, to check they are all being rejected, without having to send a full table.

forkwhilefork commented 2 years ago

peer routes would be a smaller subset of routes that's contained entirely in an AS-SET. you could take a particular real-life peer's routes as an example, or just make some up and make an AS-SET for it (probably the better way to go). IX route server would have routes with the same first ASN, but different next-hop IPs.

for transit leak, see #3 for my thoughts on how best to do that.

forkwhilefork commented 2 years ago

I marked this as “frontend”, but maybe this needs backend work too. I don’t think it’s a good idea to send every single route from the frontend to the backend.