Date: Thu, 5 Dec 2019 21:17:42 +0100 From: Michael Tuexen <tuexen@freebsd.org> To: Jeremy Harris <jgh@wizmail.org> Cc: freebsd-transport@freebsd.org Subject: Re: TCP Fast Open Message-ID: <46A739DC-CCF5-4EA1-802A-0D8E559AC187@freebsd.org> In-Reply-To: <f07bb11e-4f69-b714-ce8d-881e68a20c6b@wizmail.org> References: <5276cc23-d37f-e55e-11c5-030314e9e32c@wizmail.org> <1206B1BE-3B7E-45D0-8C2B-6012A5CB6298@freebsd.org> <2752006b-cd6b-7b8b-d23b-ae2c794dc104@wizmail.org> <f59092f1-9f93-d5c3-e7a2-06ba88bd7385@wizmail.org> <F24D850E-C6B6-4600-9B28-2439D70447A0@freebsd.org> <f07bb11e-4f69-b714-ce8d-881e68a20c6b@wizmail.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 5. Dec 2019, at 20:58, Jeremy Harris <jgh@wizmail.org> wrote: >=20 > On 05/12/2019 19:43, Michael Tuexen wrote: >> Are you asking how to figure out whether TFO was used or not? >> In that case you can use=20 >> getsockopt(fd, IPPROTO_TCP, TCP_FASTOPEN, &on, &len); >> If on =3D=3D 0, TFO was not used, on !=3D 0, TFO was used. >=20 > I'd found that, but it's so far unclear what choices it > makes among > - didn't try TFO This means it is disabled in the cookie cache or you didn't enable the = socket option. I would expect on =3D 0. > - tried TFO but the server didn't take it up I would expect on =3D 0. > - server accepted the TFO cookie, but not the data that was on the SYN I don't know. I can test it and report... > - server acked the data I would expect on =3D 1. Best regards Michael > --=20 > Cheers, > Jeremy > _______________________________________________ > freebsd-transport@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-transport > To unsubscribe, send any mail to = "freebsd-transport-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46A739DC-CCF5-4EA1-802A-0D8E559AC187>