Date: Sat, 9 May 2020 21:03:02 +0200 From: Michael Tuexen <tuexen@freebsd.org> To: Gordon Bergling <gbergling@googlemail.com> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, david@catwhisker.org Subject: Re: Error loading tcp_bbr kernel module Message-ID: <3B396584-1018-46ED-B7F9-35215B4AF17C@freebsd.org> In-Reply-To: <20200509160714.GA38490@lion.0xfce3.net> References: <20200509121851.GA59530@lion.0xfce3.net> <24D28CC3-AA45-412F-AF3D-9697A36FCB8D@freebsd.org> <F9EDABC9-504C-4A27-AFD0-F0A1BAB656A2@googlemail.com> <EE9FDF78-3E8A-4655-AFF3-91605FC1FEF2@freebsd.org> <20200509160714.GA38490@lion.0xfce3.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 9. May 2020, at 18:07, Gordon Bergling <gbergling@googlemail.com> = wrote: >=20 > Hi Michael, >=20 > On Sat, May 09, 2020 at 05:42:55PM +0200, Michael Tuexen wrote: >>> On 9. May 2020, at 16:25, Gordon Bergling <gbergling@googlemail.com> = wrote: >>> I tried tcp_rack and tcp_bbr, since both are separate TCP stacks. I = just posted the wrong error message. Both TCP stacks weren=E2=80=99t = loadable as a kernel module with just the former mentioned build option. >>>=20 >>> I currently have build running with both kernel options you = mentioned. >>>=20 >>> If the build is successful and I can change the default TCP stack to = RACK and BBR I let you know. >> That would be great. I have them running on my machines, but I might = have missed something. >>>=20 >>> Further I didn=E2=80=99t find any documentation within tcp(4) = regarding RACK and BBR. Since I am about to enhance the manpages, I=E2=80=99= ll extent tcp(4) about information about RACK and BBR, but this is a = different topic. >>>=20 >> Yes it is. And I would suggest to use separate man pages, a single = one for each stack. >> The the generic man page might refer to them... >=20 > My first thoughts on this topic were about to extent tcp(4) and create = links to > tcp_rack(4) and tcp_bbr(4), but separate manpages maybe the way to go. = I just > have to investigate the respective details. I was once very deep into = TCP/IP,=20 > while building perimeter firewalls with FreeBSD, but this was 20 years = ago. >=20 > I add you as a reviever for the differential once I have a rough cut=20= > for the manpages ready. Hi Gordon, please do so. Don't forget to add rrs@, since he wrote both stacks. Best regards Michael >=20 > Best regards, >=20 > Gordon >=20 >>>> Am 09.05.2020 um 14:37 schrieb Michael Tuexen <tuexen@freebsd.org>: >>>>> On 9. May 2020, at 14:18, Gordon Bergling = <gbergling@googlemail.com> wrote: >>>>>=20 >>>>> Greetings, >>>>>=20 >>>>> I build -CURRENT with WITH_EXTRA_TCP_STACKS=3D1, but I got the = following error >>>>> when I try to load for example tcp_bbr.ko. >>>>> z >>>>> kldload: an error occurred while loading module tcp_rack.ko. = Please check dmesg(8) for more details. >>>> This indicates that you want to load the RACK stack. >>>>=20 >>>> Please note that you need for BBR and RACK: >>>> options TCPHPTS >>>> in the kernel config and in addition to that for RACK >>>> options RATELIMIT >>>>=20 >>>>> dmesg shows: >>>>>=20 >>>>> KLD tcp_bbr.ko: depends on tcphpts - not available or version = mismatch >>>>> linker_load_file: /boot/kernel/tcp_bbr.ko - unsupported file type >>>>>=20 >>>>> Any hints on solving the problem? >>>>>=20 >>>>> The kernel config is GENERIC. >>>>>=20 >>>>> Best regards, >>>>>=20 >>>>> Gordon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B396584-1018-46ED-B7F9-35215B4AF17C>