Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 19 Mar 2023 14:42:52 +0100
From:      tuexen@freebsd.org
To:        Marek Zarychta <zarychtam@plan-b.pwste.edu.pl>
Cc:        "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject:   Re: assigning different TCP stacks to the jails
Message-ID:  <7BBAF016-3D98-40F2-9215-30E572B5857E@freebsd.org>
In-Reply-To: <18985515-e3bf-1575-4abb-30e511a45ae7@plan-b.pwste.edu.pl>
References:  <18985515-e3bf-1575-4abb-30e511a45ae7@plan-b.pwste.edu.pl>

next in thread | previous in thread | raw e-mail | index | archive | help
> On 19. Mar 2023, at 14:12, Marek Zarychta =
<zarychtam@plan-b.pwste.edu.pl> wrote:
>=20
> Dear subscribers of the list,
>=20
> TCP algo modules can be loaded/unloaded/changed on the fly. In FreeBSD =
14-CURRENT one can even change it on an active socket with tcpsso(8) =
utility, but there is no way to run jail with different TCP stack. =
Neither normal nor VNET jail support switching sysctl =
net.inet.tcp.functions_default.
>=20
> Is there any way to set TCP algo inherited through fork+exec in a =
similar way setfib(1) assigns fib or perhaps assign TCP algo per VNET =
instance?
Hi Marek,

so you are asking for the sysctl variable net.inet.tcp.functions_default =
to be vnet specific?

Best regards
Michael
>=20
> I am asking, since the almost perfect tcp_rack(4) applied on the host =
is missing TCP-MD5 singing feature which is required in one of the =
jails.
>=20
> Cheers
> --=20
> Marek Zarychta




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7BBAF016-3D98-40F2-9215-30E572B5857E>