Date: Wed, 16 Jun 2021 19:55:01 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 256657] [tcp] RACK unsuitable for jails on stable/13 Message-ID: <bug-256657-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256657 Bug ID: 256657 Summary: [tcp] RACK unsuitable for jails on stable/13 Product: Base System Version: 13.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: zarychtam@plan-b.pwste.edu.pl Created attachment 225871 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D225871&action= =3Dedit Traffic dump collected on lo0 intefrace Some RACK fixes and improvements MFCed lately to stable/13 have made RACK unusable in the jail environment. The last working build is from June 4th a= nd it was probably 92f49c769b4e. Problem description: The database client (mysql/mariadb) running in the jail is no more able to access the database over the network socket on the host (mysql/mariadb) nei= ther on the 127.0.0.1 address nor on the shred interface address (10.x.x.x). It = is classic jail, not VNET jail. Switching to net.inet.tcp.functions_default=3Dfreebsd solves the issue. The problem occu= rs irregardless of the used net.inet.tcp.cc.algorithm (tested with htcp and newreno). Conclusion: Testing RACK on FreeBSD is becoming really hard task. Switching to default net.inet.tcp.functions_default=3Dfreebsd solves a lot of issues and reduces= the PR submitting ratio. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256657-227>