any dangers of filtering every /24 on full internet table to preserve FIB space ?
davidbass570 at gmail.com
Mon Oct 10 21:24:59 UTC 2022
I frequently do this (accept peer’s, and their customers prefixes), and it
works out well. Then you can choose where you want the rest of it to go.
With multiple peers in your country this works out quite well.
On Mon, Oct 10, 2022 at 5:02 PM richey goldberg <richey.goldberg at gmail.com>
> The OP can always take the provider's address space plus their
> customer's routes and use a default route to fill in the blanks. I
> did this at a provider years ago where the global routing table
> outgrew the speed they could spend the money on upgrades and it worked
> out well. I think it was two upstreams and a connection into a TIE
> with good peering.
> On Mon, Oct 10, 2022 at 4:11 PM Geoff Huston <gih at apnic.net> wrote:
> > > On 11 Oct 2022, at 4:23 am, Tobias Fiebig <
> tobias at reads-this-mailinglist.com> wrote:
> > >
> > > Heho,
> > > Let alone $all the /24 assigned under the RIPE waiting list policy.
> > >
> > > In the Geoff Huston spirit, I quickly took a look how less specifics
> for /24s looks in my table:
> > >
> > […]
> > > So it seems like there is a healthy amount (~260k) prefixes which lack
> a less specific.
> > I also looked using a slightly different approach - namely looking for
> /24s where there was no spanning aggregate that matched the /24’s AS Path.
> In my local table there are 224,580 of them.
> > Geoff
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NANOG