How does roa_check(roa_table,net,bgp_path.last) work? Having such a ROA as example: origin AS: 64513 prefix: 78.150.40.0/20 max mask: 24 and a BGP announcement: origin AS: 64514 prefix: 78.150.45.0/22 so it's as invalid, but how does this check work? roa_table: validated roa record (validated cache) net: should be the current prefix so 78.150.45.0/22 what is bgp_path.last and how does roa_check function do the check? Thanks, Fabiano
On Sat 10 Oct 2020 22:05:45 GMT, Fabiano D'Agostino wrote:
How does roa_check(roa_table,net,bgp_path.last) work? Having such a ROA as example: origin AS: 64513 prefix: 78.150.40.0/20 max mask: 24
and a BGP announcement: origin AS: 64514 prefix: 78.150.45.0/22
so it's as invalid, but how does this check work? roa_table: validated roa record (validated cache) net: should be the current prefix so 78.150.45.0/22 what is bgp_path.last and how does roa_check function do the check?
Thanks,
Fabiano
I don’t know how you endded up to this data, but the /20 should be 78.150.40.0/20 and the /22 78.150.45.0/22. Also 64513 is a private ASN, so announcing public space from a private ASN will be invalid, whatever you try to do. -- Alarig
I wrongly pasted your errors, but 78.150.32.0/20 and 78.150.44.0/22 are the correct ones. -- Alarig
Hi Alarig, I just invented some data to do the example and I wanted to understand given that example to what bgp_path.last refers to. Thanks, Il giorno sab 10 ott 2020 alle ore 23:29 Alarig Le Lay <alarig@swordarmor.fr> ha scritto:
I wrongly pasted your errors, but 78.150.32.0/20 and 78.150.44.0/22 are the correct ones.
-- Alarig
participants (2)
-
Alarig Le Lay -
Fabiano D'Agostino