Re: Best Linux (or BSD) hosted BGP?

[Brandon Zhi <Brandon () huize asia>]

I use bird2 with Debian11 sometimes, I'm curious, what is the usual
hardware for using Linux as a router? In addition, the Linux ip rule seems
to have a problem with the matching of the ipv4 source address. . .
*Brandon Zhi*
HUIZE LTD
www.huize.asia  <https://huize.asia/>| www.ixp.su | Twitter

This e-mail and any attachments or any reproduction of this e-mail in
whatever manner are confidential and for the use of the addressee(s) only.
HUIZE LTD can’t take any liability and guarantee of the text of the email
message and virus.


On Thu, 11 May 2023 at 13:29, Blake Dunlap <ikiris () gmail com> wrote:

> I'm confused here, are you intentionally running larger MTU interfaces
> than the packet filter can handle with default config, and not wanting to
> change the tunable to fix the config for buffer size for the packet filter,
> or am I misreading?
>
> On Wed, May 10, 2023 at 11:51 PM Mark Tinka <mark@tinka.africa> wrote:
>
> > On 5/10/23 15:55, Tom Beecher wrote:
> >
> > >  That could just as easily happen today. Every OS release has all
> > > kinds of changes to defaults, and frequently don't get caught until
> > > they break something. Even if today's FreeBSD defaults worked for this
> > > scenario, the next release could change to a value that doesn't.
> >
> > We implement a lot of user-defined changes to FreeBSD defaults via
> > "/etc/sysctl.conf", as an example, whose unexpected change would not
> > necessarily break anything as they would reduce scaled performance. We
> > can live with that, because we can afford a reduction in performance
> > until the fault is found, not an outright outage.
> >
> > The problem with doing this with something like a routing protocol - and
> > in this specific case with FRR on FreeBSD for IS-IS - is that it would
> > not be a reduction in performance if an unexpected change were to find
> > its way into future revisions of FreeBSD... it would, in all likelihood,
> > be a complete outage. That is a steeper price to pay, for us anyway.
> >
> > It's just about weighing the risks for one's particular operating
> > environment, and for us, that risk is too high for a routing protocol.
> >
> > Mark.