Re: RFC: Separate import/export tables

2021-06-24 Thread Maria Matejka
Hello! I'm quite confused by what you're trying to achieve. How would you choose the routes that are likely to be exported? Hello I understood it that as small AS, you have small set of 'your' (or customers') prefixes (say 10) in prefix set which you want to export to all your peers and upstr

Re: RFC: Separate import/export tables

2021-06-24 Thread Ondrej Zajicek
On Sat, Jun 19, 2021 at 09:22:35AM +0200, Maria Matejka wrote: > Hello! > > I'm quite confused by what you're trying to achieve. How would you choose > the routes that are likely to be exported? Hello I understood it that as small AS, you have small set of 'your' (or customers') prefixes (say 10

Re: RFC: Separate import/export tables

2021-06-19 Thread Maria Matejka
Hello! I'm quite confused by what you're trying to achieve. How would you choose the routes that are likely to be exported? If there is something that you repetitively count in export filters, you may move this check into the import filters (these are run only once) and store the result using

RFC: Separate import/export tables

2021-06-18 Thread Asbjørn Sloth Tønnesen
Hi, We have an internet router setup where we have a few customer connections, and hundreds of peering sessions. A lot of CPU time is wasted running the export filters over the entire internet routing table per peer, in order to find the relatively few prefixes to actually export. I know we cou