From ml@ft-c.de Wed Oct 27 07:54:14 2021 X-Original-To: freebsd-stable@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 B5D6A18355F9 for ; Wed, 27 Oct 2021 07:54:25 +0000 (UTC) (envelope-from ml@ft-c.de) Received: from einhorn-mail-out.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail.in-berlin.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HfLYr18V3z4v3s for ; Wed, 27 Oct 2021 07:54:23 +0000 (UTC) (envelope-from ml@ft-c.de) X-Envelope-From: ml@ft-c.de X-Envelope-To: Received: from authenticated.user (localhost [127.0.0.1]) by einhorn.in-berlin.de with ESMTPSA id 19R7sFWE016436 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for ; Wed, 27 Oct 2021 09:54:15 +0200 Message-ID: Subject: pkg postgresql-client From: ml@ft-c.de Reply-To: ftimmer@ft-c.de To: "freebsd-stable@freebsd.org" Date: Wed, 27 Oct 2021 09:54:14 +0200 Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.2 FreeBSD GNOME Team List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4HfLYr18V3z4v3s X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of ml@ft-c.de has no SPF policy when checking 192.109.42.8) smtp.mailfrom=ml@ft-c.de X-Spamd-Result: default: False [-2.12 / 15.00]; HAS_REPLYTO(0.00)[ftimmer@ft-c.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[192.109.42.8:from]; REPLYTO_DN_EQ_FROM_DN(0.00)[]; NEURAL_HAM_SHORT(-0.92)[-0.920]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:29670, ipnet:192.109.42.0/24, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[192.109.42.8:from]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; REPLYTO_DOM_EQ_FROM_DOM(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[ft-c.de]; FROM_NO_DN(0.00)[]; TO_DN_EQ_ADDR_ALL(0.00)[]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Hello, I have install postgresql version 13  (and in a few weeks I switch to version 14) When I install R-studio, then pkg would change/downgrade the postgresql-client version from 13 to 12. pkg install Rstudio Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. The following 3 package(s) will be affected (of 0 checked): New packages to be INSTALLED: RStudio: 1.4.1717_2 postgresql12-client: 12.8 soci: 4.0.1_1 This error has existed for more than 5 years. Franz uname -a :> FreeBSD 13.0-RELEASE-p4 amd64 From nobody Wed Oct 27 08:20:52 2021 X-Original-To: freebsd-stable@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 E8CEF18194E0 for ; Wed, 27 Oct 2021 08:20:54 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HfM8Q6H64z3JyL; Wed, 27 Oct 2021 08:20:54 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from aniel.nours.eu (nours.eu [176.31.115.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: bapt) by smtp.freebsd.org (Postfix) with ESMTPSA id 9068229EAB; Wed, 27 Oct 2021 08:20:54 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by aniel.nours.eu (Postfix, from userid 1001) id 25CF3E578E; Wed, 27 Oct 2021 10:20:52 +0200 (CEST) Date: Wed, 27 Oct 2021 10:20:52 +0200 From: Baptiste Daroussin To: ftimmer@ft-c.de Cc: "freebsd-stable@freebsd.org" Subject: Re: pkg postgresql-client Message-ID: <20211027082052.vuieglgwlgporlpk@aniel.nours.eu> References: List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-ThisMailContainsUnwantedMimeParts: N On Wed, Oct 27, 2021 at 09:54:14AM +0200, ml@ft-c.de wrote: > Hello, > > I have install postgresql version 13  > (and in a few weeks I switch to version 14) > > When I install R-studio, then pkg would change/downgrade the > postgresql-client version from 13 to 12. > > pkg install Rstudio > Updating FreeBSD repository catalogue... > FreeBSD repository is up to date. > All repositories are up to date. > The following 3 package(s) will be affected (of 0 checked): > > New packages to be INSTALLED: > RStudio: 1.4.1717_2 > postgresql12-client: 12.8 > soci: 4.0.1_1 > > This error has existed for more than 5 years. > > Franz > > uname -a :> FreeBSD 13.0-RELEASE-p4 amd64 > > > Welcome to the postgresql hell (same applies to mysql family) on freebsd This is because on freebsd beside the fact that multiple version exists in the ports tree only the "default" can be used when using binary packages. I have posted a proposal on how to make any postgresql installable in parallel, shoudl be around 6 years ago, unfortunatly noone implemented it since :(, my proposal would have eliminated the concept of default and let the user pick the version it needs. https://lists.freebsd.org/pipermail/freebsd-ports/2015-July/099842.html Best regards, Bapt From nobody Wed Oct 27 13:28:47 2021 X-Original-To: freebsd-stable@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 5B0AF182FEF3 for ; Wed, 27 Oct 2021 13:36:29 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840::12]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "uucp.dinoex.sub.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HfV8V4GDWz4SWf for ; Wed, 27 Oct 2021 13:36:26 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Received: from uucp.dinoex.sub.de (uucp.dinoex.org [185.220.148.12]) by uucp.dinoex.org (8.17.1/8.17.1) with ESMTPS id 19RDa4Pm071983 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Wed, 27 Oct 2021 15:36:04 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) X-MDaemon-Deliver-To: X-Authentication-Warning: uucp.dinoex.sub.de: Host uucp.dinoex.org [185.220.148.12] claimed to be uucp.dinoex.sub.de Received: (from uucp@localhost) by uucp.dinoex.sub.de (8.17.1/8.17.1/Submit) with UUCP id 19RDa4Lb071982 for freebsd-stable@freebsd.org; Wed, 27 Oct 2021 15:36:04 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Received: from gate.intra.daemon.contact (gate-e [192.168.98.2]) by citylink.dinoex.sub.de (8.16.1/8.16.1) with ESMTP id 19RDVEwa087200 for ; Wed, 27 Oct 2021 15:31:14 +0200 (CEST) (envelope-from peter@gate.intra.daemon.contact) Received: from gate.intra.daemon.contact (gate-e [192.168.98.2]) by gate.intra.daemon.contact (8.16.1/8.16.1) with ESMTPS id 19RDSlPf086075 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Wed, 27 Oct 2021 15:28:47 +0200 (CEST) (envelope-from peter@gate.intra.daemon.contact) Received: (from peter@localhost) by gate.intra.daemon.contact (8.16.1/8.16.1/Submit) id 19RDSlO5086074 for freebsd-stable@freebsd.org; Wed, 27 Oct 2021 15:28:47 +0200 (CEST) (envelope-from peter) Date: Wed, 27 Oct 2021 15:28:47 +0200 From: Peter To: freebsd-stable@freebsd.org Subject: IPv6 checksum errors with divert Message-ID: List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Milter: Spamilter (Reciever: uucp.dinoex.sub.de; Sender-ip: 185.220.148.12; Sender-helo: uucp.dinoex.sub.de;) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (uucp.dinoex.org [185.220.148.12]); Wed, 27 Oct 2021 15:36:07 +0200 (CEST) X-Rspamd-Queue-Id: 4HfV8V4GDWz4SWf X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of pmc@citylink.dinoex.sub.org has no SPF policy when checking 2a0b:f840::12) smtp.mailfrom=pmc@citylink.dinoex.sub.org X-Spamd-Result: default: False [-2.10 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[4]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_NA(0.00)[sub.org]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:205376, ipnet:2a0b:f840::/32, country:DE]; RCVD_TLS_LAST(0.00)[] X-ThisMailContainsUnwantedMimeParts: N I'm getting these errors when e.g. querying the root nameservers: 05:58:50.916825 IP6 (flowlabel 0x08c7c, hlim 64, next-header UDP (17) payload length: 62) 2003:e7:17ff:192c:41d:92ff:fe01:301.42518 > 2600:1401:2::a.53: [bad udp cksum 0x24ca -> 0x48df!] These requests will never be answered. I see these checksum error when the packet goes into the divert socket, I see it when the packet comes back from divert, and I see it when the packet goes out onto the network. But, when I remove the divert socket from the path, then I still see the checksum error at the place where the divert would have happened, but when the packet goes out to the network, the checksums are okay. Obviousely this concerns only locally created packets - gatewayed IPv6 works okay. So somehow the information, that the packet is locally created and still needs checksum computation, gets lost when traversing the divert. Cheerio, PMc From nobody Wed Oct 27 16:57:48 2021 X-Original-To: freebsd-stable@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 9BA40181CD79 for ; Wed, 27 Oct 2021 16:57:55 +0000 (UTC) (envelope-from spork@bway.net) Received: from smtp2.bway.net (smtp2.bway.net [216.220.96.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HfZcz3xg4z4SF4; Wed, 27 Oct 2021 16:57:55 +0000 (UTC) (envelope-from spork@bway.net) Received: from gaseousweiner.sporklab.com (pool-74-102-83-202.nwrknj.fios.verizon.net [74.102.83.202]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: spork@bway.net) by smtp2.bway.net (Postfix) with ESMTPSA id 114002931D; Wed, 27 Oct 2021 12:57:49 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bway.net; s=mail; t=1635353869; bh=8S6jqB15ZwJz5I1sN5rijUEhGJDDRSjaBroTTuNejWo=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=bVmrWNTsBJT1O3BEQ1at70ftHfSMfrsgfd4WR7pObPuOZk0cjGuMMCsyKUeFyvCtS fJU/LXrOOiS7aDlQgM0dikYHsg6EHiNTFkRMVS4mul0zRc/dbpNAjhxHfAI9ZwdcMC 3GPo6Rrkx7Qk/wUfTPaRnm4nN+Hs1uxO/VjSukuw= Content-Type: text/plain; charset=us-ascii List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\)) Subject: Re: pkg postgresql-client In-Reply-To: <20211027082052.vuieglgwlgporlpk@aniel.nours.eu> Date: Wed, 27 Oct 2021 12:57:48 -0400 Cc: ftimmer@ft-c.de, "freebsd-stable@freebsd.org" X-Mao-Original-Outgoing-Id: 657046668.294693-69f001754a8d86fc6011668543ae59a7 Content-Transfer-Encoding: quoted-printable Message-Id: <8362A12C-F144-4572-9DF3-F06239A53900@bway.net> References: <20211027082052.vuieglgwlgporlpk@aniel.nours.eu> To: Baptiste Daroussin X-Mailer: Apple Mail (2.3445.104.21) X-Rspamd-Queue-Id: 4HfZcz3xg4z4SF4 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Reply-To: spork@bway.net From: Charles Sprickman via freebsd-stable X-Original-From: Charles Sprickman X-ThisMailContainsUnwantedMimeParts: N > On Oct 27, 2021, at 4:20 AM, Baptiste Daroussin = wrote: >=20 > On Wed, Oct 27, 2021 at 09:54:14AM +0200, ml@ft-c.de wrote: >> Hello,=20 >>=20 >> I have install postgresql version 13=20 >> (and in a few weeks I switch to version 14)=20 >>=20 >> When I install R-studio, then pkg would change/downgrade the >> postgresql-client version from 13 to 12.=20 >>=20 >> pkg install Rstudio >> Updating FreeBSD repository catalogue... >> FreeBSD repository is up to date. >> All repositories are up to date. >> The following 3 package(s) will be affected (of 0 checked): >>=20 >> New packages to be INSTALLED: >> RStudio: 1.4.1717_2 >> postgresql12-client: 12.8 >> soci: 4.0.1_1 >>=20 >> This error has existed for more than 5 years. >>=20 >> Franz >>=20 >> uname -a :> FreeBSD 13.0-RELEASE-p4 amd64 >>=20 >>=20 >>=20 >=20 > Welcome to the postgresql hell (same applies to mysql family) on = freebsd >=20 > This is because on freebsd beside the fact that multiple version = exists in the > ports tree only the "default" can be used when using binary packages. >=20 > I have posted a proposal on how to make any postgresql installable in = parallel, > shoudl be around 6 years ago, unfortunatly noone implemented it since = :(, my > proposal would have eliminated the concept of default and let the user = pick the > version it needs. +1 on that - pkg has gotten to the point where I very, very rarely use = ports and I love that Charles >=20 > = https://lists.freebsd.org/pipermail/freebsd-ports/2015-July/099842.html >=20 > Best regards, > Bapt >=20 From nobody Thu Oct 28 14:44:56 2021 X-Original-To: freebsd-stable@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 6F6EA1819999; Thu, 28 Oct 2021 14:45:18 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f46.google.com (mail-io1-f46.google.com [209.85.166.46]) (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 4Hg7dT47qcz3kqT; Thu, 28 Oct 2021 14:45:17 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f46.google.com with SMTP id d63so8443708iof.4; Thu, 28 Oct 2021 07:45:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=zfpPey5TjcpLI+WDp1UlCDbBe50UA4QULCo25k6u6UM=; b=2GGfr4dKUp464nYckWMpVq1BJ1lnvGBDk7XAAIXTX5qokIHmM+CBOc18XGNOEWtw7/ S9BQCR6PLs8mZmxYjIYUWMx7XJRtHItxDvEha+1Wo7336QMw/H46RpQIssuodRn4BcvZ 694TcFrg4K/KPapENpLqeInTN0jcaBWmdr/i8RCfS44tkMKvVEXSnGbZtIUQ1YGmSZdp Z5NG99QL4jkb6Rf4Q60BAvRuYlciBtepg0CB3MzCRlqjEbiIOD/BckTJ7yhri54NapOU ta+GLkL/BeMtHoOEgoCZWH+JxW03m6k9RRIxtfA5MWg3n5RJAoUC8l81vZjjFzlVXTtU VbAA== X-Gm-Message-State: AOAM532r9UxutFSNEqoyGRnImtlltVGJkZa6dZ/8lp7Me28l7/dXhqJE raoR8k+h1Vy+x6XwKppr9ByJduq+D4i8mK7Njf9R/8hpDsk= X-Google-Smtp-Source: ABdhPJwtFj/iwJ8hZQoyItxZpg5b8I11qGVp+TMZN0gWT8ssfAIqvuQs1cJEQZazEhAT/dD/9RTtjTasSuPIkfFMlII= X-Received: by 2002:a05:6638:1311:: with SMTP id r17mr1607142jad.76.1635432311105; Thu, 28 Oct 2021 07:45:11 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 From: Ed Maste Date: Thu, 28 Oct 2021 10:44:56 -0400 Message-ID: Subject: Deprecating smbfs(5) and removing it before FreeBSD 14 To: FreeBSD Current , freebsd-stable stable Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4Hg7dT47qcz3kqT X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.46 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-1.26 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[carpeddiem]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.68)[0.678]; NEURAL_HAM_MEDIUM(-0.94)[-0.938]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.46:from]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.46:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N The smbfs(5) filesystem supports only the obsolete SMBv1 protocol, and I propose removing it for FreeBSD 14. I know the CHERI folks have been using it but they plan to migrate away from it. It was broken for months before they fixed it, so I suspect nobody is using it on contemporary releases. I have review D32707 (https://reviews.freebsd.org/D32707) open to add this deprecation notice to the man page: The smbfs filesystem driver supports only the obsolete SMBv1 protocol. smbfs and userspace counterparts smbutil(1) and mount_smbfs(8) are not present in FreeBSD 14 and above. Users are advised to evaluate the sysutils/fusefs-smbnetfs port instead. A similar notice would be added to the smbutil and mount_smbfs man pages, and manu@ suggested having the userland utilities emit a warning when they are used. I am interested in comments, objections, or reports that anyone is in fact using smbfs. From eugen@grosbein.net Thu Oct 28 15:05:11 2021 X-Original-To: freebsd-stable@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 E157A1822256; Thu, 28 Oct 2021 15:05:32 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [IPv6:2a01:4f8:c2c:26d8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hg84r4lq8z3s4H; Thu, 28 Oct 2021 15:05:31 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id 19SF5Mx4014411 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 28 Oct 2021 15:05:22 GMT (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: emaste@freebsd.org Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.16.1/8.16.1) with ESMTPS id 19SF5KZu061391 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 28 Oct 2021 22:05:21 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 To: Ed Maste , FreeBSD Current , freebsd-stable stable References: From: Eugene Grosbein Message-ID: Date: Thu, 28 Oct 2021 22:05:11 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT autolearn=disabled version=3.4.2 X-Spam-Report: * -0.0 SHORTCIRCUIT No description available. * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on hz.grosbein.net X-Rspamd-Queue-Id: 4Hg84r4lq8z3s4H X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N 28.10.2021 21:44, Ed Maste wrote: > The smbfs(5) filesystem supports only the obsolete SMBv1 protocol, and > I propose removing it for FreeBSD 14. I know the CHERI folks have been > using it but they plan to migrate away from it. It was broken for > months before they fixed it, so I suspect nobody is using it on > contemporary releases. > > I have review D32707 (https://reviews.freebsd.org/D32707) open to add > this deprecation notice to the man page: > The smbfs filesystem driver supports only the obsolete SMBv1 protocol. > smbfs and userspace counterparts smbutil(1) and mount_smbfs(8) are not > present in FreeBSD 14 and above. Users are advised to evaluate the > sysutils/fusefs-smbnetfs port instead. > > A similar notice would be added to the smbutil and mount_smbfs man > pages, and manu@ suggested having the userland utilities emit a > warning when they are used. > > I am interested in comments, objections, or reports that anyone is in > fact using smbfs. I routinely use smbfs(5) to access files on Windows-based local file servers, both for read and write. Also, some hosters provide extra network storage (for backups etc.) available over SMB. Please do not remove what is not broken. From nobody Thu Oct 28 15:15:20 2021 X-Original-To: stable@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 CA1851827ED9 for ; Thu, 28 Oct 2021 15:15:30 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.netfence.it (mailserver.netfence.it [78.134.96.152]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mailserver.netfence.it", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hg8JK3Nxkz3wSc for ; Thu, 28 Oct 2021 15:15:29 +0000 (UTC) (envelope-from ml@netfence.it) Received: from [10.1.2.18] (alamar.local.netfence.it [10.1.2.18]) (authenticated bits=0) by soth.netfence.it (8.17.1/8.16.1) with ESMTPSA id 19SFFKOt075788 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for ; Thu, 28 Oct 2021 17:15:21 +0200 (CEST) (envelope-from ml@netfence.it) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netfence.it; s=202108; t=1635434121; bh=YhuHBw6P8J31a7TKR5mYJcdbzCFNdrk5ZTRu2NIZvcU=; h=Date:Subject:To:References:From:In-Reply-To; b=l4x4GyxJfcwO863jUL48MrCvUDmsN09Ig+RCucw8BT89qErwwJGjPzknjOIYyJJI6 AwFO44kMhq16J2LvNPivwDayDcMhDPJbgGV0R88tz9IwQaYnAuDnmb1bPMKu4xfPIs kYZgbOZH6MrrKnDEIuP18QYcpGz2QxCtEosAGjdI= X-Authentication-Warning: soth.netfence.it: Host alamar.local.netfence.it [10.1.2.18] claimed to be [10.1.2.18] Message-ID: <192ad495-83de-2b4d-c2e0-cca802373b12@netfence.it> Date: Thu, 28 Oct 2021 17:15:20 +0200 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Content-Language: en-US To: stable@freebsd.org References: From: Andrea Venturoli In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Hg8JK3Nxkz3wSc X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=netfence.it header.s=202108 header.b=l4x4GyxJ; dmarc=pass (policy=none) header.from=netfence.it; spf=pass (mx1.freebsd.org: domain of ml@netfence.it designates 78.134.96.152 as permitted sender) smtp.mailfrom=ml@netfence.it X-Spamd-Result: default: False [-3.94 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[netfence.it:s=202108]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:78.134.96.152]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[stable@freebsd.org]; HAS_XAW(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[netfence.it:+]; DMARC_POLICY_ALLOW(-0.50)[netfence.it,none]; NEURAL_HAM_SHORT(-0.94)[-0.939]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:35612, ipnet:78.134.0.0/17, country:IT]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 10/28/21 17:05, Eugene Grosbein wrote: > I routinely use smbfs(5) to access files on Windows-based local file servers, > both for read and write. > > Also, some hosters provide extra network storage (for backups etc.) available over SMB. > > Please do not remove what is not broken. IMVVVVHO... I *would* use it if it worked: typical case is trying to rescue a broken system with a live USB key and needing to copy some data to a different machine. Given it only supports SMBv1, I more and more find it useless, as the other side won't cope. If it was upgraded to support a newer version of SMB protocol... but that would be another story and it's unlikely to happen. bye av. From nobody Thu Oct 28 15:19:58 2021 X-Original-To: freebsd-stable@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 0FA9918297D4; Thu, 28 Oct 2021 15:20:09 +0000 (UTC) (envelope-from freebsd@oldach.net) Received: from nuc.oldach.net (hmo.in-vpn.de [IPv6:2001:67c:1407:60::1]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "nuc.oldach.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hg8Pg6QPqz4S1Y; Thu, 28 Oct 2021 15:20:07 +0000 (UTC) (envelope-from freebsd@oldach.net) Received: from nuc.oldach.net (localhost [127.0.0.1]) by nuc.oldach.net (8.17.1/8.17.1/hmo17dec20) with ESMTPS id 19SFJwlk082442 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 28 Oct 2021 17:19:58 +0200 (CEST) (envelope-from freebsd@oldach.net) Received: (from hmo@localhost) by nuc.oldach.net (8.17.1/8.17.1/Submit) id 19SFJwF0082441; Thu, 28 Oct 2021 17:19:58 +0200 (CEST) (envelope-from freebsd@oldach.net) Message-Id: <202110281519.19SFJwF0082441@nuc.oldach.net> Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 In-Reply-To: from Ed Maste at "28 Oct 2021 10:44:56" To: emaste@freebsd.org (Ed Maste) Date: Thu, 28 Oct 2021 17:19:58 +0200 (CEST) Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org From: freebsd@oldach.net (Helge Oldach) X-No-Archive: Yes List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: inspected by milter-greylist-4.6.4 (nuc.oldach.net [0.0.0.0]); Thu, 28 Oct 2021 17:19:58 +0200 (CEST) for IP:127.0.0.1 DOMAIN:localhost HELO:nuc.oldach.net FROM:freebsd@oldach.net RCPT: X-Rspamd-Queue-Id: 4Hg8Pg6QPqz4S1Y X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@oldach.net designates 2001:67c:1407:60::1 as permitted sender) smtp.mailfrom=freebsd@oldach.net X-Spamd-Result: default: False [-3.15 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[oldach.net]; NEURAL_HAM_LONG(-1.00)[-1.000]; MID_RHS_MATCH_FROMTLD(0.00)[]; NEURAL_HAM_SHORT(-0.86)[-0.856]; FROM_NO_DN(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:29670, ipnet:2001:67c:1400::/45, country:DE]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N Ed Maste wrote on Thu, 28 Oct 2021 16:44:56 +0200 (CEST): > The smbfs(5) filesystem supports only the obsolete SMBv1 protocol, and > I propose removing it for FreeBSD 14. I know the CHERI folks have been > using it but they plan to migrate away from it. It was broken for > months before they fixed it, so I suspect nobody is using it on > contemporary releases. I'm using SMBv1 to connect a FreeBSD VM running under VirtualBox with the host file system. This is significantly more reliable than vboxvfs - which, to name one annoying issue, still stumbles over large directories and cuts them short. SMBv1 security concerns aside - this is a local application not touching any wires or radio waves. Please don't remove it. In case the decision would be in favor of removal, please convert it into a decent, light-weight port. Kind regards Helge From nobody Thu Oct 28 15:26:42 2021 X-Original-To: freebsd-stable@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 39E72182C163 for ; Thu, 28 Oct 2021 15:26:44 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (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 4Hg8YJ0pxDz4Vb5 for ; Thu, 28 Oct 2021 15:26:44 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-qt1-x82f.google.com with SMTP id 19so4488913qtt.7 for ; Thu, 28 Oct 2021 08:26:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=gPS3xPMGEVxYoF0zKCE1MuXrrGeEl5ey8sqot95Cxcs=; b=TpiVFZvpsZgBqrUhG5G3ZP1nBvDsjbGiEADg6Ib1x500vYTb1lycuC0ShqEeSlSE8C GYhmxy9o58IuMkRSYWtUKCWzAsjS5G5f+fe4sQ6vVu/eWQSNtdZwpbsXDeiH0aYVPnxJ oEytLsq69xs0iDAds0FqozePg0adPvGjVaymNGtctl14pfebtXQZye4NUWYWrh7eXoQu FbCf1pWO+GLSzOaaaueOfmD2GwL7vU6E/Xw+YXsk1R37RuCpWeT1BQOwUnh3BNqwZL/N VEOacjLVBVj3mwgChLvKKU4HJTs/5Oz0gdiClsPYUXftmCtH8hl8Q5+rwbpxsdmuw6Gs I5CQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=gPS3xPMGEVxYoF0zKCE1MuXrrGeEl5ey8sqot95Cxcs=; b=8RONqePqLEb3OoJUdozNEr2KWOrV7Y6zybfhso5bcFOQpmSN8usy5Hx+Sy/7uqL1pN oP/s+efNf4assEBBIrGyln0fgw5fWxBIM2zDcma+essXoJoSMNAUINt450VyOnOLDh9x J3ttwtAyB90gBSu/YGwXYiNduMJhPbGHteCNia8SHufq8/CUakO2P+QhMFCJzgpEXeAM c6uvi/hIQjec5A3bfZy+RAo8omjgt8aGrh9UgC7YV7M6Fd4WWKP9xgzlN6gfMgNWSaYX 3x8uKUd5sil/NXzOw1vwjq8YgEhXt0mv8uGlRgdJsVDrN9yb7w2ma487tcZmQYyoG0M/ HFlg== X-Gm-Message-State: AOAM532x8SBLjcf1DpkNKCqQDCitHspaTvHc7qjETQ4/mq2cnfGts6OX GYXJEMvaeqFknJDSD5vS+RHHhA== X-Google-Smtp-Source: ABdhPJykr/ITrKvlrVSLzCzMQmKYdg1BWVYmPBgPL84KtZzI8v/spFxGLFBU7JQwbBoo90b3oRdJhg== X-Received: by 2002:ac8:5613:: with SMTP id 19mr5563986qtr.100.1635434803551; Thu, 28 Oct 2021 08:26:43 -0700 (PDT) Received: from mutt-hbsd (pool-100-16-224-136.bltmmd.fios.verizon.net. [100.16.224.136]) by smtp.gmail.com with ESMTPSA id y8sm2215073qko.36.2021.10.28.08.26.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Oct 2021 08:26:43 -0700 (PDT) Date: Thu, 28 Oct 2021 11:26:42 -0400 From: Shawn Webb To: Ed Maste Cc: FreeBSD Current , freebsd-stable stable Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Message-ID: <20211028152642.ejvwewkztewotln4@mutt-hbsd> X-Operating-System: FreeBSD mutt-hbsd 14.0-CURRENT-HBSD FreeBSD 14.0-CURRENT-HBSD X-PGP-Key: https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/blob/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc References: List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="brkcv3d7hvmd7n7w" Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4Hg8YJ0pxDz4Vb5 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N --brkcv3d7hvmd7n7w Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 28, 2021 at 10:44:56AM -0400, Ed Maste wrote: > The smbfs(5) filesystem supports only the obsolete SMBv1 protocol, and > I propose removing it for FreeBSD 14. I know the CHERI folks have been > using it but they plan to migrate away from it. It was broken for > months before they fixed it, so I suspect nobody is using it on > contemporary releases. >=20 > I have review D32707 (https://reviews.freebsd.org/D32707) open to add > this deprecation notice to the man page: > The smbfs filesystem driver supports only the obsolete SMBv1 protoco= l. > smbfs and userspace counterparts smbutil(1) and mount_smbfs(8) are n= ot > present in FreeBSD 14 and above. Users are advised to evaluate the > sysutils/fusefs-smbnetfs port instead. >=20 > A similar notice would be added to the smbutil and mount_smbfs man > pages, and manu@ suggested having the userland utilities emit a > warning when they are used. >=20 > I am interested in comments, objections, or reports that anyone is in > fact using smbfs. >=20 It seems that smbfs might be used with some level of frequency in virtualized environments. I wonder if providing a 9pfs client would be a good step in helping deprecate smbfs. Thanks, --=20 Shawn Webb Cofounder / Security Engineer HardenedBSD https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A= 4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc --brkcv3d7hvmd7n7w Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEA6TL67gupaZ9nzhT/y5nonf44foFAmF6wTAACgkQ/y5nonf4 4fpoXw//Q04ZLd66de+3d5PpWib5YDiJrHexiDyqahYGhhWcj3fLl3sMdkNoQ46L GVtqo4yeh6qs4EnUSSvNkXk0bO7R3nvaMORUWk3zHnxh98V5mj/O7abxn4DSnXkH Lk2CwoGMozizWL8Ht+s1Xsppl3QeUc1QwaXIFwf6blsmjU/+Gzusg9nVoPuaOhQm lurbEzXZJg2akXaG3apJJcB9MKBLGZV3adjFJpnyCnOa8pP/xOmc4ipsAHAUGQ82 pwAj4OM68MN3uUH3lTirn2l8Bm4+EbQXF104yc3BErEP7qpPAu/kcMvqTfKMDd9m R8zwSbh6x9FsK/qczVpqKP0nwQt8Nb9a6cVpA4/Oo0+uSrZMjNBzbWlnAscz0tW0 x4/WWfniT8wt4qDUwl20muwH8cWQaqhvIPfxruYQuBLnxyPejcwAffEX4IfkC3D9 LPGszuAkfXm1+zTQc8SHjC34x5hgK89b4vnZV7yh//uj/onMOI6pKBeyxU9EEu2U gMD+oreHXD+6G+r09tQa1E24ish/4U8Ap9LnyE0898Tr/XzmIo385D7Rp3MsJZlS 31m3Mv7EdyCPTo0l2AGHYt+YRq9FvibSh4h3ZUVEZrkcpbYVTavDQiEUv+GGMirU bPkIcIzhzpEIdaxIRVdPnID0G073U1hI2ipDqvGHq9/vHtMVqFw= =9HE4 -----END PGP SIGNATURE----- --brkcv3d7hvmd7n7w-- From nobody Thu Oct 28 15:37:33 2021 X-Original-To: freebsd-stable@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 CEB291832A3C; Thu, 28 Oct 2021 15:37:46 +0000 (UTC) (envelope-from SRS0=oNTo=PQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hg8p229Srz4c8F; Thu, 28 Oct 2021 15:37:46 +0000 (UTC) (envelope-from SRS0=oNTo=PQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 5010928417; Thu, 28 Oct 2021 17:37:38 +0200 (CEST) Received: from illbsd.quip.test (ip-78-45-215-131.net.upcbroadband.cz [78.45.215.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 708F728411; Thu, 28 Oct 2021 17:37:36 +0200 (CEST) Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 To: Ed Maste , FreeBSD Current , freebsd-stable stable References: From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <8d25d2f4-24e2-5b19-5c81-2fe12dc937b7@quip.cz> Date: Thu, 28 Oct 2021 17:37:33 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Hg8p229Srz4c8F X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On 28/10/2021 16:44, Ed Maste wrote: > The smbfs(5) filesystem supports only the obsolete SMBv1 protocol, and > I propose removing it for FreeBSD 14. I know the CHERI folks have been > using it but they plan to migrate away from it. It was broken for > months before they fixed it, so I suspect nobody is using it on > contemporary releases. > > I have review D32707 (https://reviews.freebsd.org/D32707) open to add > this deprecation notice to the man page: > The smbfs filesystem driver supports only the obsolete SMBv1 protocol. > smbfs and userspace counterparts smbutil(1) and mount_smbfs(8) are not > present in FreeBSD 14 and above. Users are advised to evaluate the > sysutils/fusefs-smbnetfs port instead. > > A similar notice would be added to the smbutil and mount_smbfs man > pages, and manu@ suggested having the userland utilities emit a > warning when they are used. > > I am interested in comments, objections, or reports that anyone is in > fact using smbfs. I am working for one company where smbfs is heavily used to connect Windows / MacOS / Linux / FreeBSD (12.2) machines and we are really sad that FreeBSD's mount_smbfs does not support SMBv2 / SMBv3 protocols (so we are using SMBv1 with all the risk). I tried fusefs alternatives from the ports tree in the past but it never worked as is needed. From our point of view smbnetfs cannot replace mount_smbfs. I cannot found any good examples of how to configure it to mount about 20 shares from /etc/fstab on boot as user root from different hosts with different login, passwords and mount options to defined mount points. Everything seems to be very differently designed to work for non-root user with configuration in users home, not system wide and mounting in some strange hierarchy. (and bad performance was cited by many on other platforms too) It was discussed in the past in some other FreeBSD mailinglist that it is not so easy to implement SMBv2 in to mount_smbfs. But is there any possibility to make it as some sponsored work? What about FreeBSD Foundation? There were some paid projects in the past. Or some other bounty program. Is there anybody who have the skill to implement it if there is good amount of $? If I am "well informed" FreeBSD is the only widely used OS not supporting SMBv2. (MacOS, Linux, Solaris have it supported) I will be really glad "if somebody can fix it" in the base. (or at least document how to use smbnetfs the way mount_smbfs is used) Kind regards Miroslav Lachman From nobody Thu Oct 28 16:25:52 2021 X-Original-To: freebsd-stable@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 30A6B1829941; Thu, 28 Oct 2021 16:26:14 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f41.google.com (mail-io1-f41.google.com [209.85.166.41]) (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 4Hg9sx6Bdfz3CND; Thu, 28 Oct 2021 16:26:13 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f41.google.com with SMTP id m184so8945552iof.1; Thu, 28 Oct 2021 09:26:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=r5ZRlgox9oMC33IfcuWqruXKYidbGZ99/43wZj8Rqo0=; b=gYGzinSB4qYeY4c2r2JrA+djQD8IdLD1pBpGit56pE9uUO81OZupjFTyWyPlT3NPrP jl0bgYTK9EJEAIBpKssmPGrKaoO8mvVbk9roMb4Yb8jLvJuwiL2hK3JZaIhxZnRL+zfz J89ZmcbLxQl8ELDUn/0kCggdLWUpfOKMayzFM0+eue/I5ITZlYce0TMrkbxUfZ14uBWL ahEisPkJxyv92soJ9rdHK11QQGdBpFFBM2k7uzHp6emnT1sfPYVZkmF3Lv29+Hm7AhKW yT1dssqA7WCdY0rpjx9z6WITXnrqfzUGykA53189q+krcSOcBH+JL46b8AfbnwFzRZ+a O/tQ== X-Gm-Message-State: AOAM533278wYiQj2cNQwyzBz1sfif0ojkiKub1Zf21uas1abRWcs/Plh 8ONsWsk3ImW4P27JPkijQnb10hiJI4Lv+m8BhTlas9b61Yc= X-Google-Smtp-Source: ABdhPJwV9EXKWQpDDm2bJJ3pqVR2rt6S3SccvqOuvtJS5kvCJw+YWAV+bTdWUlXYhIlG51lpFgeuWH1FWOMypfYk3tU= X-Received: by 2002:a5d:9416:: with SMTP id v22mr3729483ion.96.1635438367414; Thu, 28 Oct 2021 09:26:07 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Ed Maste Date: Thu, 28 Oct 2021 12:25:52 -0400 Message-ID: Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 To: Eugene Grosbein Cc: FreeBSD Current , freebsd-stable stable Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4Hg9sx6Bdfz3CND X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Thu, 28 Oct 2021 at 11:05, Eugene Grosbein wrote: > > Please do not remove what is not broken. That is exactly the problem though: it was broken. It was fixed only because the CHERI folks found that it wasn't working and fixed it, and they are not going to be using it much longer. If nobody else regularly tests it in -CURRENT it will break again, and will end up broken in a release. That said, since it does seem that several folks are still currently using i I'll avoid trying to remove it in the near future. A caveat for the man pages may instead be something like: The smbfs filesystem driver supports only the obsolete SMBv1 protocol. smbfs is unmaintained and may not function correctly in FreeBSD 14 or later. Users are advised to evaluate the sysutils/fusefs-smbnetfs port instead. From nobody Thu Oct 28 16:32:31 2021 X-Original-To: freebsd-stable@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 7FC22182C4DE; Thu, 28 Oct 2021 16:32:53 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-il1-f170.google.com (mail-il1-f170.google.com [209.85.166.170]) (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 4HgB1d39rvz3Grb; Thu, 28 Oct 2021 16:32:53 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-il1-f170.google.com with SMTP id s3so7627499ild.0; Thu, 28 Oct 2021 09:32:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cscR72H3Vrjj8pWvcZ1kHUDXVpYQeFA6RNMEwXj+hng=; b=sbOE4P8SVdXOjkbjP3Epf4AB5w4fr3aatuSUNSSIG4dnfm6AhSrhedaE+Ly9R9dBjO HvKx639JdQNSJ4C+GtEgPOQpQgvxe7+fsuZQTgJZ3GszbYI46+8/jWhtDVJaShGGsWLN VjinLaO+E+GoDUZHvA3BlOX5+GXbsTSSgLzeNC+wOivlLqnGI/bc5s/1v5sRCPZhLSZs C/1fIQwL8c6e021yRPps2/wVUHbW5Nff9igssknO+h5oDnfApT3MC+CWByXrwGFlzydg S+5ljsTSZ8u36ZJJ1nV85j108t+4rN16VkXw8dF01xQ77eBm3jNBmozWZJSJCfRd+2TL qKQQ== X-Gm-Message-State: AOAM533fn2xNAsSsZFHJWu+GCMxGIL1KnJuqgi5tt61tGv8B+gZ072Os 0saLAkQpgKzHMWsozXAGAXMG+5Q7Yl1coSqcmlSlL4Do X-Google-Smtp-Source: ABdhPJwLSc0AauL4O6NDI5LyWPnZ8ISytbuPIuezZdJ4SNLpTL1vtSzuK9ANWs9UsHqXlbgNWmDl3lm8NuLfifI/gGM= X-Received: by 2002:a92:d7c3:: with SMTP id g3mr3865072ilq.35.1635438767292; Thu, 28 Oct 2021 09:32:47 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <20211028152642.ejvwewkztewotln4@mutt-hbsd> In-Reply-To: <20211028152642.ejvwewkztewotln4@mutt-hbsd> From: Ed Maste Date: Thu, 28 Oct 2021 12:32:31 -0400 Message-ID: Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 To: Shawn Webb Cc: FreeBSD Current , freebsd-stable stable Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4HgB1d39rvz3Grb X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Thu, 28 Oct 2021 at 11:26, Shawn Webb wrote: > > It seems that smbfs might be used with some level of frequency in > virtualized environments. I wonder if providing a 9pfs client would be > a good step in helping deprecate smbfs. Indeed, that addresses one of the primary reasons it is still being used, including by CHERI. Their plan to migrate away from smbfs is based on moving to 9pfs. From nobody Thu Oct 28 17:22:00 2021 X-Original-To: freebsd-stable@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 9BC971819176; Thu, 28 Oct 2021 17:22:28 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172]) (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 4HgC6r3Wsdz3nSj; Thu, 28 Oct 2021 17:22:28 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: by mail-lj1-f172.google.com with SMTP id 17so8811245ljq.0; Thu, 28 Oct 2021 10:22:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=heYUqypMGQ1rKmpGipzpGq6k1yYodmntY/C6BinHDts=; b=zYBCeRoOLGL8/x0/iXWgurI6j+kwDElo3pe0aGWzbMc6SPXmP+x4rizPBEujTqYfcW SqZTJVkSlWzOR2uJ8PWFU2RoryahsMs9jHAkfBa8kzhruAooknpDIqQ/bU1s3Xj/AgBz 0oii/9Y9iAVxkoytlEcU1TEd0W78FtiwqRThCpBMH4igZrkTpkfjk0f00OZyNQ+PBM9Z JD5wUvueAyDVTBeDujw5XwbHkjMOBnfv8PFRIKJCx/6DlJIFz0lnPNoMd8RKnoPGkpeY YAjaTpiObSgbFSJjna6i8OkwCK4Mkdz1wsGkPKfmweQAYHnnc6Hg154ZrdMsHNJCcVp3 7SdA== X-Gm-Message-State: AOAM531izvfikdcAWEXZQP1vfLqF5UZCZa7HjRZNh6G6cT3jwbzHTDsF VnLm3gbydaIv17klb/bizsWgfvtFzYY18Q== X-Google-Smtp-Source: ABdhPJyQLxhcTR90gr9EjYmTP+HB9Kzvtsz38OWWvI2gco7nXcGxHApjkLocJIIi7+q0njc0CnU4sw== X-Received: by 2002:a2e:81cb:: with SMTP id s11mr5996490ljg.222.1635441746990; Thu, 28 Oct 2021 10:22:26 -0700 (PDT) Received: from mail-lj1-f170.google.com (mail-lj1-f170.google.com. [209.85.208.170]) by smtp.gmail.com with ESMTPSA id h4sm368811lft.184.2021.10.28.10.22.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 28 Oct 2021 10:22:26 -0700 (PDT) Received: by mail-lj1-f170.google.com with SMTP id 1so6044539ljv.2; Thu, 28 Oct 2021 10:22:26 -0700 (PDT) X-Received: by 2002:a2e:a554:: with SMTP id e20mr6189528ljn.500.1635441746690; Thu, 28 Oct 2021 10:22:26 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <8d25d2f4-24e2-5b19-5c81-2fe12dc937b7@quip.cz> In-Reply-To: <8d25d2f4-24e2-5b19-5c81-2fe12dc937b7@quip.cz> From: Gleb Popov Date: Thu, 28 Oct 2021 20:22:00 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 To: Miroslav Lachman <000.fbsd@quip.cz> Cc: FreeBSD Current , freebsd-stable stable Content-Type: multipart/alternative; boundary="0000000000005cc94d05cf6cf465" X-Rspamd-Queue-Id: 4HgC6r3Wsdz3nSj X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --0000000000005cc94d05cf6cf465 Content-Type: text/plain; charset="UTF-8" On Thu, Oct 28, 2021 at 6:39 PM Miroslav Lachman <000.fbsd@quip.cz> wrote: > I am working for one company where smbfs is heavily used to connect > Windows / MacOS / Linux / FreeBSD (12.2) machines and we are really sad > that FreeBSD's mount_smbfs does not support SMBv2 / SMBv3 protocols (so > we are using SMBv1 with all the risk). I tried fusefs alternatives from > the ports tree in the past but it never worked as is needed. From our > point of view smbnetfs cannot replace mount_smbfs. > I cannot found any good examples of how to configure it to mount about > 20 shares from /etc/fstab on boot as user root from different hosts with > different login, passwords and mount options to defined mount points. > Everything seems to be very differently designed to work for non-root > user with configuration in users home, not system wide and mounting in > some strange hierarchy. (and bad performance was cited by many on other > platforms too) > It was discussed in the past in some other FreeBSD mailinglist that it > is not so easy to implement SMBv2 in to mount_smbfs. But is there any > possibility to make it as some sponsored work? What about FreeBSD > Foundation? There were some paid projects in the past. Or some other > bounty program. Is there anybody who have the skill to implement it if > there is good amount of $? > > If I am "well informed" FreeBSD is the only widely used OS not > supporting SMBv2. (MacOS, Linux, Solaris have it supported) > I will be really glad "if somebody can fix it" in the base. > > (or at least document how to use smbnetfs the way mount_smbfs is used) > > Kind regards > Miroslav Lachman > > I'm also aware of a local company that actively uses smbfs. Removing it would probably cause them to switch to Linux, which is a pity. --0000000000005cc94d05cf6cf465-- From nobody Thu Oct 28 19:33:18 2021 X-Original-To: freebsd-stable@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 A09991834027; Thu, 28 Oct 2021 19:33:22 +0000 (UTC) (envelope-from SRS0=oNTo=PQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HgG1t3MTVz3JyD; Thu, 28 Oct 2021 19:33:22 +0000 (UTC) (envelope-from SRS0=oNTo=PQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 7B4D928411; Thu, 28 Oct 2021 21:33:20 +0200 (CEST) Received: from illbsd.quip.test (ip-78-45-215-131.net.upcbroadband.cz [78.45.215.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 20A0A28417; Thu, 28 Oct 2021 21:33:18 +0200 (CEST) Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 To: Ed Maste , Eugene Grosbein Cc: FreeBSD Current , freebsd-stable stable References: From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Thu, 28 Oct 2021 21:33:18 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4HgG1t3MTVz3JyD X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On 28/10/2021 18:25, Ed Maste wrote: > On Thu, 28 Oct 2021 at 11:05, Eugene Grosbein wrote: >> >> Please do not remove what is not broken. > > That is exactly the problem though: it was broken. It was fixed only > because the CHERI folks found that it wasn't working and fixed it, and > they are not going to be using it much longer. If nobody else > regularly tests it in -CURRENT it will break again, and will end up > broken in a release. Can this problem be covered by some automated tests to catch it sooner - before release? > That said, since it does seem that several folks > are still currently using i I'll avoid trying to remove it in the near > future. > > A caveat for the man pages may instead be something like: > > The smbfs filesystem driver supports only the obsolete SMBv1 protocol. > smbfs is unmaintained and may not function correctly in FreeBSD 14 or > later. Users are advised to evaluate the sysutils/fusefs-smbnetfs port > instead. Kind regards Miroslav Lachman From nobody Thu Oct 28 20:49:14 2021 X-Original-To: freebsd-stable@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 7FB871832A29; Thu, 28 Oct 2021 20:49:21 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HgHjY32Q4z3vP3; Thu, 28 Oct 2021 20:49:21 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id E7A363C0199; Thu, 28 Oct 2021 20:49:14 +0000 (UTC) Date: Thu, 28 Oct 2021 20:49:14 +0000 From: Brooks Davis To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Ed Maste , Eugene Grosbein , FreeBSD Current , freebsd-stable stable Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Message-ID: <20211028204914.GC81740@spindle.one-eyed-alien.net> References: List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-Rspamd-Queue-Id: 4HgHjY32Q4z3vP3 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 28, 2021 at 09:33:18PM +0200, Miroslav Lachman wrote: > On 28/10/2021 18:25, Ed Maste wrote: > > On Thu, 28 Oct 2021 at 11:05, Eugene Grosbein wrot= e: > >> > >> Please do not remove what is not broken. > >=20 > > That is exactly the problem though: it was broken. It was fixed only > > because the CHERI folks found that it wasn't working and fixed it, and > > they are not going to be using it much longer. If nobody else > > regularly tests it in -CURRENT it will break again, and will end up > > broken in a release. >=20 > Can this problem be covered by some automated tests to catch it sooner -= =20 > before release? FWIW, any testing at all would have caught this. It paniced on unmount in a kernel with INVARIANTS. The awkward thing about testing it is that it requires a server. We'd have caught it sooner if we hadn't had a major stall in merging FreeBSD head to CheriBSD. We're hoping to stop using it because it's slow, server support will eventually go away, etc. We don't really have an opinion about it staying or going. -- Brooks --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJhewzKAAoJEKzQXbSebgfARbEH/iI3XIthG+cIYUq6XtOd25r0 XvJQ6fjnbXZElLI/BDLTXe4gND04RCla/YtmJPPip0ykjTr7rsGzouLdLzXy2Gvz ojyUTH2ubq8bHniD9vefGpqWheYwBmewTedoN1vpleXIcGQyGsjouMB7M04ZEKsB FgHlKgCbo+zlUiKFUYqVImmh22zKHV7UzVkeZOg7BTvFY3WBQVYtDJArxwwgubJZ z9MasqxngVQ69Jk+4lIKmNESEr+0ixaOs2LhHFJqRrDxWZcRnf0ZZzYBLiYOvyZm Aoia3PZK0ZdUSJTbxygEIZT+lFxONS95A3omB+JyyLJT8g88lDKgoOTxitOdTts= =NXlm -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From nobody Thu Oct 28 22:47:02 2021 X-Original-To: freebsd-stable@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 73251181C78F; Thu, 28 Oct 2021 22:47:16 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 4HgLKc07nZz3GGr; Thu, 28 Oct 2021 22:47:15 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from kalamity.joker.local (123-48-130-181.area1b.commufa.jp [123.48.130.181]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 19SMl3es004849; Fri, 29 Oct 2021 07:47:04 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Fri, 29 Oct 2021 07:47:02 +0900 From: Tomoaki AOKI To: freebsd-stable@freebsd.org Cc: freebsd-current@freebsd.org, Miroslav Lachman <000.fbsd@quip.cz>, Ed Maste Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Message-Id: <20211029074702.d69cba39a643f3f912f8ec81@dec.sakura.ne.jp> In-Reply-To: <8d25d2f4-24e2-5b19-5c81-2fe12dc937b7@quip.cz> References: <8d25d2f4-24e2-5b19-5c81-2fe12dc937b7@quip.cz> Reply-To: junchoon@dec.sakura.ne.jp Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4HgLKc07nZz3GGr X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Thu, 28 Oct 2021 17:37:33 +0200 Miroslav Lachman <000.fbsd@quip.cz> wrote: > On 28/10/2021 16:44, Ed Maste wrote: > > The smbfs(5) filesystem supports only the obsolete SMBv1 protocol, and > > I propose removing it for FreeBSD 14. I know the CHERI folks have been > > using it but they plan to migrate away from it. It was broken for > > months before they fixed it, so I suspect nobody is using it on > > contemporary releases. > > > > I have review D32707 (https://reviews.freebsd.org/D32707) open to add > > this deprecation notice to the man page: > > The smbfs filesystem driver supports only the obsolete SMBv1 protocol. > > smbfs and userspace counterparts smbutil(1) and mount_smbfs(8) are not > > present in FreeBSD 14 and above. Users are advised to evaluate the > > sysutils/fusefs-smbnetfs port instead. > > > > A similar notice would be added to the smbutil and mount_smbfs man > > pages, and manu@ suggested having the userland utilities emit a > > warning when they are used. > > > > I am interested in comments, objections, or reports that anyone is in > > fact using smbfs. > > I am working for one company where smbfs is heavily used to connect > Windows / MacOS / Linux / FreeBSD (12.2) machines and we are really sad > that FreeBSD's mount_smbfs does not support SMBv2 / SMBv3 protocols (so > we are using SMBv1 with all the risk). I tried fusefs alternatives from > the ports tree in the past but it never worked as is needed. From our > point of view smbnetfs cannot replace mount_smbfs. > I cannot found any good examples of how to configure it to mount about > 20 shares from /etc/fstab on boot as user root from different hosts with > different login, passwords and mount options to defined mount points. > Everything seems to be very differently designed to work for non-root > user with configuration in users home, not system wide and mounting in > some strange hierarchy. (and bad performance was cited by many on other > platforms too) I, as an end-user who need to access local NAS, tried it a few yearsago (when it once broken by struct sockbuf issue that I finally sent patch) and had concluded smbnetfs is unusable for me. Additionally, it was quite unstable ATM. Sudden forcible unmount and failing remount. If it worked as expected, I wouldn't have tried digging into and sent Bug 182963. BTW, current in-tree code is broken for me and mandated patch proposed on Bug 90815. There are 3 patches uploaded and I use second one for years. Third one worked, too when I tried, but not continually using. The first one would no longer applicable. > It was discussed in the past in some other FreeBSD mailinglist that it > is not so easy to implement SMBv2 in to mount_smbfs. But is there any > possibility to make it as some sponsored work? What about FreeBSD > Foundation? There were some paid projects in the past. Or some other > bounty program. Is there anybody who have the skill to implement it if > there is good amount of $? +1 for FreeBSD Foundation project. But possibly we need to delete current smbfs code from base and switch to ports (sysutils/*?) if it require some code having incompatible license for base. Anyway, please don't remove it unless usable alternative appears. > If I am "well informed" FreeBSD is the only widely used OS not > supporting SMBv2. (MacOS, Linux, Solaris have it supported) > I will be really glad "if somebody can fix it" in the base. > > (or at least document how to use smbnetfs the way mount_smbfs is used) > > Kind regards > Miroslav Lachman > -- Tomoaki AOKI From nobody Fri Oct 29 15:37:10 2021 X-Original-To: freebsd-stable@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 096171821E03; Fri, 29 Oct 2021 15:37:14 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hgmkx5t6Mz3PRg; Fri, 29 Oct 2021 15:37:13 +0000 (UTC) (envelope-from gjb@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1635521833; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type; bh=YHARxc56yqcWuwDsVmpxENASLERBjBzy/3vCKV6O7kU=; b=oOIkFca5GY2cXyM1MmIosgRa1nwUjYSSOQ9WYpxOENVIz1Jtn8DJAUZn55YqnZ3YWF40fP TDckbELs2ce7auv9h4I+n3ek36V2e1GhjVBbr+DTZpVSQ9h+8Gyr0aLGrNTUrXB6gMtkiy wGHLTr45T1pE/ADlkbYGnB1Clp6tkGk7p5P9UVpYEWb/WHtZoV0hbHQGX0oEULlLWUXtHf tPEBKoxFv/j3jmY98+2GTz7Cvyqs+uSQUpA/y3EiwtrhGtdiJYOJJedLWisHNqIXUpM4gN QT2k0PhG8ofNZzhoZA7UoIOzSZeyF6YsOWgy0/L1vI9vkEbKOKVr0QO7G5kTiQ== Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 5AC8818940; Fri, 29 Oct 2021 15:37:13 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Fri, 29 Oct 2021 15:37:10 +0000 From: Glen Barber To: freebsd-snapshots@freebsd.org, freebsd-stable@freebsd.org Cc: FreeBSD Release Engineering Team Subject: FreeBSD 12.3-BETA2 Now Available Message-ID: <20211029153710.GF2620@FreeBSD.org> List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1635521833; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type; bh=YHARxc56yqcWuwDsVmpxENASLERBjBzy/3vCKV6O7kU=; b=L4op3zIzP+KA6JRl70daht7iS9xf4mG6Khs/4VjsUqzCVX9T8dr/f86/n7KOL/u1EoEpW6 G4qFVpql4MNR342CYQOO16vMHkzCfLjA+z1h2QIMJyvw3VCdhI+aLQ4tAPZcY6KXVyoSWm CXsiiX/nubGTKHCr8Tny66rixnYYwgB5tQBHEv+xMbNXDOymHUrccnQ3AmnvfY/Fkw4Jvr Jc0cOf9VI4YxYh4HtGH2jqzWRc3DmzvYU4bXJ6WdXTBBZK3k0oAjRHL5dDm1TGZvK8Fpss fQuptWfvL80ML9UrNB1ZjBmfrodtJVEy9Rr6V754jKDpzbaN4PA/WwWHUejZmQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1635521833; a=rsa-sha256; cv=none; b=b4W67ciDpOgZXL1EGNEn9Iw9aoz1/JStYgqehaU7NjXTA0RS9ks+kvmOCf62NhYFiWj0BQ jWRi17k/pZqCM2Pn7T+Wmt7jAaCdzQcBisWWGfrW0DdDuYNwScyqPdOjZW7D18usfuh28/ Mnq1xaB4sENqX911zO+JiH/nyv+IhNvS3saFbOxwYc8XtH1SSsd2pfl04CSNeZjV59uqXI xKdbRgxxdFUeKDpGzjspKxtrSuwZItZNQamVGC0J2IsasrcrHsMIYWykVq1sDh29E04jEP mwYZLFVoNR2uPmKzDFlDp+xe2ZgOK5gQiBNxvia9Hk+woTKlmldo0bRyiPA9Gg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The second BETA build of the 12.3-RELEASE release cycle is now available. Installation images are available for: o 12.3-BETA2 amd64 GENERIC o 12.3-BETA2 i386 GENERIC o 12.3-BETA2 powerpc GENERIC o 12.3-BETA2 powerpc64 GENERIC64 o 12.3-BETA2 powerpcspe MPC85XXSPE o 12.3-BETA2 sparc64 GENERIC o 12.3-BETA2 armv6 RPI-B o 12.3-BETA2 armv7 BANANAPI o 12.3-BETA2 armv7 BEAGLEBONE o 12.3-BETA2 armv7 CUBIEBOARD o 12.3-BETA2 armv7 CUBIEBOARD2 o 12.3-BETA2 armv7 CUBOX-HUMMINGBOARD o 12.3-BETA2 armv7 RPI2 o 12.3-BETA2 armv7 WANDBOARD o 12.3-BETA2 armv7 GENERICSD o 12.3-BETA2 aarch64 GENERIC o 12.3-BETA2 aarch64 RPI3 o 12.3-BETA2 aarch64 PINE64 o 12.3-BETA2 aarch64 PINE64-LTS Note regarding arm SD card images: For convenience for those without console access to the system, a freebsd user with a password of freebsd is available by default for ssh(1) access. Additionally, the root user password is set to root. It is strongly recommended to change the password for both users after gaining access to the system. Installer images and memory stick images are available here: https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.3/ The image checksums follow at the end of this e-mail. If you notice problems you can report them through the Bugzilla PR system or on the -stable mailing list. If you would like to use SVN to do a source based update of an existing system, use the "releng/12.3" branch. A summary of changes since 12.3-BETA1 includes: o An update to cmp(1) to limit stack garbage limits. o An update to tzdata to correct DST in Palestine. o An update to tzdata to correct DST in Fiji. Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 12.3-RELEASE cycle progresses. === Virtual Machine Disk Images === VM disk images are available for the amd64, i386, and aarch64 architectures. Disk images may be downloaded from the following URL (or any of the FreeBSD download mirrors): https://download.freebsd.org/ftp/releases/VM-IMAGES/12.3-BETA2/ The partition layout is: ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label) ~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label) ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label) The disk images are available in QCOW2, VHD, VMDK, and raw disk image formats. The image download size is approximately 135 MB and 165 MB respectively (amd64/i386), decompressing to a 21 GB sparse image. Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI loader file is needed for qemu-system-aarch64 to be able to boot the virtual machine images. See this page for more information: https://wiki.freebsd.org/arm64/QEMU To boot the VM image, run: % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \ -bios QEMU_EFI.fd -serial telnet::4444,server -nographic \ -drive if=none,file=VMDISK,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -device virtio-net-device,netdev=net0 \ -netdev user,id=net0 Be sure to replace "VMDISK" with the path to the virtual machine image. === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are available in the following regions: af-south-1 region: ami-077f91c5579626bad eu-north-1 region: ami-01c6e730d8917d8fb ap-south-1 region: ami-0e74c2b98d730343c eu-west-3 region: ami-04fdf60792918c090 eu-west-2 region: ami-01be6f12a4e591114 eu-south-1 region: ami-0ba9a90dd98c1969b eu-west-1 region: ami-079adc2700379a1d1 ap-northeast-3 region: ami-0761cd0c639b03110 ap-northeast-2 region: ami-0cb94263bd6197e12 me-south-1 region: ami-0bc9f87632bece6bf ap-northeast-1 region: ami-05d427cd27dbcf07a sa-east-1 region: ami-021df0ed72eb03e7f ca-central-1 region: ami-04256dde3f8311c5e ap-east-1 region: ami-00a8323acfe870fe0 ap-southeast-1 region: ami-03a8c238c7244735f ap-southeast-2 region: ami-0e1596ddd79df0a10 eu-central-1 region: ami-02f6ffa749afb395c us-east-1 region: ami-095d5102d288197f3 us-east-2 region: ami-01b2bbcb153589b40 us-west-1 region: ami-01d596be82cbb9b27 us-west-2 region: ami-00cc992baab13fc46 These AMI IDs can be retrieved from the Systems Manager Parameter Store in each region using the keys: /aws/service/freebsd/amd64/base/ufs/12.3/BETA2 FreeBSD/aarch64 EC2 AMIs are available in the following regions: af-south-1 region: ami-0db50a53f15e9902b eu-north-1 region: ami-0413d10427fe88127 ap-south-1 region: ami-09ad53f96f56994c2 eu-west-3 region: ami-08897f38e3d6fb380 eu-west-2 region: ami-02d1e2e28ed1f28c4 eu-south-1 region: ami-0d838b338efcf104c eu-west-1 region: ami-09bc1c176a30922f8 ap-northeast-3 region: ami-0ecf1374e8750796f ap-northeast-2 region: ami-05db57ad14b5868a5 me-south-1 region: ami-018cde3f9d96590dd ap-northeast-1 region: ami-01ded5df514820f25 sa-east-1 region: ami-0bc216bdb785ee86a ca-central-1 region: ami-0f8a0b276eb0921f4 ap-east-1 region: ami-05ad39a06870d63fd ap-southeast-1 region: ami-022c6c66c3fc09197 ap-southeast-2 region: ami-0c291ac7972dc1fe3 eu-central-1 region: ami-06166e9facb402ae9 us-east-1 region: ami-097936468ed6f98c4 us-east-2 region: ami-0a7470112814e4698 us-west-1 region: ami-055ea5574f8d1ad8c us-west-2 region: ami-08a5ce4093064b8ff These AMI IDs can be retrieved from the Systems Manager Parameter Store in each region using the keys: /aws/service/freebsd/arm64/base/ufs/12.3/BETA2 === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can be installed by running: % vagrant init freebsd/FreeBSD-12.3-BETA2 % vagrant up === Upgrading === The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r 12.3-BETA2 During this process, freebsd-update(8) may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install It is recommended to rebuild and install all applications if possible, especially if upgrading from an earlier FreeBSD release, for example, FreeBSD 11.x. Alternatively, the user can install misc/compat11x and other compatibility libraries, afterwards the system must be rebooted into the new userland: # shutdown -r now Finally, after rebooting, freebsd-update needs to be run again to remove stale files: # freebsd-update install == ISO CHECKSUMS == o 12.3-BETA2 amd64 GENERIC: SHA512 (FreeBSD-12.3-BETA2-amd64-bootonly.iso) = f1bd314fdd764793b7c08758e971740269a97495120052e44c2b942a7edd1c08c07ca79228c9cd236b2e57c08c81c8576862031ace26a9e9001e164a2476ede7 SHA512 (FreeBSD-12.3-BETA2-amd64-bootonly.iso.xz) = b97c6c424fb2d58ef4f1e855c89d00d3219a02b5d4c1e41fbd8595e9dfa8c550d288289c082096b3d1d1628ce1f35a116449e8667c3bc1b06c238209dc589537 SHA512 (FreeBSD-12.3-BETA2-amd64-disc1.iso) = 2a846ab27c1dc643ea10f78c25fa15c5131839c291082bd232120f71a3d6ac69c659b9c9df294caa7d150f7a1aba9f73e65ebf47be1f1f66b69b0871f1d835a3 SHA512 (FreeBSD-12.3-BETA2-amd64-disc1.iso.xz) = c9510783f583c4b45615bae4cdb63849fef09df8d0cfb629fce5a63aa86f6a6ad84ce822b3ea1936b3a01a79fdc18cd66536bb458f7edf554da1890befc61bd0 SHA512 (FreeBSD-12.3-BETA2-amd64-dvd1.iso) = ed16bc083290428ebec0176829eb4943ea8048be2960f633005f67f79116f09cdc44ddb7355dab3065753c123fdc3c952ffb3b265c9f9a799b33d67f37dfac5c SHA512 (FreeBSD-12.3-BETA2-amd64-dvd1.iso.xz) = 898e88b17050cbd120152518b63fc79cad41d90101b0fd99973ccf21d050c6b7b1f791b1c1bb655b8b2fb367f326b494f60ec17333b5c6981afa1b162e15954d SHA512 (FreeBSD-12.3-BETA2-amd64-memstick.img) = 5d8c495d086f5297a59241da2167babd2231cae14f9bd6cd00f78e54f62e42a30875aa973428c1b3f79ca27113b5d64554fc4144ae88f339496465cdbca4128c SHA512 (FreeBSD-12.3-BETA2-amd64-memstick.img.xz) = f83b116e62da3f6cd20e02e5b46a670fce3d0cd2fc3cab80c80ab8adab4e9942b25572166d2e1836962f4066887fd825a8f318329a88fef94e2e376f62bffd16 SHA512 (FreeBSD-12.3-BETA2-amd64-mini-memstick.img) = 51f386cfc07a28ec59ee6a9c1b63b199772741ac00dce14f49a34866a4a338ecab7f3fe64f90d59f84779e649ac0a713cf1ff6bec53000925e96db7486f76795 SHA512 (FreeBSD-12.3-BETA2-amd64-mini-memstick.img.xz) = 8a04f14d103f7cf84114b0f62e5b70c0798f93020c4c58b3bea74bfe3ce38cb643d920e5032720bc8eb5cfb2c6e622176d695378562771601eec9248e878df85 SHA256 (FreeBSD-12.3-BETA2-amd64-bootonly.iso) = 972d68bbf05660d8864993a105fbb497bd090f4f47236270f39c1a98d2a43063 SHA256 (FreeBSD-12.3-BETA2-amd64-bootonly.iso.xz) = 462f1d7967b98cce45e24b2e880d1cd8f124620addec28d427b1608acf7fdcab SHA256 (FreeBSD-12.3-BETA2-amd64-disc1.iso) = 0dca65e7f7ef3fa7894b297a50c0bf78c8243dee523cfa2123132cf1ce747dee SHA256 (FreeBSD-12.3-BETA2-amd64-disc1.iso.xz) = 7e4f4f133fe1b80540898cbfaac5af8ab270be96d413f16fa1949e3167d3bc11 SHA256 (FreeBSD-12.3-BETA2-amd64-dvd1.iso) = bf74a8d150b5f0e7552f91b4b765a1873a21eed530837dd9f798b58d1cb33100 SHA256 (FreeBSD-12.3-BETA2-amd64-dvd1.iso.xz) = 4ea8478357cc6545dbab79cdc4727138434183db505af7b0a5479079e9051fee SHA256 (FreeBSD-12.3-BETA2-amd64-memstick.img) = 5369bb099332bc7cc4af959da5dd8420f5138cc008cf543ad990f7d91bd168b6 SHA256 (FreeBSD-12.3-BETA2-amd64-memstick.img.xz) = 29ec955e6f2dcffed299689240fc20b1b806c92ffc73d8184f7bf4fbf9455de2 SHA256 (FreeBSD-12.3-BETA2-amd64-mini-memstick.img) = 69887607c84c44e9ea7de66edbacbb6b6d7df69ffdcdebfed824d28a7db17226 SHA256 (FreeBSD-12.3-BETA2-amd64-mini-memstick.img.xz) = 7ee629417c96366a10738e090f09b275bed0767b08162c90713f2c16759e8fd0 o 12.3-BETA2 i386 GENERIC: SHA512 (FreeBSD-12.3-BETA2-i386-bootonly.iso) = 19f70141bc9db7b45579e4ee084a70031442cef4bb4c87ba01f9ba1cf7cd6b009020bb3675ecd09b1ac9a75ccb6a51a1e7173874386c40592f6311a9f0011e0a SHA512 (FreeBSD-12.3-BETA2-i386-bootonly.iso.xz) = 6b33230947686caeb3a2be795c9c5bedd5a578c535441fe80196c32277e204f39675a646f9a648bff20f7e918abdd6397728139a67419314bdaaca0c0579accd SHA512 (FreeBSD-12.3-BETA2-i386-disc1.iso) = f9f633e9ae8efa57b3e52eb09aef19dc8e551380c0ebfc76d06d021561ae560f1ee39988771cb225d7292031ffb4b78bc0fc2fda938c98014ab27caff366b2c4 SHA512 (FreeBSD-12.3-BETA2-i386-disc1.iso.xz) = 225acddac0b2b82e406292f265dd3810009eef945709e73144a87fcaa85420121a86ef86b7bb6a9364d4675a0d5c0026932c9ec2b437c939742fce74fc217462 SHA512 (FreeBSD-12.3-BETA2-i386-dvd1.iso) = 92788b2dc662f07284728baff238810a612cee3636e6ec83f64544fdcd07b8b09826065b7198ab28abb80b64d36f35dc47e10bc7795fa30703ecc7105f6582c9 SHA512 (FreeBSD-12.3-BETA2-i386-dvd1.iso.xz) = cd1ac5a1b8c246f20883febbfd2403d9d089b6fa3de2e6c2fe9f7c5a3dab0aca5b35abe78a7942aebfd19824bb935a5fe2d0413d848c66d99e88f63fa0266d01 SHA512 (FreeBSD-12.3-BETA2-i386-memstick.img) = f91b61f975bbb9dcf6270bede4e421de4a4fa0f1bf454e2aa7662c31861f93e4ab38406e447f7302d7daedebcadfb19dc59ee6a044f3798863e8fbc1e070ade2 SHA512 (FreeBSD-12.3-BETA2-i386-memstick.img.xz) = 148f1fdc541e128e5da25199c2489eb6858bf74f3a15300629f205c722af2665845186e4510079107a49ab1dc6c0b1c803e4fa38769578560d8aabcd6693eaa2 SHA512 (FreeBSD-12.3-BETA2-i386-mini-memstick.img) = 8f6d95c171ebaf55b215f44b5ca5d8a87a15b3d23dd5828aa18727756e88a9819ccd33f69717ac5d49cdfc860393a2a929a00e11fbbd43f7ce65dcd8b7278d55 SHA512 (FreeBSD-12.3-BETA2-i386-mini-memstick.img.xz) = 0648317a31d6974b41604f3caf9e881bfcaa329de3e558f1a7b1b78fa0e4c3436c4c99e112e3f4ffd9a813fe393aea09005a1617e736587fd21c5c4352bd47c0 SHA256 (FreeBSD-12.3-BETA2-i386-bootonly.iso) = 90673d91f6a82aa3c06853a78bb3e8120bfe8f29046135fb49f1ec8106220b2c SHA256 (FreeBSD-12.3-BETA2-i386-bootonly.iso.xz) = d739574dba91fbb00eb3b73714966caa1ddc1dce828ba8f19d6861d38e1ee83a SHA256 (FreeBSD-12.3-BETA2-i386-disc1.iso) = e64a5cd7c024cff8c901e1f1d6cb7927259ce44375dca02563605120c50e9f86 SHA256 (FreeBSD-12.3-BETA2-i386-disc1.iso.xz) = 554271708bc916d2886f098fbd00fbe28241313b3291993ea9730aa8f8d3fcfa SHA256 (FreeBSD-12.3-BETA2-i386-dvd1.iso) = 6e2444d624c94d15486a54d70e967d54f9b157d12bafa5356c3f1811a0a1bc50 SHA256 (FreeBSD-12.3-BETA2-i386-dvd1.iso.xz) = 8a99f183e6b47a7a7510bf3eb25ddcb1ae73e65805ea244e2fec2e6442c0e7c0 SHA256 (FreeBSD-12.3-BETA2-i386-memstick.img) = cc780d0a896befd35ee136b1333b86da0fb8abef37fdfd3121f203147b0ecc57 SHA256 (FreeBSD-12.3-BETA2-i386-memstick.img.xz) = f5ec9acd6b0672bf82739b05949177f365cbc8d254411642a560f5e2491cd595 SHA256 (FreeBSD-12.3-BETA2-i386-mini-memstick.img) = 59835a7513bfa4bcb408708f2147599f1bc1807e26ca40c519f29204d0fcaced SHA256 (FreeBSD-12.3-BETA2-i386-mini-memstick.img.xz) = 9b5bd65069e75b6ef3d43d2a010daa6cc8d43ec67d464aa5b6ed512207ac7875 o 12.3-BETA2 powerpc GENERIC: SHA512 (FreeBSD-12.3-BETA2-powerpc-bootonly.iso) = 0c5dc2408a9a47151e1ace1f532c4c49754e1cc94a3e5c54e58a8afb501494cb7b60576f559243cbc8a7fd91818f9a44a583f419bc2d74f4ee5ccd1c4f5ec4ad SHA512 (FreeBSD-12.3-BETA2-powerpc-bootonly.iso.xz) = 113023cc2b6e38e6246004a074217f2463cc3d9bdf4b6c00b6f920edb1dd5de1772753a28e816c238b606d12b6b945aeab03c735784e56548c5673bd155a3b9a SHA512 (FreeBSD-12.3-BETA2-powerpc-disc1.iso) = cc0013d5742253c2fd95b55331aa68f28b396c387737074a1e23c0ac19434329c08b7e60b85a12552d9c32ca12a1ce342aa239648a5f03bda75da7d14df58a3f SHA512 (FreeBSD-12.3-BETA2-powerpc-disc1.iso.xz) = c63a0196a38f74a814b57c5ee8e5aa50db100a457ee7e818d08fbecaa0fb4663ec661dce6fe6ca6fa11907035b7a388ae3f7fd0557dcceff991b6725c125f1fe SHA512 (FreeBSD-12.3-BETA2-powerpc-dvd1.iso) = 3205b47ec052044423fb446dcd382f44cdf6f2e2eaf4b7e77e9609aa7d147066a95e0790c91cf22665562177fc0efc5af052899f4f0a28ffa6e6ea8d670c5c47 SHA512 (FreeBSD-12.3-BETA2-powerpc-dvd1.iso.xz) = 00c9a33808bec142bdbef52874d5a4d0cae55113c6b61e95c83495aff36d775def58583c69104114ef617e425c12b3001286f4f717f1f33da6e11da3dc5c4607 SHA512 (FreeBSD-12.3-BETA2-powerpc-memstick.img) = 1510acf78cbf20ee98798202370c9d26b6f34c1a0bc79ec09146289ed05ab1c29a1f24c276df2b0da8ffb96a830d30e0d5eb33073ea6a605f62f1ae3b996c156 SHA512 (FreeBSD-12.3-BETA2-powerpc-memstick.img.xz) = 5fd999bd33fcb38198cbe9e39618646f8006a21f5ba693a29a824774a183b33921022cdf2e8582cde3f4df137584ace701105b62c518f80ae50b25f74f27cb10 SHA512 (FreeBSD-12.3-BETA2-powerpc-mini-memstick.img) = 9dc56f0d545191b5e1ab554588dcb271bafe2e9fca0cf4912a9a0b53475949806d006f5f39b347c1760e5bfdc7b48eed918da0d798c4c9e9bc44eb7fa6924c7d SHA512 (FreeBSD-12.3-BETA2-powerpc-mini-memstick.img.xz) = a610f4f568c35ecfbaac4154ff62aa5df6e01e053911e21be453ff724bb6bf2a626c49f7252a2fb6e516fe79636bfcbe236e7602682c22de338c6ed334a8aaf0 SHA256 (FreeBSD-12.3-BETA2-powerpc-bootonly.iso) = c22d038e2a87b87221d9dabee53f869f653f394c0f479745eba93bce48e52f79 SHA256 (FreeBSD-12.3-BETA2-powerpc-bootonly.iso.xz) = c09ca5a2a4f5038120ddaae051bdb1bc6c3fc960ba42d31b1958df9fefd86113 SHA256 (FreeBSD-12.3-BETA2-powerpc-disc1.iso) = 0099dfc1a973d1b8510c2316acdfb25c96436bdf6c4f95c5aa024c71b6ef1c93 SHA256 (FreeBSD-12.3-BETA2-powerpc-disc1.iso.xz) = 176ed4a8940fe81d18fc992a63f00de6c47eb380a8ea9361314727b2c2e091d8 SHA256 (FreeBSD-12.3-BETA2-powerpc-dvd1.iso) = ca06e806fc9587bb7ddfabb99c13e41395d90f4b1cc3413f3675784b1f165acc SHA256 (FreeBSD-12.3-BETA2-powerpc-dvd1.iso.xz) = 24a076a15b364956dea35469c15e16227127908daec7e0f0b4737089d3c0c0c3 SHA256 (FreeBSD-12.3-BETA2-powerpc-memstick.img) = 4c272df8d56413f5cedeb64af742445361e5d7fe17f0d32f3f08c1d28dd1679a SHA256 (FreeBSD-12.3-BETA2-powerpc-memstick.img.xz) = 9148119d809b73cad2fb2d6dc738988bfa9b719007127cdc28888e3c08fde845 SHA256 (FreeBSD-12.3-BETA2-powerpc-mini-memstick.img) = 7293ea4e50f39df9a89cca7ff96a37200ffbf07f8fa98cdf1608a8ba38ed715e SHA256 (FreeBSD-12.3-BETA2-powerpc-mini-memstick.img.xz) = e514335f03301535e5521234efb9e1a2c4c7ee0558bcc2d6640127b61aea7a84 o 12.3-BETA2 powerpc64 GENERIC64: SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpc64-bootonly.iso) = f8e537d9cc26d12c5eb9eeeff6e73ddf87e40e91b2e7ac02395a85c3507ea438f2c67f9f8883f478086d9303be49ceca657d382bcf03ac41f6a0f1fa21c83072 SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpc64-bootonly.iso.xz) = 8ba9234c2b596e02df9a9d8b108b6cb287fa372d8be6f9255bda1c4006d52d52cdac5b44bb9eaa5eb7fc4510eb765d259924f29790139b4420330059a579fcaa SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpc64-disc1.iso) = a7c4befa688d0fca6edf262f429f83cbcadc1d0f39defde10d19fd92a756d701c1b8ed80ddd607c3ff72444ef89933b7af420221e51f846a8902f8b95f79adbc SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpc64-disc1.iso.xz) = 15e237ea5c8e7fcf68ee0c87642a6fba31f54e227594efb763128669c7880da38eee95e70c84e778dfc266d933274496e5f0fc782809c68ece5a570270629aa2 SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpc64-dvd1.iso) = f51f6cbe44aa48d6cfe2e5ad89b7478294d68e59e297a1af3cdfbfdbccbfbbf8b9cb10764272cea70d6eb835045cc2ff8c397875ba7ce75735309f708a664d29 SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpc64-dvd1.iso.xz) = df4139bdcba5c02ad69bd8e9900bd5d1a5af23a28d7f58922ef6599173664f3c30d2a6a6ec6091d7d6a36c33a97a9024d991d95207c8c61e6897f459cbbe7f9c SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpc64-memstick.img) = 698316bb86108ed1d8388550a71bedf0da2e437f2aa05a0081c551f888631f8da35515d02c8ed6bc69890753a34e82523184de2f9778b23b0b0fd4a378628842 SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpc64-memstick.img.xz) = 11d49369e87566efc3b7f6f63a9168519d367fab05c164edc14f26d5f1a72074c229732b96e14860e85d9f5ce223de12f76f95b282ae7b0c2678bd293b4af721 SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpc64-mini-memstick.img) = b0d5f98a3c2b0ccd3df07cc2c89dc680a95048b3a9e0747e5283a89bf8b432dfdd98bdd08a1ff39cf2c5eaa4760626738cfc0f463549063685a4aedb410329ac SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpc64-mini-memstick.img.xz) = 475268cb692b4d6f8e972e5447fdbc63078e7030b925ab5937aad931a006a75375565f7757bc0b522a0b2c18c0979d2f9684729bae64bfd32ec2fd9fa9edd565 SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpc64-bootonly.iso) = e01c4d1c2ff52cbce0f650315a166a76426d225aef7045514c6bc40d355f1386 SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpc64-bootonly.iso.xz) = 2226812158d7553a92ed44c7fdb783440a035083cd3c522aebce23e9a275098f SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpc64-disc1.iso) = 93022851da96bb7e92f6acd8732d8fd62ac41d77f1a76bab528363dc5c76d776 SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpc64-disc1.iso.xz) = 0359ce79a12a3e1b23db66cc7135412eaf7b785b0eb5db6e0610a61c2cfdff58 SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpc64-dvd1.iso) = 71e715a1ecc2b766d7e745e87e565e6dddeaf4fb6a76c04d688d0789163d2aed SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpc64-dvd1.iso.xz) = 2daf83379683601ad01bb2ff1ad428ad8719877c41c1621aed6228a6aa46e42d SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpc64-memstick.img) = ede9ddb3348ae904a6d7b29f077aa836ee8723355c67818f5061e18a4fe292c8 SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpc64-memstick.img.xz) = b25eacc2f172e98b2185a6b1c7aa2a79783b701473022c38b3c3424b6aadda7f SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpc64-mini-memstick.img) = f92592b1e689286273bc945999e4f0a9f7b1fc9e6da89d9269885c42b0e738fd SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpc64-mini-memstick.img.xz) = 63e0942a8404da74e0e372f912df04cd53118e14e43e973a7fc989400bb9031b o 12.3-BETA2 powerpcspe MPC85XXSPE: SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-bootonly.iso) = d790def55aef89cc5b7b90d2588a8f5fdd84403e69a2a9b5cbc38ff17ccadc8fd5b7b2dfee58ada435cca0bc27ff7b46932bdb4c27f26ad19a1a71886329304c SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-bootonly.iso.xz) = fc762a9dd6527700282149123a72fbb2d17009c87eab569bf713841c3dc0e6798aa4799442ad7e79c96a005d7a6cc44c18c0067b837c7c435ddab57e9c87a370 SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-disc1.iso) = 78ec6e5e5ca5d5751d54d1cdd19f19d92ce8b5594ccf8a3ef41f8146eb5230c37f1271e7591acd160541c58ebbee98a6631351c0cbceb89eec98b2fad89eaf5b SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-disc1.iso.xz) = 4dcfbc44cb2821447616e12413d86d295ac161c897f6b1b0a134437077ae205d8d982356602ae6071366b2964d6f196d05d803fcd7a00943faf3b587abc20654 SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-dvd1.iso) = 7c9a1672c520677a0923328ab1e7ceb80f5d912076787df329e1532eed3b00bf38b6b643bb940e145ccd999453196aa72bb1d4fa19adf75bba3ad596d0c86a1e SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-dvd1.iso.xz) = 4c77247c46a7e8d9c39f15a176a950ac4c2664b3103a4941cdd12eb3f066e607c4559058e63339b686adad28bddee61bf4d1f6f5d8ed5557285d3f09ddec5f79 SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-memstick.img) = 23da4d7c43145fc91809f623f37fa77eae50148aa7df914c290428bb39db15977e5d20e8d0eecebda9e9c0e87d6c6657ce5dfc8204c40d70c1a4623b4df90819 SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-memstick.img.xz) = 8cf43a4502d8b18d2168623c46841709d84c12f4152c87d706189ccd8c0c8f4810430f3af39ea11c5ecceed59a4e60065dd450bcf6499309fee7370c412a6570 SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-mini-memstick.img) = e557a24154b6aac37dc97cefd5aeec919aab375e9d049f82152b8c6769696fc1db0198b28c00aa57b5a4e9dd9e4583f141ecba9b633030a8e802c3e76ad7d4b9 SHA512 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-mini-memstick.img.xz) = d3bb6b173fbc58d79fd19271852858cab6f5ecc9c4a844bca13230571265fe6e6e7d0778acf6adcd7e9dfb7bd8cbc4e0104cb2d17312dd6263a8771cee9a3557 SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-bootonly.iso) = 5133d05699f2692a086a47ad9ab75b967ba6e5ba2726dfb8bfee4fab86265faf SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-bootonly.iso.xz) = 2d0c1676e153cf1e79d89d039704a2ac6ce620b7f6e1bbf84b56353b9b1f4286 SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-disc1.iso) = 47366edfb4f0c5845ae99f0466451399362b55ba8a20ecc2dd6ee7579a7129f3 SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-disc1.iso.xz) = bde9275c5a5ffe5544a9a92ea11a142c0197e2e3bd3985a56c32763acd1c19e2 SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-dvd1.iso) = c039f8b11d237ab4caa1e01cfed603d3d12eaea98f03207138b9e15ce28a64a0 SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-dvd1.iso.xz) = a46bee0b375a34ad995dddc76f90066ce1350202e5c80f983556a734d2589147 SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-memstick.img) = 0076578738ddfdaf9be5b4d66ef6206090b11a5bb0b51777babf3be62fc371b4 SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-memstick.img.xz) = 9c4785b9a445d8d4e0c1381acfc0f100c846a89599fd34af53d03de8bb244de1 SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-mini-memstick.img) = d35fa2eeb490567a06f5366750cf51c4368894aab5f15de099d1baf15ba0c94a SHA256 (FreeBSD-12.3-BETA2-powerpc-powerpcspe-mini-memstick.img.xz) = 27bc828413d7015ca0bb55935bda8e09eb26213c3f768d918533c721e490dad2 o 12.3-BETA2 sparc64 GENERIC: SHA512 (FreeBSD-12.3-BETA2-sparc64-bootonly.iso) = ef94c7186233dffc0d026e1ff40546ca171de65115b77e83b481f1d99d9679ac8453d9f369956318367037d6d7ce740bd1625d70e3cb52526bf291b4a7cd542c SHA512 (FreeBSD-12.3-BETA2-sparc64-bootonly.iso.xz) = f388d02c82beb045b2af5de8ac8e563fd004f6ee360dcc4f6af8229b4715bafe9c58647d9bef191459ed75101291bce7fa0b349588408b6467363210fe266c54 SHA512 (FreeBSD-12.3-BETA2-sparc64-disc1.iso) = 5ce03e063b6f7f08e6ffae352b6cfc22238a18ceb44f21e133137b51b4a837d5b38beb6868736f9fb62ee9627db6f75c879bdf638ccde0c3d8b219b7f543d45c SHA512 (FreeBSD-12.3-BETA2-sparc64-disc1.iso.xz) = 087b7cc711e342e3574bfe81ff15485b03cce16729b670b5a8e7a5aeb4a6eb366f444b1b7c595ff27335bc6a0ca2558115d6f9eea5795d012fba8fd4a8fed7e5 SHA512 (FreeBSD-12.3-BETA2-sparc64-dvd1.iso) = 4ac1103aca10e1f8c4d57097f940d29850024a6f72b86ac809e0db280e024e7620bc3b043469f16fc33ad8a7e6edc22b773326ce111cd8e2f70f9ff04a62222b SHA512 (FreeBSD-12.3-BETA2-sparc64-dvd1.iso.xz) = 4b2aef98e749390ccdfcfb5afef7aee5be7aa66c49c5e591ded2c71f288efd8c23e47dd11d1f00f2ad19c164531875824f4fbf910893e27e6c420822fcac8012 SHA256 (FreeBSD-12.3-BETA2-sparc64-bootonly.iso) = 9c6fce3da920131c792a9ea8b848628d28ffad86076bd07e49cc04348dd39590 SHA256 (FreeBSD-12.3-BETA2-sparc64-bootonly.iso.xz) = 338c8ace40fc575d48bb97f54d452b155942802b5887f9fe5749107c90693012 SHA256 (FreeBSD-12.3-BETA2-sparc64-disc1.iso) = c251652f67ed888bd28c6cd0416e4cf868ea54c4982666fd4605ee84c5f5a959 SHA256 (FreeBSD-12.3-BETA2-sparc64-disc1.iso.xz) = 68678684556a83bb9ecf628bb2d3f1e1249f5f125bb6758f6cae921d3d9a8898 SHA256 (FreeBSD-12.3-BETA2-sparc64-dvd1.iso) = c21305fcff7b3c8d54961393696f57ef77c54bb6a1508aa7a4f597a7405ef86a SHA256 (FreeBSD-12.3-BETA2-sparc64-dvd1.iso.xz) = 0b8191a467afde321e8c639c11aac792ae7948e50354f9db8f9feb79f8e84059 o 12.3-BETA2 armv6 RPI-B: SHA512 (FreeBSD-12.3-BETA2-arm-armv6-RPI-B.img.xz) = 291c1cc570b719e05690ea16ef9864978b581018a106689fb7da55429548d427d288a30159ab7a01fb25d16e9ab5432956428a5623aaa1dd2f57cc3110f91e2d SHA256 (FreeBSD-12.3-BETA2-arm-armv6-RPI-B.img.xz) = d87658246827205b1de0d014114385a23b632fcf8a10e9256613b44e05ed1893 o 12.3-BETA2 armv7 BANANAPI: SHA512 (FreeBSD-12.3-BETA2-arm-armv7-BANANAPI.img.xz) = d4bf1bef014ffb96d7170ed862186fd5d0a8f641ed9d9ef58e1c74ffc2c274d1161d45782753e0dc0973998bd8bec5cd47a8b58b493d3afe9d12fc756716e2e3 SHA256 (FreeBSD-12.3-BETA2-arm-armv7-BANANAPI.img.xz) = fc16962b1b8cdd715fd91c2c85ddae2de9cb7fccdaab3a502dae9a895039f02d o 12.3-BETA2 armv7 BEAGLEBONE: SHA512 (FreeBSD-12.3-BETA2-arm-armv7-BEAGLEBONE.img.xz) = dd9ceb6fe9edc55f4b358c3ede5c33aa5cb7ff5f6dc8b88cf9521d9e43ad5a90b84cb8bbdf6829c129b2c121e11ce7e1c3431541c32c702d75fd1eca8539b6c6 SHA256 (FreeBSD-12.3-BETA2-arm-armv7-BEAGLEBONE.img.xz) = 0b25f67395f6baf33269716188f449ad60cdb2fe8776de1684922e4020cc9586 o 12.3-BETA2 armv7 CUBIEBOARD: SHA512 (FreeBSD-12.3-BETA2-arm-armv7-CUBIEBOARD.img.xz) = f56bc20fded4839b48a46efc04a23d7a975787f09f746547ff6d1c976826d37fc8e6024dfad714be4ddd90025479f39bb32d2ba6ff15ed1cf19eece2c67fe49c SHA256 (FreeBSD-12.3-BETA2-arm-armv7-CUBIEBOARD.img.xz) = f0f7932f4cefc502fe03115e6bee86b5d61f147237fd6980af65e4f36a5a93e1 o 12.3-BETA2 armv7 CUBIEBOARD2: SHA512 (FreeBSD-12.3-BETA2-arm-armv7-CUBIEBOARD2.img.xz) = 6beb3c0bb339e4a943be4dcebd41fc0395ee3e7c0a280d306f34a0cf16460ef05d6f614a93588c238ea0c9b2588948ff31b24fac67259343fc6137b023e11580 SHA256 (FreeBSD-12.3-BETA2-arm-armv7-CUBIEBOARD2.img.xz) = b835f7d5f67e38df92f38d25b41042b5a38b22c135a2fd231816474079d5b31e o 12.3-BETA2 armv7 CUBOX-HUMMINGBOARD: SHA512 (FreeBSD-12.3-BETA2-arm-armv7-CUBOX-HUMMINGBOARD.img.xz) = 8144d750d8ba18e3ddfe268fa41a0694803aa9e7a48420596c17dde62ee510468401790c88a1ba976758bb7f55925fa079e309415948b74be5c007da9feff72a SHA256 (FreeBSD-12.3-BETA2-arm-armv7-CUBOX-HUMMINGBOARD.img.xz) = df0ba88588a4f5a57d1a668342da9463901e09e04c81ed85765af679aa05a5af o 12.3-BETA2 armv7 RPI2: SHA512 (FreeBSD-12.3-BETA2-arm-armv7-RPI2.img.xz) = 5a19e85c5d504b25afa2f4ce5152cf52e92dd9b51407c6c64815887419e7f622bd76058c31bc0a9b222925505e1a5c58f6fa2911f46264cfc7271b6118100d9c SHA256 (FreeBSD-12.3-BETA2-arm-armv7-RPI2.img.xz) = 14e07a182899ec7fd5091d3708fb556de225ad73860656811d13516ebc52ece9 o 12.3-BETA2 armv7 WANDBOARD: SHA512 (FreeBSD-12.3-BETA2-arm-armv7-WANDBOARD.img.xz) = 95aefa59d4579f0c4841896196e5671d3bcc0aba4649fc71cae0ca53652bcdafe12b3e3fe218d1a82ced49954b32e0f56ccaf9596fefec565b5de5176124c98c SHA256 (FreeBSD-12.3-BETA2-arm-armv7-WANDBOARD.img.xz) = 463685b06ddd3ed3af98924b1f5faffb0d3167374464adbada0f5501eab0faad o 12.3-BETA2 armv7 GENERICSD: SHA512 (FreeBSD-12.3-BETA2-arm-armv7-GENERICSD.img.xz) = 0cb0d80c79ac914eba3c94298149876ce20b129a10f2a85e6d8f8a7715fc81aa1f69f652ab0b90bac348ee3127a10cc4b73528819ec926cce54677e7b7c86de6 SHA256 (FreeBSD-12.3-BETA2-arm-armv7-GENERICSD.img.xz) = 0ccf0f327d2582d4bdd7a850af4ee11d0810d36c790b58a47c93db97f49baca2 o 12.3-BETA2 aarch64 GENERIC: SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64-bootonly.iso) = 46293334718dd195bb0ef75bbd0113cf1482810053cb25157b1bc036e6272888ef2f38293bd205b53d065f92c2c0c0077d8a08704899229483f4469beeaa40ad SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64-bootonly.iso.xz) = 690800f479f493264f7f739bd793cbd13134bb445c3065fe53354be584afb4af9bb740b2e9614b1c0895c1d304125804a22fb9de3e1f76ef4981c253d9f76586 SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64-disc1.iso) = 66c426ebcc29a32a01e0f727167cf6ddc4ed2b12540710d165567cba2bf8bf8b90e47f0b8d1feccac6de1a27e9526007f9bea0325e74cbba196eb83ef4d35437 SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64-disc1.iso.xz) = 42c1b3179ba6c0c4fe0be5e1f12c15aef64f81fb761e31d2ffb32eec2fd395af2c45e46dad0ccf89358e3ec97459053305ee9a026d9a55e086b6fb3bd0694d10 SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64-dvd1.iso) = 78e739e0de35f4d1c06ad3f23de4a1576f61b6a799eca374133cca56db597fd0aacdf8e9bdc3b7a8bd7cb681c1254fabb23f7cea594085f80920ed82e45978dc SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64-dvd1.iso.xz) = fac5ae00be55064ae9049eafba1af8ab9112940992abe210c06e25d9eccef3cbc63922b636ff3c697b892d19f50474fd07a9ca89dd93c69785adac562a173a65 SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64-memstick.img) = 54fcb0fc925ce44272b4e7d750b30634a7b3b4a6ee0fa976068d2d715d00cc203426097394815196bc2c5792d74ff7914f009ae76062a995d79a5c5f8bc6e10b SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64-memstick.img.xz) = 9a5ba420f04b605948f356782f266cd3fdcb62908646a100189103bcfd07b71c4e4aa4b17a84db069361b4749c60fab63f236d82d213973c19dc27a2ccf5346d SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64-mini-memstick.img) = 79a7591b8ac02949d3f0c7083ef083c5cee0e5b7b8726b18cad6c8be4220dd4bdf4ef69ffe9293a026ebc4f7a424006f6800f0da796f21928a820f0ed0caacd9 SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64-mini-memstick.img.xz) = dfb8aafc0f722e72c90e476f666b9a7c4b88d86bf3ea071ff933ef6666059e52fd0bb4ef95d2f39eea1ecaa030593194a0ee7eee723cd9bddf766c3288a8fe85 SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64-bootonly.iso) = aed838586f33e95b08a1018353a35e96268c850f32ead2c340c7f826e8a17598 SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64-bootonly.iso.xz) = d7b7931c94dc691fce40436b92362df40840a1ef41e6f9e33815904f2d37a73f SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64-disc1.iso) = 61f381a905c95372b2f5b532aa3fad0cb6f7017dcba3a2b43ac3bb5090ab41f7 SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64-disc1.iso.xz) = ae3ce98f6d98788634982d1f0ca611d4589bd5399b3f1935d39f188b6838bb9b SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64-dvd1.iso) = b30a7383fdd60b0c0315ad7e0ed811e20fd7cac8849908979a8d8f7ab69cb3a1 SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64-dvd1.iso.xz) = 672f401fed529adc383964fb72a6bfc87ff305d99627e171362089bf3f632847 SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64-memstick.img) = 092409ddcaabdb5f850558dfaddf3bd7a48bb335a6c240575bf622e8a4f264c6 SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64-memstick.img.xz) = c3cbaaa39ee40a4788dd29df9707c2746a44f5db82ca498e98ad185bc45cdd91 SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64-mini-memstick.img) = b5313421d56e2219141bb8ad335ae9f61d7e389338c792f51a3cc9147a933886 SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64-mini-memstick.img.xz) = 163920da5f2d784b8ea3c2e7fe929feae76b5bfc761f8348770270614897d972 o 12.3-BETA2 aarch64 RPI3: SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64-RPI3.img.xz) = 1d61461ab4c34f9a667ea53b63f15c11f23627aeee582801b060a76112bee870982a06e783edcf7dee89e0c80c54c6637de84ff0f3b98ae140cd4348a895cf27 SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64-RPI3.img.xz) = c5f373911a837055edcc1445706b940e6cf66df572609a3a05b89d99e55eb468 o 12.3-BETA2 aarch64 PINE64: SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64-PINE64.img.xz) = 2abd6709dc74f7456213c6ac4845383ecc94d82a9cd6aaf271f8a084e68b09d3f04ef08aaa0b796a32b80b8338e448b3132b3d9e6d814acefd544d6396084f29 SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64-PINE64.img.xz) = e270de866d3daf5e62e376ee37b655d3c9c0026591e305e91a27ed7770ea559d o 12.3-BETA2 aarch64 PINE64-LTS: SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64-PINE64-LTS.img.xz) = 0194171dba6d0abe68888192e05c458518ee29997925fc32dc74866d6a6c76d6def97ec50e23420204d5b37f00ed7be8b9134aedd279c379fa638f3ec9b6e73b SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64-PINE64-LTS.img.xz) = b5a970711a11bbc95a4e1aa74191a4ae7a643ff45c9196e26bedc49a6244e0e0 == VM IMAGE CHECKSUMS == o 12.3-BETA2 amd64: SHA512 (FreeBSD-12.3-BETA2-amd64.qcow2.xz) = ca5307c976b544fb43dbafad9cb3c979c5d5ededa7b47e284dde5a85d2045ca4f7d33b45afa7e7a2b4a3c8977f802b8f320d1c84597845178f75cd787126dcb7 SHA512 (FreeBSD-12.3-BETA2-amd64.raw.xz) = 200712f9dee23f5c70a7ca59cfc465ffb63e15dc80cd6769d9cdf50c0369ae3df69b6a4080c2e2af100b3119466e57794a92557a1473fc5108e93b24b9ea2ac8 SHA512 (FreeBSD-12.3-BETA2-amd64.vhd.xz) = 7e7bdf2a9caf265fc31324bb1e8a0052a6e3b464be4aaecb9baa788209169457ae3d9da7ee2c527bcdc10df5d59c30d9d893b1edcf3074c443c26579504c2524 SHA512 (FreeBSD-12.3-BETA2-amd64.vmdk.xz) = 859dce35487e8f64d8de548d9f536d08470b9b786124be798f03d96aeb70781af8f5e4376ca46e99081f06b64185d26965c8549e5835c2fa0d5e0a4f002e5c18 SHA256 (FreeBSD-12.3-BETA2-amd64.qcow2.xz) = 88677bd0d0e6f510c76ab689e89014d88868c63ba80bd8adf7ac55e904b07912 SHA256 (FreeBSD-12.3-BETA2-amd64.raw.xz) = 80ddae516840002a160ae0c075a81d3ecd5c8afab63f178c305f38dba7d65d38 SHA256 (FreeBSD-12.3-BETA2-amd64.vhd.xz) = 3dfb0c7f7fcf5b5ede6c4192e793fd1b020d7083b7075a81253748a4c151ab57 SHA256 (FreeBSD-12.3-BETA2-amd64.vmdk.xz) = 083dd73c6dbcd58bd80eab849b3e17a6691158ffaded688b56207756303d8f26 o 12.3-BETA2 i386: SHA512 (FreeBSD-12.3-BETA2-i386.qcow2.xz) = 54ddad8b7835f3a5de57ab31b133ec8fc180e889e2c7f66259b0c69047318cd97453032382a037b92af024e786b988b87cfc145cc8eab1774275f7b6482ba100 SHA512 (FreeBSD-12.3-BETA2-i386.raw.xz) = 42c235162be11119c40457ff6209c8509e8940471c9c33fa5a2e7d4d2ce271dfbb0622e80708e3417a530802f4a7587c86ff8b892e4a2da701ee0aa18104ecb6 SHA512 (FreeBSD-12.3-BETA2-i386.vhd.xz) = ab41c0448eee73511eba4c08526d6607b40655392fc3ac4841e02d93b1cd3ea4553d0acc07cc6329f78ed592b3b9b390b7f0d85d04663678945152b0dbbc0a4a SHA512 (FreeBSD-12.3-BETA2-i386.vmdk.xz) = 04e78d9312fcc0a520dc0d91ef0877e9d9dcf7eab320f744b79baed96140797bf12fdb35080ae5b525272f1248d0098037ec7c3327d3ac8310e0801de49185af SHA256 (FreeBSD-12.3-BETA2-i386.qcow2.xz) = 5c5a3d7e5da71d7085e3d77e44283d2d98564c44ac113ba181b8dee3dfbe90af SHA256 (FreeBSD-12.3-BETA2-i386.raw.xz) = d462ee593fbc9f923626f8bf244e158931e5992fe867bb2ccdfc478102f0ab76 SHA256 (FreeBSD-12.3-BETA2-i386.vhd.xz) = 3e063b2d705ea23267930c0527a0be9b08657b6deb55e29066ce68251dc9afe4 SHA256 (FreeBSD-12.3-BETA2-i386.vmdk.xz) = 8730dcf4e1a054ad778b46f0c36dc1ed7144688cf1c31c618cf05c35dcab74ec o 12.3-BETA2 aarch64: SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64.qcow2.xz) = ba4b8c89b685746a87e751763bd3b3503f3668c49cecacaef62e05c335dbbf53ab2e4bbc3703bb94cd9aeb5cb85b116086734a615357c9a0af7ec016b3ad2e96 SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64.raw.xz) = 33e2a8bd9783111d70a4f1497f8299671c1feae92b50e6b7e31c222b44bbdd4df9d16e6b7d3d428b7d1ae017ae4265833b0c7c28743fb57fb2b3c00fde19ef2c SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64.vhd.xz) = a0f8cb6b375e10f5c42a47f8868fd08d88ce15b49dde8027827b17e25e4dd0c824159724cfb63b500e95cda0ac4cc5e0c99ec79093a43a5340e48986633c18a1 SHA512 (FreeBSD-12.3-BETA2-arm64-aarch64.vmdk.xz) = 22fcf553efb266245b094c23d80f9c4ccfab064f1fd0915dceb560d01c5420cc67fb0921e83213e40bf1e5293a92c3ba47e12925fc5ed2dbd42c9d0e9ca8c442 SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64.qcow2.xz) = f6f2c6c987c089dbe565d997b1eaa1fff513c3571d2301e84a2197b30860673e SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64.raw.xz) = 884100fe17c94b16029455efff1eeff301031195866a8d0dd5b16cb70625cd73 SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64.vhd.xz) = 76deec59afdfcb26646b68cfaaa68423e83457b3dfa6870d4b976b3d4d0de2c7 SHA256 (FreeBSD-12.3-BETA2-arm64-aarch64.vmdk.xz) = 6e75222a9e0322ec71a64c8a759fa2f2ef92bddb424c5780242131ebbdc9a3cc Regards, Glen Love FreeBSD? Support this and future releases with a donation to the FreeBSD Foundation! https://www.freebsdfoundation.org/donate/ -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAmF8FSYACgkQAxRYpUeP 4pNpJg//f/u/ql52JOC6VEglN5CM++587OVdkhvTCuvg4a3d80n8mK5/+H6azRB9 5Pw5Hdr3F7IWM6v50chqI45yfjFIxrAJSfHFggLirEFJqvqO3/3e1zRXqT6z1/1K Xl1j9RrRkzqyBhfTx90loc8HGpihT152DbpMs70xBQB7Pc0rbGm0hGD0Lr6q4R51 jBFnsfN18jqgnFKUraoxsSFxT4ZaHIZcoTNPE8eIxYqZNose1LnykDIn0DERgHJK ukVqLpJlfhDQpBdt0frsqMTiU0IdyvvUNvfA8HDj/Yzn9WpAWo8CDShi8Va6K8bc 8zm6RQDS4hkrq/rUYpOWRVQd2q1EdwyMpp+Kz6ao2mpilRVwj0lhqoMXb+EiEn0Z 4/ggUcEnweVL+xYaP4s3M7OB7RfCRa0lptzgb59XiFgdxCsSlwcjD2THGgi2kB0z u9WtVA0pq/tiSzOqMsG6jdKdJM3CHXUxo8pAydBfEwcCZjeZTafQYS032mekldVY a3OZwdNlx54HJpmT+R8fxIL2LHpV/dGkP4SXcsfO5OGuD83qVkuknUZ9yD+0C5TQ lAF0FR/Vzj3paWZ+nAqisVgLjs+seCkxyKgfYMhVZHGsr+QHhvn7GmEjr8uKxO2s gVH2vkwgTpiSDlwfVagFWCGLJ3jVDJtUITNlJ74DxeTH0lHG2xU= =oK/m -----END PGP SIGNATURE----- From nobody Fri Oct 29 17:45:38 2021 X-Original-To: freebsd-stable@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 150B51836A90 for ; Fri, 29 Oct 2021 17:45:51 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward501o.mail.yandex.net (forward501o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::611]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HgqbK432sz4mCL for ; Fri, 29 Oct 2021 17:45:49 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from myt6-fd890da583f9.qloud-c.yandex.net (myt6-fd890da583f9.qloud-c.yandex.net [IPv6:2a02:6b8:c12:1d80:0:640:fd89:da5]) by forward501o.mail.yandex.net (Yandex) with ESMTP id 3767545C4D24; Fri, 29 Oct 2021 20:45:40 +0300 (MSK) Received: from myt6-5751e79998e4.qloud-c.yandex.net (2a02:6b8:c12:5224:0:640:5751:e799 [2a02:6b8:c12:5224:0:640:5751:e799]) by myt6-fd890da583f9.qloud-c.yandex.net (mxback/Yandex) with ESMTP id Oxm3oKvQoJ-jdDO8pGa; Fri, 29 Oct 2021 20:45:40 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1635529540; bh=LNxRs0rrpUqBna7SuShLaAQ6BhXnxBkFN4BkKCuqlqQ=; h=In-Reply-To:Subject:From:Date:References:To:Message-ID; b=KqXqVMpwgjQSlck7/rdmtmFu04ka233KWNI5XaUyTy5G4bjG0GQ8Ii1cglWJwp34T 1cDf6NqhydQrXD8o8N+4f9pkHS1Yu0lWGM27JFY9a2fJaSTGrMwZqDlAE7yjmdLnuM ZfYZEe+nGa9pE3Cmu5YfagHS3+/95i0B3fpuQHoc= Received: by myt6-5751e79998e4.qloud-c.yandex.net (smtp/Yandex) with ESMTPS id XT75sDpS0h-jdM49aFl; Fri, 29 Oct 2021 20:45:39 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) X-Yandex-Fwd: 2 To: Peter , freebsd-stable@freebsd.org References: From: "Andrey V. Elsukov" Subject: Re: IPv6 checksum errors with divert Message-ID: Date: Fri, 29 Oct 2021 20:45:38 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6bxKEuoa76hLtpPDMW8S8cO3UMq9uH3da" X-Rspamd-Queue-Id: 4HgqbK432sz4mCL X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yandex.ru header.s=mail header.b=KqXqVMpw; dmarc=pass (policy=none) header.from=yandex.ru; spf=pass (mx1.freebsd.org: domain of bu7cher@yandex.ru designates 2a02:6b8:0:1a2d::611 as permitted sender) smtp.mailfrom=bu7cher@yandex.ru X-Spamd-Result: default: False [-6.10 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[yandex.ru:s=mail]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yandex.ru]; R_SPF_ALLOW(-0.20)[+ip6:2a02:6b8:0:1000::/52]; HAS_ATTACHMENT(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[yandex.ru:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[yandex.ru,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; FREEMAIL_ENVFROM(0.00)[yandex.ru]; ASN(0.00)[asn:208722, ipnet:2a02:6b8::/32, country:FI]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yandex.ru:dkim] X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6bxKEuoa76hLtpPDMW8S8cO3UMq9uH3da Content-Type: multipart/mixed; boundary="7y8znZLzgtABYD1Y5Irv4koqytTVLlQsX"; protected-headers="v1" From: "Andrey V. Elsukov" To: Peter , freebsd-stable@freebsd.org Message-ID: Subject: Re: IPv6 checksum errors with divert References: In-Reply-To: --7y8znZLzgtABYD1Y5Irv4koqytTVLlQsX Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable 27.10.2021 16:28, Peter =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > I see these checksum error when the packet goes into the divert > socket, I see it when the packet comes back from divert, and I > see it when the packet goes out onto the network. > But, when I remove the divert socket from the path, then I still > see the checksum error at the place where the divert would have > happened, but when the packet goes out to the network, the checksums > are okay. Hi, This is usually due to enabled IPv6 checksum offloading on the NIC. When upper level protocols like TCP/UDP/SCTP send a packet, they can leave checksum for delayed calculation. This delayed calculation occurs when IP packet is going to the physical interface. If an interface is unable to offload checksums calculation, IP layer does forced calculation, otherwise it leaves checksum as is. This is why you see corrupted checksums in the tcpdump output on egress interface. It is just not yet calculated by interface. Divert was designed for IPv4 only and it does not properly support another address families. But you can try this patch: https://people.freebsd.org/~ae/ipv6_divert_csum.diff --=20 WBR, Andrey V. Elsukov --7y8znZLzgtABYD1Y5Irv4koqytTVLlQsX-- --6bxKEuoa76hLtpPDMW8S8cO3UMq9uH3da Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAmF8M0MFAwAAAAAACgkQAcXqBBDIoXrm owf/VjLNODZdZpumjInf7+1JvBr7ZDVEeVsmw+UumlFXv8Xmzk57ZqDSZhUeKKJEm2/nCNarKe30 scmxOfKsY83p+PW+GVXYZ2w4UVSXGxQMcHCSzzeFj4AiCfLYsfUMd0UosRcIgA2LpmhtX3EVQlz/ WK8FkP2khIS4MvOwZzFEQf+OHe3HEEeHfG4q0G/6D/98Mk3wwbIA9TImtPf2Mf86CN3EFvVabwUg 3iuUtbz8cIWWvNNLEdAZF0vivFz9hjiAHM6MIqKNDusgODINWCtMxWWGI4FD2gl1OTCLUoY87cLd Md73D8UqRc7/q6u8wPYXjLP+CMcC/jGa3cwftPP8sA== =j/U1 -----END PGP SIGNATURE----- --6bxKEuoa76hLtpPDMW8S8cO3UMq9uH3da-- From nobody Fri Oct 29 18:33:14 2021 X-Original-To: freebsd-stable@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 84F741827DA0 for ; Fri, 29 Oct 2021 18:45:31 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840::12]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "uucp.dinoex.sub.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HgrwC2BnDz3MTH for ; Fri, 29 Oct 2021 18:45:30 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Received: from uucp.dinoex.sub.de (uucp.dinoex.org [185.220.148.12]) by uucp.dinoex.org (8.17.1/8.17.1) with ESMTPS id 19TIj4eH031949 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 29 Oct 2021 20:45:04 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) X-Authentication-Warning: uucp.dinoex.sub.de: Host uucp.dinoex.org [185.220.148.12] claimed to be uucp.dinoex.sub.de Received: (from uucp@localhost) by uucp.dinoex.sub.de (8.17.1/8.17.1/Submit) with UUCP id 19TIj4Ew031945; Fri, 29 Oct 2021 20:45:04 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Received: from gate.intra.daemon.contact (gate-e [192.168.98.2]) by citylink.dinoex.sub.de (8.16.1/8.16.1) with ESMTP id 19TIXGuJ054396; Fri, 29 Oct 2021 20:33:16 +0200 (CEST) (envelope-from peter@gate.intra.daemon.contact) Received: from gate.intra.daemon.contact (gate-e [192.168.98.2]) by gate.intra.daemon.contact (8.16.1/8.16.1) with ESMTPS id 19TIXERW054368 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 29 Oct 2021 20:33:14 +0200 (CEST) (envelope-from peter@gate.intra.daemon.contact) Received: (from peter@localhost) by gate.intra.daemon.contact (8.16.1/8.16.1/Submit) id 19TIXEJx054367; Fri, 29 Oct 2021 20:33:14 +0200 (CEST) (envelope-from peter) Date: Fri, 29 Oct 2021 20:33:14 +0200 From: Peter To: "Andrey V. Elsukov" Cc: freebsd-stable@freebsd.org Subject: Re: IPv6 checksum errors with divert Message-ID: References: List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: X-Milter: Spamilter (Reciever: uucp.dinoex.sub.de; Sender-ip: 185.220.148.12; Sender-helo: uucp.dinoex.sub.de;) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (uucp.dinoex.org [185.220.148.12]); Fri, 29 Oct 2021 20:45:07 +0200 (CEST) X-Rspamd-Queue-Id: 4HgrwC2BnDz3MTH X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N Hi Andrey, On Fri, Oct 29, 2021 at 08:45:38PM +0300, Andrey V. Elsukov wrote: ! 27.10.2021 16:28, Peter =D0=BF=D0=B8=D1=88=D0=B5=D1=82: ! > I see these checksum error when the packet goes into the divert ! > socket, I see it when the packet comes back from divert, and I ! > see it when the packet goes out onto the network. !=20 ! > But, when I remove the divert socket from the path, then I still ! > see the checksum error at the place where the divert would have ! > happened, but when the packet goes out to the network, the checksums ! > are okay. !=20 ! Hi, !=20 ! This is usually due to enabled IPv6 checksum offloading on the NIC. When The nic is 'tun0', and I don't think it ever does hardware checksum offload. ! upper level protocols like TCP/UDP/SCTP send a packet, they can leave ! checksum for delayed calculation. This delayed calculation occurs when ! IP packet is going to the physical interface. Yes, but when a packet goes thru divert(4), the CSUM_DELAY_DATA* flags are lost, and cksum will not be inserted later when transmitting. ! Divert was designed for IPv4 only and it does not properly support ! another address families. Ah, yes, I figured that. But suricata runs on divert, and it runs IPv4 and IPv6. (suricata wants to dump ipfw support, but I don't want that to happen, because it is just cute to be able to wire it arbitrarily into any flow desired.) ! But you can try this patch: ! https://people.freebsd.org/~ae/ipv6_divert_csum.diff Yeah, I came up with mostly the same patch yesterday. ;) And it works! I don't get why this isn't in the code. Divert my not be supposed to support IPv6; but then, that code does already have some "#ifdef INET6", so it does also not really /not/ support it - it is just stuck somewhere in limbo. Cheerio, PMc From nobody Sat Oct 30 23:33:23 2021 X-Original-To: freebsd-stable@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 7F6D21821369 for ; Sat, 30 Oct 2021 23:45:46 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840::12]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "uucp.dinoex.sub.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HhbX93Wdvz4g78 for ; Sat, 30 Oct 2021 23:45:44 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Received: from uucp.dinoex.sub.de (uucp.dinoex.org [185.220.148.12]) by uucp.dinoex.org (8.17.1/8.17.1) with ESMTPS id 19UNj4Tl032356 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 31 Oct 2021 01:45:04 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) X-Authentication-Warning: uucp.dinoex.sub.de: Host uucp.dinoex.org [185.220.148.12] claimed to be uucp.dinoex.sub.de Received: (from uucp@localhost) by uucp.dinoex.sub.de (8.17.1/8.17.1/Submit) with UUCP id 19UNj4SN032354; Sun, 31 Oct 2021 01:45:04 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Received: from gate.intra.daemon.contact (gate-e [192.168.98.2]) by citylink.dinoex.sub.de (8.16.1/8.16.1) with ESMTP id 19UNaHV8025943; Sun, 31 Oct 2021 01:36:17 +0200 (CEST) (envelope-from peter@gate.intra.daemon.contact) Received: from gate.intra.daemon.contact (gate-e [192.168.98.2]) by gate.intra.daemon.contact (8.16.1/8.16.1) with ESMTPS id 19UNXNQE025300 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 31 Oct 2021 01:33:24 +0200 (CEST) (envelope-from peter@gate.intra.daemon.contact) Received: (from peter@localhost) by gate.intra.daemon.contact (8.16.1/8.16.1/Submit) id 19UNXNde025299; Sun, 31 Oct 2021 01:33:23 +0200 (CEST) (envelope-from peter) Date: Sun, 31 Oct 2021 01:33:23 +0200 From: Peter To: freebsd-stable@freebsd.org Cc: bu7cher@yandex.ru Subject: Re: IPv6 checksum errors with divert Message-ID: List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Milter: Spamilter (Reciever: uucp.dinoex.sub.de; Sender-ip: 185.220.148.12; Sender-helo: uucp.dinoex.sub.de;) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (uucp.dinoex.org [185.220.148.12]); Sun, 31 Oct 2021 01:45:07 +0200 (CEST) X-Rspamd-Queue-Id: 4HhbX93Wdvz4g78 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of pmc@citylink.dinoex.sub.org has no SPF policy when checking 2a0b:f840::12) smtp.mailfrom=pmc@citylink.dinoex.sub.org X-Spamd-Result: default: False [0.90 / 15.00]; FAKE_REPLY(1.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; HAS_XAW(0.00)[]; AUTH_NA(1.00)[]; DMARC_NA(0.00)[sub.org]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:205376, ipnet:2a0b:f840::/32, country:DE]; FREEMAIL_CC(0.00)[yandex.ru] X-ThisMailContainsUnwantedMimeParts: N Hi Andrey, hi all, there is at least one further issue with divert (and dummynet) and IPv6: If I put EITHER a divert OR a dummynet pipe/queue into the OUTgoing (layer3) ruleset to the uplink interface, then Youtube is not able to insert their advertisments into playback, and may hang entirly on playback. That seems to not happen due to timing or bandwith issues, but due to the sheer existance of a dummynet (or divert). And if I move the dummynet to the incoming, INTRAnet-facing side of the router, the problem does not appear. So there must still be some other bit in the IPv6 (or in the mbuf?) that gets improperly mangled during divert and also during dummynet. It appears a bit difficult to hunt that one down, due to the sheer amount of traffic involved in YT streaming, and also since I do not know exactly for what to look... Any helpful ideas are welcome. Cheerio, PMc From nobody Sat Oct 30 23:50:34 2021 X-Original-To: stable@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 0EE661822E16 for ; Sat, 30 Oct 2021 23:50:44 +0000 (UTC) (envelope-from brian@sonicboom.org) Received: from entwistle.sonicboom.org (www.sonicboom.org [69.75.45.54]) (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 4Hhbdv0V4pz4hrl for ; Sat, 30 Oct 2021 23:50:43 +0000 (UTC) (envelope-from brian@sonicboom.org) Received: from [198.18.44.20] (unknown [192.168.1.254]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: brian) by entwistle.sonicboom.org (Postfix) with ESMTPSA id 6165E1EA00FD for ; Sat, 30 Oct 2021 16:50:36 -0700 (PDT) Message-ID: <184f1bd0-0d96-7e6a-7b8e-921874ddc8c5@sonicboom.org> Date: Sat, 30 Oct 2021 16:50:34 -0700 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Subject: Re: IPv6 checksum errors with divert Content-Language: en-US To: stable@freebsd.org References: From: brian In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Hhbdv0V4pz4hrl X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of brian@sonicboom.org designates 69.75.45.54 as permitted sender) smtp.mailfrom=brian@sonicboom.org X-Spamd-Result: default: False [0.43 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[brian]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[stable@freebsd.org]; NEURAL_SPAM_MEDIUM(0.63)[0.632]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.90)[-0.897]; DMARC_NA(0.00)[sonicboom.org]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_SPAM_SHORT(1.00)[1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20001, ipnet:69.75.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Maybe with a tcpdump or packet capture search for http error codes; https://developer.mozilla.org/en-US/docs/Web/HTTP/Status has a list. 400 errors are what usually lead to errors clients observe while the server is still alive. Brian On 10/30/2021 4:33 PM, Peter wrote: > Hi Andrey, hi all, > > there is at least one further issue with divert (and dummynet) > and IPv6: > > If I put EITHER a divert OR a dummynet pipe/queue into the OUTgoing > (layer3) ruleset to the uplink interface, then Youtube is not able to > insert their advertisments into playback, and may hang entirly on > playback. > > That seems to not happen due to timing or bandwith issues, but due to > the sheer existance of a dummynet (or divert). And if I move the > dummynet to the incoming, INTRAnet-facing side of the router, the > problem does not appear. > > So there must still be some other bit in the IPv6 (or in the mbuf?) > that gets improperly mangled during divert and also during dummynet. > > It appears a bit difficult to hunt that one down, due to the sheer > amount of traffic involved in YT streaming, and also since I do not > know exactly for what to look... > > Any helpful ideas are welcome. > > Cheerio, > PMc > From nobody Sun Oct 31 02:24:25 2021 X-Original-To: freebsd-stable@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 1325318223E4 for ; Sun, 31 Oct 2021 02:36:13 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840::12]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "uucp.dinoex.sub.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HhgJr1HX3z4X3N for ; Sun, 31 Oct 2021 02:36:12 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Received: from uucp.dinoex.sub.de (uucp.dinoex.org [185.220.148.12]) by uucp.dinoex.org (8.17.1/8.17.1) with ESMTPS id 19V2a4HX045069 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Sun, 31 Oct 2021 03:36:04 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) X-MDaemon-Deliver-To: X-Authentication-Warning: uucp.dinoex.sub.de: Host uucp.dinoex.org [185.220.148.12] claimed to be uucp.dinoex.sub.de Received: (from uucp@localhost) by uucp.dinoex.sub.de (8.17.1/8.17.1/Submit) with UUCP id 19V2a46X045068 for freebsd-stable@freebsd.org; Sun, 31 Oct 2021 03:36:04 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) Received: from gate.intra.daemon.contact (gate-e [192.168.98.2]) by citylink.dinoex.sub.de (8.16.1/8.16.1) with ESMTP id 19V2RHBR067432 for ; Sun, 31 Oct 2021 03:27:17 +0100 (CET) (envelope-from peter@gate.intra.daemon.contact) Received: from gate.intra.daemon.contact (gate-e [192.168.98.2]) by gate.intra.daemon.contact (8.16.1/8.16.1) with ESMTPS id 19V2OPRd066969 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Sun, 31 Oct 2021 03:24:25 +0100 (CET) (envelope-from peter@gate.intra.daemon.contact) Received: (from peter@localhost) by gate.intra.daemon.contact (8.16.1/8.16.1/Submit) id 19V2OPOh066968 for freebsd-stable@freebsd.org; Sun, 31 Oct 2021 03:24:25 +0100 (CET) (envelope-from peter) Date: Sun, 31 Oct 2021 03:24:25 +0100 From: Peter To: freebsd-stable@freebsd.org Subject: IPv6 inflight fragmentation Message-ID: List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Milter: Spamilter (Reciever: uucp.dinoex.sub.de; Sender-ip: 185.220.148.12; Sender-helo: uucp.dinoex.sub.de;) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (uucp.dinoex.org [185.220.148.12]); Sun, 31 Oct 2021 03:36:07 +0100 (CET) X-Rspamd-Queue-Id: 4HhgJr1HX3z4X3N X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of pmc@citylink.dinoex.sub.org has no SPF policy when checking 2a0b:f840::12) smtp.mailfrom=pmc@citylink.dinoex.sub.org X-Spamd-Result: default: False [-2.10 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[4]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_NA(0.00)[sub.org]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:205376, ipnet:2a0b:f840::/32, country:DE]; RCVD_TLS_LAST(0.00)[] X-ThisMailContainsUnwantedMimeParts: N >From what I understood, inflight fragmentation (on an intermediate router) is not practical with IPv6. But it happens: This router has inbound ethernet and outbound PPPoE: vtnet0: flags=8943 metric 0 mtu 1500 tun0: flags=8151 metric 0 mtu 1492 And that's what is transported - Incoming on vtnet0: IP6 2003:e7:1740:a7e0:41d:92ff:fe01:222.20487 > 2a00:1450:4001:67::8.443: Flags [.], seq 0:1428, ack 1, win 1035, options [nop,nop,TS val 2061109754 ecr 739209924], length 1428 IP6 2003:e7:1740:a7e0:41d:92ff:fe01:222.20487 > 2a00:1450:4001:67::8.443: Flags [.], seq 0:1428, ack 1, win 1035, options [nop,nop,TS val 2061113154 ecr 739209924], length 1428 Outgoing on tun0: IP6 2003:e7:1740:a7e0:41d:92ff:fe01:222 > 2a00:1450:4001:67::8: frag (0|1440) 59241 > 443: Flags [.], seq 0:1408, ack 1, win 1035, options [nop,nop,TS val 2312762048 ecr 739149759], length 1408 IP6 2003:e7:1740:a7e0:41d:92ff:fe01:222 > 2a00:1450:4001:67::8: frag (1440|20) IP6 2003:e7:1740:a7e0:41d:92ff:fe01:222 > 2a00:1450:4001:67::8: frag (0|1440) 59243 > 443: Flags [.], seq 1:1409, ack 1, win 1035, options [nop,nop,TS val 3069543472 ecr 739199972], length 1408 IP6 2003:e7:1740:a7e0:41d:92ff:fe01:222 > 2a00:1450:4001:67::8: frag (1440|20) And it doesn't seem like these packets would be answered at all. This happens when there is a dummynet pipe/queue rule (or a divert rule) in the outbound rules to an interface that must reduce the MTU. As soon as we skip over that dummynet (or divert), we get these ICMPv6 messages at the other end, and the fragmentation ceases: 02:59:53.651258 IP6 2003:e7:1740:a7ff::2 > 2003:e7:1740:a7e0:41d:92ff:fe01:222: ICMP6, packet too big, mtu 1492, length 1240 02:59:53.693376 IP6 2003:e7:1740:a7ff::2 > 2003:e7:1740:a7e0:41d:92ff:fe01:222: ICMP6, packet too big, mtu 1492, length 1240 So the problem is with dummynet and divert. Cheerio, PMc From nobody Sun Oct 31 22:06:40 2021 X-Original-To: freebsd-stable@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 00FA5182617F; Sun, 31 Oct 2021 22:06:53 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 4Hj9Hb3XYrz55xg; Sun, 31 Oct 2021 22:06:50 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from kalamity.joker.local (123-48-130-181.area1b.commufa.jp [123.48.130.181]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 19VM6fFQ021901; Mon, 1 Nov 2021 07:06:41 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Mon, 1 Nov 2021 07:06:40 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Message-Id: <20211101070640.247345226b0dc84717c3ee0b@dec.sakura.ne.jp> In-Reply-To: References: <8d25d2f4-24e2-5b19-5c81-2fe12dc937b7@quip.cz> <20211029074702.d69cba39a643f3f912f8ec81@dec.sakura.ne.jp> <940c9341-6938-05a1-d0b3-f20f07f9d3de@netfence.it> Reply-To: junchoon@dec.sakura.ne.jp Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Hj9Hb3XYrz55xg X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp X-Spamd-Result: default: False [0.40 / 15.00]; HAS_REPLYTO(0.00)[junchoon@dec.sakura.ne.jp]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; DMARC_NA(0.00)[sakura.ne.jp]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_LAST(0.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; NEURAL_HAM_LONG(-1.00)[-0.998]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[123.48.130.181:received] X-ThisMailContainsUnwantedMimeParts: N On Sun, 31 Oct 2021 18:15:25 +0100 Marek Zarychta wrote: > W dniu 29.10.2021 o$B".(B08:29, Andrea Venturoli pisze: > > > > On 10/29/21 00:47, Tomoaki AOKI wrote: > > > >> But possibly we need to delete current smbfs code from base and switch > >> to ports (sysutils/*?) if it require some code having incompatible > >> license for base. > > > +1 for removing smbfs(5) from the base and eventually moving it to the > ports tree. I know some people are still using it with a bit of duct > tape and baling twine to workaround$B".(B SMBv{2,3) incompatibility. Keeping this in base as long as possible should be preferred, as changes throuout all filesystems would be easier to be missed that on ports. But borrowing GPL'ed (or any other BSD-incompatible licensed) codes would disallow it. > With SMBv1 support, only our smbfs(5) became useless a few years ago. No. It's much better than nothing. For example, DSM on Synology NAS disabled support for SMB1 and NTLM1 by default, but admin can easily enable them again through control panel. So it's usable (for local networks) at least for now. > Unfortunately, there is no replacement in the ports tree. To mount SMB > shares for Nextcloud the port net/pecl-smbclient can be used, but > definitely deploying Nextcloud to mount only SMB shares is overkill. > > > OTOH having a port is not in any way worse as having a broken piece of > > base. > > It sounds reasonable. Moreover, the story of net/wireguard-kmod has > proven that moving some modules into ports, where the software > development is done in a more flexible way, can be beneficial for both: > the developers and the community. > > My opinion is only the opinion of the FreeBSD user, but I believe that > sometimes the feedback from the userbase is important, especially that a > few months I was told by one of the younger *NIX admins that our > (FreeBSD) community is the best and he is willing to make a transition > of some services to FreeBSD as soon as he gets permission from the > management. > > With kind regards, > > -- > Marek Zarychta > > -- Tomoaki AOKI