From nobody Wed Jul 27 03:37:16 2022 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4LszxK5xk8z4WyH7 for ; Wed, 27 Jul 2022 03:37:25 +0000 (UTC) (envelope-from starbops@hey.com) Received: from 01b.relay.hey.com (01b.relay.hey.com [204.62.114.225]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4LszxJ6J5vz3xnx for ; Wed, 27 Jul 2022 03:37:24 +0000 (UTC) (envelope-from starbops@hey.com) Received: from hey.com (bigip-vip.rw-ash-int.37signals.com [10.20.0.24]) by 01.relay.hey.com (Postfix) with ESMTPS id 37D15C1B53; Wed, 27 Jul 2022 03:37:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hey.com; s=heymail; t=1658893037; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=VmHHPh3OBZuM1hS5UVEGas47aQAi5cS4983u7cJkTRE=; b=uKID2Jr+nrY6LUi6CGM8bCn8TFXbm18W0b1ZYVWFqg0KJCQ8MbJf9zzErzvaH2SUwIznIr +tz4YRvk4JGemYlAkh6/9VDfLCYF1EM+8f/pc6weXHRiWJTS0mTW2yds6n0gBqH7w+EXLU lmN+svscHfGkBX0a0+m5TRSWgNPqBgs8SfdL9jixO7Z22rAKVgLxG6NKssSHeCU48By17l pjBsm30M49VIPIKgylywa/ppvmBmUx5q/GOElXSxT/L+34Ht5KdzHiVOF5I2YzkqZzx3gm KKM+E7lAxflU6D4kRi+LOXbDyh4Sgo7UbZrr6b6IyVp8TmQEsVWWZFiXHN2TYA== Date: Wed, 27 Jul 2022 11:37:16 +0800 From: Chih-Hsin Chang To: freebsd-net@freebsd.org Message-ID: Subject: Question on Current Status of TCPUTO Socket Option List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_62e0b2ecc5d82_6126fc198f4"; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4LszxJ6J5vz3xnx X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=hey.com header.s=heymail header.b=uKID2Jr+; dmarc=pass (policy=quarantine) header.from=hey.com; spf=pass (mx1.freebsd.org: domain of starbops@hey.com designates 204.62.114.225 as permitted sender) smtp.mailfrom=starbops@hey.com X-Spamd-Result: default: False [-5.50 / 15.00]; DWL_DNSWL_MED(-2.00)[hey.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[hey.com,quarantine]; R_DKIM_ALLOW(-0.20)[hey.com:s=heymail]; R_SPF_ALLOW(-0.20)[+ip4:204.62.114.0/23]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[freebsd-net@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:25657, ipnet:204.62.114.0/24, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DKIM_TRACE(0.00)[hey.com:+]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N ----==_mimepart_62e0b2ecc5d82_6126fc198f4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hello, I'm working on OpenStack porting stuff recently. I encountered an issue that caused `nova-scheduler` unable to start normally. The `nova- scheduler` needs to build up connections to RabbitMQ with the aid of the RabbitMQ driver in the `oslo.messaging` library. The point is that the driver needs to configure a socket option called `TCP_USER_TIMEOUT` (defined in RFC5482) along the process but the socket option seems not to exist on the FreeBSD platform AFAIK. After searching on the web, I found there're two wiki pages and some patches working on FreeBSD `TCP_USER_TIMEOUT` implementation. But none of them were accepted or merged in the source tree. I would like to know about the current situation of the implementation of this socket option. Thank you. - https://github.com/openstack/oslo.messaging/blob/12.14.0/oslo_messaging/_drivers/impl_rabbit.py#L1025 - https://wiki.freebsd.org/FangWang/TCPUTO - https://wiki.freebsd.org/CatalinNicutar/TCPUTO Sincerely, Chih-Hsin Chang ----==_mimepart_62e0b2ecc5d82_6126fc198f4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I'm working on OpenStack porting stuff recently. I e= ncountered an issue that caused `nova-scheduler` unable to start normally= . The `nova-scheduler` needs to build up connections to RabbitMQ with the= aid of the RabbitMQ driver in the `oslo.messaging` library. The point is= that the driver needs to configure a socket option called `TCP_USER_TIME= OUT` (defined in RFC5482) along the process but the socket option seems n= ot to exist on the FreeBSD platform AFAIK.

After searching on the = web, I found there're two wiki pages and some patches working on FreeBSD = `TCP_USER_TIMEOUT` implementation. But none of them were accepted or merg= ed in the source tree. I would like to know about the current situation o= f the implementation of this socket option.

Thank you.

- ht= tps://github.com/openstack/oslo.messaging/blob/12.14.0/oslo_messaging/_dr= ivers/impl_rabbit.py#L1025
- https://wiki.freebsd.org/FangWang/TCPUTO<= br>- https://wiki.freebsd.org/CatalinNicutar/TCPUTO

Sincerely,
= Chih-Hsin Chang
----==_mimepart_62e0b2ecc5d82_6126fc198f4--