From nobody Thu Oct 26 01:36:04 2023 X-Original-To: freebsd-current@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 4SG7g43Pdfz4yK81 for ; Thu, 26 Oct 2023 01:36:16 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SG7g41XSkz4TTM for ; Thu, 26 Oct 2023 01:36:16 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-x432.google.com with SMTP id d2e1a72fcca58-6ba172c5f3dso341562b3a.0 for ; Wed, 25 Oct 2023 18:36:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698284175; x=1698888975; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=ZdeXSpSmOrjtDuhxN95I9FsQAqVBsZECOPuFH5x78AQ=; b=E6rVpb/knlvhdx2DizNa3m68SYzBS5WUvSQiQe3fNExMgvPx8YW6gd70fN4Z6THkNF aGA4vGX1WruZOiI1Ww+DAabBRXi47HqaBgL8W2DqzMjSOXcwTmKlC5hHhYvNU8ybIEmj Y2ReutObvlAKBmeV2vax6H5OBq8tWUG0I/BWjueVTwGNbGjbfyxFXiBKtoTX3SvffHMD uZxXyqeK+/YRYbiWB5KFuIH7SGyGqh3IZqiYxXgmNUttTjJiajFqCNMaWUShVJMQYDgE 5cYtin3bUvCGxZ157eF6jVylUYwwji7CPP31uawi16VZLCLZynrgtjj2+32VJW1+pAAO VNzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698284175; x=1698888975; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ZdeXSpSmOrjtDuhxN95I9FsQAqVBsZECOPuFH5x78AQ=; b=bZctH9Izo1T4LaP7w/Ohu2d6GGJD+3ZQZiuY0vFpgBsgxT83bd5JuE+8+lsSxB/zkX 9dRSsZ1uo1Di/b9nxCKGR9btngugT2lsth89cQgwVilVAEp5vWt3Mg0F2szKiJiK4XGa MggCNBJD/nahy5/m2mgD1XcAH7KffVlCF04r30B7nPbWuyMu5w+j2fjh2c4kcWDkVMNF MFsTsJBiapZ7u3tL9imqy0HsVlbprL7ngpNW20C3pxL07RXw607+LQONT7YDQZ6+nqcS Q40KCMiLcQVYT5T8btCdW/0hG+tNULE52v1xziwpO15hqXoltAXY8x3BVnVCSCxzoIyg u+cQ== X-Gm-Message-State: AOJu0YzwjdTr6ZzuHObrQj3gFUGoMlMAeJeqCl/bNN9ofBW+EbbPGd9I eoZV03EEEBItcwQHXFMe2rptk9CI9Vb9W7hPyA== X-Google-Smtp-Source: AGHT+IGqmPamZDZPTUpr+e7tkfAYJBNwXuS0QpUd2RMbwzY7TrPzatEon9mcE38oAXCP2fGgqZgGM3YUKqw+jlPjB6E= X-Received: by 2002:a05:6a21:3b49:b0:16b:7602:1837 with SMTP id zy9-20020a056a213b4900b0016b76021837mr7525141pzb.29.1698284175002; Wed, 25 Oct 2023 18:36:15 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Rick Macklem Date: Wed, 25 Oct 2023 18:36:04 -0700 Message-ID: Subject: Re: RFC: NFS over TLS stats To: Freddie Cash Cc: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Queue-Id: 4SG7g41XSkz4TTM Thanks for all the suggestions. I've modified the patch for all of them. (tx/rx instead of snd/rcv, _tls at the end of the names so the order is more readable.) There aren't really errors visible at the RPC/TLS boundary, but I have added counts of successful/failed handshakes and a count of alert messages (basically "Peer Resets" from what I've seen). Thanks, rick ps: Just replying to one of the messages and, yes, I did top post.. On Wed, Oct 25, 2023 at 8:47=E2=80=AFAM Freddie Cash wr= ote: > > On Tue, Oct 24, 2023 at 10:56=E2=80=AFPM Rick Macklem wrote: >> >> Garrett Wollman asked me via email how a server >> admin could tell what usage NFS over TLS was >> happening. >> >> I admitted that there was nothing. I have come up >> with a patch that generates the following: >> kern.rpctls.snd_tls_msgbytes: 21508 >> kern.rpctls.snd_msgbytes: 20828 >> kern.rpctls.snd_tls_msgcnt: 57 >> kern.rpctls.snd_msgcnt: 58 >> kern.rpctls.rcv_tls_msgbytes: 12336 >> kern.rpctls.rcv_msgbytes: 12072 >> kern.rpctls.rcv_tls_msgcnt: 57 >> kern.rpctls.rcv_msgcnt: 58 > > > Have no technical comments, but a style suggestion: put the tls at the e= nd to make the output look nicer. :) > >> kern.rpctls.snd_msgbytes: 21508 >> kern.rpctls.snd_msgbytes_tls: 20828 >> kern.rpctls.snd_msgcnt: 58 >> kern.rpctls.snd_msgcnt_tls: 57 >> kern.rpctls.rcv_msgbytes: 12072 >> kern.rpctls.rcv_tmsgbytes_tls: 12336 >> kern.rpctls.rcv_msgcnt: 58 >> >> kern.rpctls.rcv_msgcnt_tls: 57 > > > -- > Freddie Cash > fjwcash@gmail.com