From nobody Mon Sep 16 22:39:53 2024 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 4X70Gr2fVbz5W2Vr for ; Mon, 16 Sep 2024 22:40:04 +0000 (UTC) (envelope-from pete@twisted.org.uk) Received: from toybox.twisted.org.uk (toybox.twisted.org.uk [178.250.76.50]) (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 4X70Gq3WF5z4PL7 for ; Mon, 16 Sep 2024 22:40:03 +0000 (UTC) (envelope-from pete@twisted.org.uk) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=twisted.org.uk header.s=tbx-short header.b=JR0LSKZa; dmarc=pass (policy=none) header.from=twisted.org.uk; spf=pass (mx1.freebsd.org: domain of pete@twisted.org.uk designates 178.250.76.50 as permitted sender) smtp.mailfrom=pete@twisted.org.uk DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=twisted.org.uk; s=tbx-short; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:From:References:To:Subject:MIME-Version:Date:Message-ID:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=XjcAIup3BL59uncUfYVHzWM6qmzCKAO8tfb3cBR8CyA=; t=1726526403; x=1727390403; b=JR0LSKZa73FosAUSCi9bVDtUOgkhKkiMcJqbSi7lfkeO02On9gPGGSRpyWozOEJEI+8YdAcqnoU qPkUfO++YcimFT3AtYj556jMj0x4sBTXDJU4T0/64eCTt8BKiHg76bTH7s42cRNrYm27QUvc5o34/ RNyP6e4/jtCqZViWejU=; Received: from mailnull by toybox.twisted.org.uk with spamc-scanned (Exim 4.96.2 (FreeBSD)) (envelope-from ) id 1sqKNu-000PKZ-0J for stable@freebsd.org; Mon, 16 Sep 2024 22:39:54 +0000 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on toybox.twisted.org.uk X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED, T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=4.0.0 X-Spam-Score: -1.0 () Received: from balta.twisted.org.uk ([2001:470:6cc4:1::57]) by toybox.twisted.org.uk with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.96.2 (FreeBSD)) (envelope-from ) id 1sqKNt-000PKU-3B for stable@freebsd.org; Mon, 16 Sep 2024 22:39:54 +0000 Message-ID: Date: Mon, 16 Sep 2024 23:39:53 +0100 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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta Subject: Re: 13.3R's installworld killed system--please help! To: stable@freebsd.org References: <202409150523.48F5NNVj003365@sdf.org> Content-Language: en-GB From: Pete French In-Reply-To: <202409150523.48F5NNVj003365@sdf.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-spamc-toybox: true X-transport-toybox: lookuphost X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.987]; DMARC_POLICY_ALLOW(-0.50)[twisted.org.uk,none]; R_SPF_ALLOW(-0.20)[+ip4:178.250.76.50/32]; R_DKIM_ALLOW(-0.20)[twisted.org.uk:s=tbx-short]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; SUBJECT_ENDS_EXCLAIM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:12290, ipnet:178.250.72.0/21, country:GB]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[stable@freebsd.org]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[twisted.org.uk:+] X-Rspamd-Queue-Id: 4X70Gq3WF5z4PL7 On 15/09/2024 06:23, Scott Bennett wrote: > Thank you very much for this suggestion! It hadn't crossed my mind, > likely because I thought I had thrown all those old CD-Rs and DVD+/-Rs away > when I moved to a different apartment in February. After seeing your message, > though, I went looking. In the very first place I checked, lo and behold, I > found a DVD-R I had labeled "PC-BSD 8.2 (64-bit) Installer, LiveCD, and Repair > Disk" and "PCBSD8.2-x64-DVD.iso Disk 1 of 1". 8-D So I then did as you > suggested. Unfortunately, it made no change in the resulting boot behavior. > :-( At least I now know I have such a disk at hand to try such things. Am gald you found the disc - I was also going to say that I am quite happy to burn one for you and post it, though thats a slow method of acquiring a CD! I remember posting someone in the US a copy of Minix on 5.25 floppies back in 1989, and it took a while to get there, but did indeed boot on arrival. Am dissapointed that the updated boot sectors didnt help though. I would have bet money on that being the issue (and lost the bet!) > Thank you both for that reassuring information. After all this, it is > now clear that the boot code was not the problem and that I *still* have no > idea what went wrong. I do not remember ever having an upgrade from source > actually fail before this experience. Even the trickiest one many years ago-- > a merged procedure to upgrade from i386 to amd64 in place and from, I *think*, > 9.x to 10.x, went well. (Trust me, I was as nervous as I would be on a > non-precision approach in nighttime IMC in a non-radar, mountainous environment > with flashes of light around me (yes, that happened to me once), but I had > planned all the steps carefully, and my combined procedure was successful.) !!!! umm, yeah, I really would not like to try that! not that I would, never having got an IMC rating, but the little bits I did with foggles on convinced me that this was not the kind of flying I wanted to do ;) i386 -> amd64, however, I did that, and that worked fine, despite also being very nervous. I;ve only ever done source upgrades, going right back to FreeBSD 3, and the only times it failed to boot were when I forgot to upgrade the boot code for a newer ZFS pool. > rolled every file system back to that snapshot. After reinserting the drives > into the tower, I booted it and ... my 12.4-RELEASE-p2 system was up and > running again. What a relief! Aha! Fantastic! OK, so, you rolled back the filesystems .... but left the boot code intact ? So this is now running your old filesystems but booting using the updated 14.2 code that you wrote using PC-BSD, yes ? > So I'm back to where I was before attempting the upgrade. It's a good > system, but it is out of support, so thank you very much to everyone who > responded anyway. I am pondering what my next step should be. OK, I have forgotten the start of this thread, but you went from the last version of 12 to a build of 13.0 release, which you compiled under the installed 12? How far did it get in the boot process - did it even find the pool and try and load the kernel, or not even that far? If it is now booting off the installed latest boot code, then we know it can run code which should find the pool. Do you have the 'bootfs' property set on the pool ? This is a puzzle - I've done this repeatedly, going from 3 all the way to 14, and its always worked. -pete. From nobody Mon Sep 16 22:58:38 2024 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 4X70wk21vBz5WMQM for ; Mon, 16 Sep 2024 23:09:26 +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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X70wh5g3Jz4TjK; Mon, 16 Sep 2024 23:09:24 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of pmc@citylink.dinoex.sub.org designates 2a0b:f840::12 as permitted sender) smtp.mailfrom=pmc@citylink.dinoex.sub.org; arc=pass ("uucp.dinoex.org:s=M20221114:i=1") Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840:0:0:0:0:0:12]) by uucp.dinoex.org (8.18.1/8.18.1) with ESMTPS id 48GN96lp026474 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 17 Sep 2024 01:09:06 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) ARC-Seal: i=1; a=rsa-sha256; d=uucp.dinoex.org; s=M20221114; t=1726528149; cv=none; b=AtmrViBmXCxlh1j4ecCxHut64OIGh0sIjj9B9OrAHKnl0ztlIL4fyqEO2OV6fhv3o0/VYPUsMklCEnyzMszJZkP+syS+cnqEmK9asjzHonfGtueHG2/PdpDc654KgRpjEJgXfZB9BKCYHrvC59p41nmMKbNnR0DswkQAJZCg0aA= ARC-Message-Signature: i=1; a=rsa-sha256; d=uucp.dinoex.org; s=M20221114; t=1726528149; c=relaxed/simple; bh=55KU1KNcwVz9Nl2TTUZQXmarwRPLSYfqNDo6t8u8F3A=; h=Received:Received:Received:Received:X-Authentication-Warning:Date: From:To:Cc:Subject:Message-ID:MIME-Version:Content-Type: Content-Disposition:X-Milter:X-Greylist; b=jkjvHS1UsFJ6v2bLrYkrWcxKfztElPDen2VA9wFmEvCuFlVRIgdCvoM2RXoQ2CTDtCwtFFqM29FOm3J5u5pmg7N8nSYGbG/ieDzmqeZf8yLJqYZQWsWqC/kEMMS5ir89C/ylyJDGwMoxfEMqT45h8sIXnaB8DF9A6pw8kZ+wS/M= ARC-Authentication-Results: i=1; uucp.dinoex.org Received: (from uucp@localhost) by uucp.dinoex.org (8.18.1/8.18.1/Submit) with UUCP id 48GN96IY026473; Tue, 17 Sep 2024 01:09:06 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Received: from disp.intra.daemon.contact (disp-e.intra.daemon.contact [IPv6:fd00:0:0:0:0:0:0:112]) by admn.intra.daemon.contact (8.18.1/8.18.1) with ESMTPS id 48GN1Z9s008150 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=OK); Tue, 17 Sep 2024 01:01:36 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Received: from disp.intra.daemon.contact (localhost [127.0.0.1]) by disp.intra.daemon.contact (8.18.1/8.18.1) with ESMTPS id 48GMwcVF027450 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 17 Sep 2024 00:58:39 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Received: (from pmc@localhost) by disp.intra.daemon.contact (8.18.1/8.18.1/Submit) id 48GMwcMS027449; Tue, 17 Sep 2024 00:58:38 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) X-Authentication-Warning: disp.intra.daemon.contact: pmc set sender to pmc@citylink.dinoex.sub.org using -f Date: Tue, 17 Sep 2024 00:58:38 +0200 From: Peter To: freebsd-stable@freebsd.org Cc: cmt@freebsd.org Subject: 13.4 compiles firefox functionally different 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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Milter: Spamilter (Reciever: uucp.dinoex.org; Sender-ip: 0:0:2a0b:f840::; Sender-helo: uucp.dinoex.org;) X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (uucp.dinoex.org [IPv6:2a0b:f840:0:0:0:0:0:12]); Tue, 17 Sep 2024 01:09:09 +0200 (CEST) X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.58 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; ARC_ALLOW(-1.00)[uucp.dinoex.org:s=M20221114:i=1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.72)[0.718]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; R_DKIM_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:205376, ipnet:2a0b:f840::/32, country:DE]; HAS_XAW(0.00)[]; DMARC_NA(0.00)[sub.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4X70wh5g3Jz4TjK Hi, after upgrading to 13.4-RC2-p1, I recompiled all ports. Today I found my firefox can no longer render a certain webpage; the output is garbled as if the CSS were missing/defective. Here is details and picture: https://forums.freebsd.org/threads/firefox-displays-unintellegible-garbage-only-on-freebsd.94963/post-671994 The firefox version is -esr-115.15.0,1, from 2024Q3 as of a week ago. Investigation showed: * firefox from package as of today (130.something) works well. * firefox-esr from package as of today (128.something) works well. * firefox-esr from ports as of today (128.2.0esr) freshly compiled on 13.4-RC2-p1 also works well (prereqs still from last week) * firefox-esr 115.14.0_1,1 locally compiled a few weeks ago on Rel. 13.3 also works well. So I did verify: I restarted a Rel.13.3-p5, fetched all prereqisite ports from backup (so these were also compiled on 13.3), and then compiled firefox-esr-115.15.0,1, the very same that now renders garbage, using the very same ports tree, with OS running 13.3-p5. And that one now works! So bottomline is: firefox-esr 115.15.0,1 - the one that was in 2024Q3 until about a week ago - works correct when compiled on 13.3 (along with all it's prereq ports), but renders garbage for a certain webpage when compiled on 13.4-RC2 (along with all it's prereq ports). I don't like this, because now the question is: what else might 13.4 compile so that it suddenly functions differently? (I glanced thru PR 277021 - but it doesn't seem to mention anything about webpages displaying broken, or any functional difference) Any idea how this might come to happen, anybody? From nobody Tue Sep 17 11:06:28 2024 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 4X7JrF72fPz594Wx for ; Tue, 17 Sep 2024 11:06:37 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.osfux.nl (vm1982.osfux.nl [79.99.187.212]) (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 4X7JrF0TLsz4Cff for ; Tue, 17 Sep 2024 11:06:36 +0000 (UTC) (envelope-from mail@osfux.nl) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=osfux.nl header.s=default header.b=P8ma8+Ds; dmarc=pass (policy=reject) header.from=osfux.nl; spf=pass (mx1.freebsd.org: domain of mail@osfux.nl designates 79.99.187.212 as permitted sender) smtp.mailfrom=mail@osfux.nl Received: from vm1982.osfux.nl (localhost [127.0.0.1]) by vm1982.osfux.nl (Postfix) with ESMTP id 13C217F for ; Tue, 17 Sep 2024 13:06:29 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1726571189; bh=UOpat0X8w/Cy0ETwtZ7YF12mS7N36lmaSn9OuZHtRDE=; h=Date:To:From:Subject; b=P8ma8+DspoCRlFzQQg9ljfJjAqt9DYD/ARw/xs1EGA+ITMPoHsZDVKp9K9qjLJzfi SsFddwO43OKsho/53nZbFG3xGDDdYQ0imAO1zXm9DUXT4/3YtUI83Ji9gyPSJe47D7 cktzYS6RL7D6o5Rpz4yY1WvDUzWo/FLDGNrqAY7Rqvt8AJ5ohNNpmo/sqiuqS0DhFO CQsR/y5lfLDfRPIrMkL5UQWdSNwIEm7SO59aW9dKVVfFE7DqsiplDCWlpuCFsWtGJL caEVd7+Qj8FQN4XVHxe+7bqJVPLbhjW8HfIwzzTXXxmmoXzoI6fphNxpVyKoCFGwRp ICdYZ1qMzdXVtdDuxUSVsqb1ENKHjWE5hrtMGYtWS30OuKwA0fdye7xJoLnHufViSX sWVuXNr6xycYFFcvGk97zbM4fR1w98C3HswWyKZt5QGWLf7u9ChRDan8Eq0/gYYLBM GOPWEUM3a90SFv1/jut6erqvf8qwtoO9x7radlSsflmpl2QGKVHYpt5tqjmhK1fISe kfTRn1ORCrWEL4o0BTC1NN3Fjk7OMhjeu3RXaFl6gs0Xj/lz3KjrgX5WdRa9tDJad3 uTzbZP24OGqphB4Sjm/3ebUgEvolqTWAe4Cmvh1okKctO+EuPEu5e2cp+nkv71rQAP 12uiIt/5jIb70MSj8dY8lsjs= X-Spam-Status: No, score=0.0 required=5.0 tests=none shortcircuit=no X-Spam-Checker-Version: SpamAssassin 4.0.0 Received: from [0.0.0.0] (unknown [193.187.128.167]) (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) (No client certificate requested) by vm1982.osfux.nl (Postfix) with ESMTPSA for ; Tue, 17 Sep 2024 13:06:29 +0200 (CEST) Message-ID: Date: Tue, 17 Sep 2024 13:06:28 +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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: freebsd-stable@freebsd.org From: fuxjez Subject: issues with syslogd include redirecting wg0 output to custom location Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.996]; DMARC_POLICY_ALLOW(-0.50)[osfux.nl,reject]; R_DKIM_ALLOW(-0.20)[osfux.nl:s=default]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:8315, ipnet:79.99.184.0/21, country:NL]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; DKIM_TRACE(0.00)[osfux.nl:+] X-Rspamd-Queue-Id: 4X7JrF0TLsz4Cff Hi, I'm experimenting with FreeBSD's 14.1's wireguard implementation. So far i've been quite satisfied with using it locally (over an unsecured network). I would like to set up a PoC using wg as a VPN provider (replacing openvpn) next. Before opening wireguard endpoints up for global connectivity I would like wireguard logs to be parsed by something like Fail2ban (so I can have pf ward off baddies). I've managed to get wireguards' logs into /var/log/messages by issueing: /sbin/ifconfig wg0 debug Since they are quite verbose and are polluting /var/log/messages, I'd like for them to land in /var/ramdisk_log/wireguard.log instead. I've instructing newsyslog to create the logfile : [root@system:/]# cat /var/ramdisk_log/wireguard.log Sep 17 00:27:36 system newsyslog[55203]: logfile first created [root@system:/]# ls -laht /var/ramdisk_log/wireguard.log -rw-rw---- 1 root wheel 66B Sep 17 00:27 /var/ramdisk_log/wireguard.log [root@system:/]# and have since attempted to redirect the "wg0" logs to /var/ramdisk_log/wireguard.log by using these syslog includes: :msg, contains, ".*wg0: .*" *.* /var/ramdisk_log/wireguard.log and :msg, regex, "wg[0-9]{1,2}\:\ " *.* /var/ramdisk_log/wireguard.log Unfortunately, the includes are not redirecting the wg0 logs to my preferred location (the includes are placed in /etc/syslog.d/wireguard.conf which is parsed by syslogd) and I'm out of ideas / logs on how to further troubleshoot why the logstream doesn't get redirected :( Im hoping somebody - a little better versed in syslog - could provide me with some insights / pointers... Feedback appreciated! ruben From nobody Tue Sep 17 12:09:03 2024 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 4X7LDN5VTdz59DJc for ; Tue, 17 Sep 2024 12:09:08 +0000 (UTC) (envelope-from SRS0=vk1u=QP=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 4X7LDN22qbz4Nj5 for ; Tue, 17 Sep 2024 12:09:08 +0000 (UTC) (envelope-from SRS0=vk1u=QP=quip.cz=000.fbsd@elsa.codelab.cz) Authentication-Results: mx1.freebsd.org; none Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 597B1D78A8; Tue, 17 Sep 2024 14:09:05 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quip.cz; s=private; t=1726574945; bh=EINHgKmNf6zhdevHhTfP+NdpvpEzu623uTyUUO87Nms=; h=Date:Subject:To:References:From:In-Reply-To; b=Y81UGETSDc5EcUZjjRLftzts25DgRW4LG3fOPyWfCcFTpZJ1B/8vONvylLDa4gvMV fRVue4wzW/6pQB2LVRcLSkzXRA6/fRRtBXfmd/igZ4PrK+Gd69L04CNGTcNsoXY1M+ nmNmzDEGgssQxgHO8/thE0RDxWQOTDUie8IoYqhI= Received: from [192.168.145.49] (ip-89-177-27-225.bb.vodafone.cz [89.177.27.225]) (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 A1464D78A3; Tue, 17 Sep 2024 14:09:04 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quip.cz; s=private; t=1726574944; bh=EINHgKmNf6zhdevHhTfP+NdpvpEzu623uTyUUO87Nms=; h=Date:Subject:To:References:From:In-Reply-To; b=pLdv7ic/yTQ/jDIZNp54yIz+40wIkQd3Fho+iCn+/xNrEFMtsN4p87aII91WQmsTT Hl30y5inBJpn6mDC4V9rI8MNJaoZpN1ElHyXqz9wPREHsj1uR8u+jQKpBQ3TIEYzeR jP+LfE2jlGGqomtsn/Jgd79doHzoe4M6qQzt45+4= Message-ID: Date: Tue, 17 Sep 2024 14:09:03 +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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: issues with syslogd include redirecting wg0 output to custom location To: fuxjez , freebsd-stable@freebsd.org References: Content-Language: en-US From: Miroslav Lachman <000.fbsd@quip.cz> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ] X-Rspamd-Queue-Id: 4X7LDN22qbz4Nj5 On 17/09/2024 13:06, fuxjez wrote: [..] > and have since attempted to redirect the "wg0" logs to > /var/ramdisk_log/wireguard.log by using these syslog includes: > > :msg, contains, ".*wg0: .*" > *.*                                /var/ramdisk_log/wireguard.log > > and > > :msg, regex, "wg[0-9]{1,2}\:\ " > *.*                                /var/ramdisk_log/wireguard.log > > Unfortunately, the includes are not redirecting the wg0 logs to my > preferred location (the includes are placed in > /etc/syslog.d/wireguard.conf which is parsed by syslogd) and I'm out of > ideas / logs on how to further troubleshoot why the logstream doesn't > get redirected :( I never used property based filters in syslog.conf. Is it possible for you to use just classic style? For example I use following to have separate log file for messages from pkg (install / upgrade / delete): !-pkg,pkg-static *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages !pkg,pkg-static *.* /var/log/pkg.log But I don't know how your wg0 debug entries are identified in the messages log. Kind regards Miroslav Lachman From nobody Tue Sep 17 12:38:27 2024 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 4X7LtP2YDxz59J5R for ; Tue, 17 Sep 2024 12:38:37 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.osfux.nl (vm1982.osfux.nl [IPv6:2a03:5500:1724:55:79:99:187:212]) (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 4X7LtP0Htzz4SFk for ; Tue, 17 Sep 2024 12:38:36 +0000 (UTC) (envelope-from mail@osfux.nl) Authentication-Results: mx1.freebsd.org; none Received: from vm1982.osfux.nl (localhost [127.0.0.1]) by vm1982.osfux.nl (Postfix) with ESMTP id 03FD87F; Tue, 17 Sep 2024 14:38:28 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1726576708; bh=9GyX3YaAiOju9nX+q/SXua/t3769sCVHrcVdVQSEMho=; h=Date:Subject:To:References:From:In-Reply-To; b=gtx4Dea4QLSE0NcmxBNGr6KYTXHbj/SjRZX2ER2eFQu5hX4xPnVof1GzRRlv4fSlh 4fVLci95AjUV4jT+OMf5SqvuNCcUx0NBkoygUaq1MX2fbZ3DMb/hPyfDkr/FD151ld S1y8NKs6NiHJenokEyqoomyZxsIVKWivI7nIeEmc5e/ycPjSvbTM8C30QkeltktXqa 1w/e1f5Af/7G9ikeFTCAUN+C5vGDYaoO5TRB9k8frrFsvc/qK+I/42zrsE4bCOXZQZ +zbpzEqyxOxiaPyDY20cdjFyg8YjJP46o3xG0IYoeOg7Ky+5ZnlxCnikhOtGA+hbcN C/QVyEMfyVdjfRl8JJpWYINZx1RkzugwntsEO+CpWfi/aipkE+gkEO7I9ilYf8VBaR BoQumtNMqpXEqGodV8hzdosPVaVagzzOPkSPKol8n0ZlDTnay0k2f0B7NOkMGNBiA2 F5/449K3/sT+dQcCp1ZRx3d2rLa+1p/zdam8y97Slr8eIW2W88BtDZosvEqLpQN0Nb +3ZzCmxMYnQA/pk8zx/hWmBGmOE0QKkVyYzoYppj43xr5r3Tv3tIssZmATZnMlXBvX k19FEHyvgwZQZsiP1yvb7rNTZ1nPU7gZH1eCVuypj3AgOPqGhfUl7/a3tVB3muqgmA OyeRPFB1pl1vEqDgVLyZtt+4= X-Spam-Status: No, score=0.0 required=5.0 tests=none shortcircuit=no X-Spam-Checker-Version: SpamAssassin 4.0.0 Received: from [0.0.0.0] (unknown [193.187.128.167]) (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) (No client certificate requested) by vm1982.osfux.nl (Postfix) with ESMTPSA; Tue, 17 Sep 2024 14:38:27 +0200 (CEST) Message-ID: <4250c967-61c7-419a-b542-455a8f655dd1@osfux.nl> Date: Tue, 17 Sep 2024 14:38:27 +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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: issues with syslogd include redirecting wg0 output to custom location To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-stable@freebsd.org References: Content-Language: en-US From: fuxjez In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8315, ipnet:2a03:5500::/31, country:NL] X-Rspamd-Queue-Id: 4X7LtP0Htzz4SFk Hi Miroslav, Thank you for your suggestion. I got the property based filtering from the manpage. The entries in /var/log/messages look like these: wg0: Sending handshake response to peer 1 wg0: Receiving keepalive packet from peer 1 wg0: Sending keepalive packet to peer 1 wg0: Sending keepalive packet to peer 1 wg0: Sending keepalive packet to peer 1 wg0: Receiving handshake initiation from peer 0 wg0: Sending handshake response to peer 0 wg0: Sending keepalive packet to peer 0 wg0: Sending keepalive packet to peer 1 wg0: Receiving handshake initiation from peer 1 wg0: Sending handshake response to peer 1 wg0: Sending keepalive packet to peer 1 replacing: *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages in - /etc/syslog.conf - with: !-wg0 *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages !wg0 *.* /var/ramdisk_log/wireguard.log does redirect the logstream perfectly. Thank you for your suggestion :) Regards, ruben On 9/17/24 14:09, Miroslav Lachman wrote: > On 17/09/2024 13:06, fuxjez wrote: > > [..] > >> and have since attempted to redirect the "wg0" logs to /var/ >> ramdisk_log/wireguard.log by using these syslog includes: >> >> :msg, contains, ".*wg0: .*" >> *.*                                /var/ramdisk_log/wireguard.log >> >> and >> >> :msg, regex, "wg[0-9]{1,2}\:\ " >> *.*                                /var/ramdisk_log/wireguard.log >> >> Unfortunately, the includes are not redirecting the wg0 logs to my >> preferred location (the includes are placed in /etc/syslog.d/ >> wireguard.conf which is parsed by syslogd) and I'm out of ideas / logs >> on how to further troubleshoot why the logstream doesn't get >> redirected :( > > I never used property based filters in syslog.conf. > Is it possible for you to use just classic style? > For example I use following to have separate log file for messages from > pkg (install / upgrade / delete): > > !-pkg,pkg-static > *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/ > messages > > !pkg,pkg-static > *.*                                  /var/log/pkg.log > > But I don't know how your wg0 debug entries are identified in the > messages log. > > Kind regards > Miroslav Lachman > > From nobody Tue Sep 17 13:35:59 2024 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 4X7N8d3chvz59Qv0 for ; Tue, 17 Sep 2024 13:36:01 +0000 (UTC) (envelope-from mack@macktronics.com) Received: from mail.macktronics.com (coco.macktronics.com [209.181.253.65]) (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 4X7N8d1qTkz4bCC; Tue, 17 Sep 2024 13:36:01 +0000 (UTC) (envelope-from mack@macktronics.com) Authentication-Results: mx1.freebsd.org; none Received: from olive.macktronics.com (unknown [209.181.253.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.macktronics.com (Postfix) with ESMTPS id 244D6FDA; Tue, 17 Sep 2024 08:35:59 -0500 (CDT) Date: Tue, 17 Sep 2024 08:35:59 -0500 (CDT) From: Dan Mack To: Peter cc: freebsd-stable@freebsd.org, cmt@freebsd.org Subject: Re: 13.4 compiles firefox functionally different In-Reply-To: Message-ID: <0e6c0c09-907c-26f3-fb78-287231661952@macktronics.com> 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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:209, ipnet:209.181.252.0/23, country:US] X-Rspamd-Queue-Id: 4X7N8d1qTkz4bCC On Tue, 17 Sep 2024, Peter wrote: > Hi, > > after upgrading to 13.4-RC2-p1, I recompiled all ports. > > Today I found my firefox can no longer render a certain webpage; > the output is garbled as if the CSS were missing/defective. > Here is details and picture: > https://forums.freebsd.org/threads/firefox-displays-unintellegible-garbage-only-on-freebsd.94963/post-671994 > > The firefox version is -esr-115.15.0,1, from 2024Q3 as of a > week ago. > > Investigation showed: > * firefox from package as of today (130.something) works well. > * firefox-esr from package as of today (128.something) works > well. > * firefox-esr from ports as of today (128.2.0esr) freshly compiled > on 13.4-RC2-p1 also works well (prereqs still from last week) > * firefox-esr 115.14.0_1,1 locally compiled a few weeks ago on > Rel. 13.3 also works well. > > So I did verify: I restarted a Rel.13.3-p5, fetched all > prereqisite ports from backup (so these were also compiled on 13.3), > and then compiled firefox-esr-115.15.0,1, the very same that now > renders garbage, using the very same ports tree, with OS running > 13.3-p5. And that one now works! > > So bottomline is: > firefox-esr 115.15.0,1 - the one that was in 2024Q3 until about a > week ago - works correct when compiled on 13.3 (along with all it's > prereq ports), but renders garbage for a certain webpage when > compiled on 13.4-RC2 (along with all it's prereq ports). > > I don't like this, because now the question is: what else might 13.4 > compile so that it suddenly functions differently? > > > (I glanced thru PR 277021 - but it doesn't seem to mention anything > about webpages displaying broken, or any functional difference) > > Any idea how this might come to happen, anybody? Probably not related but I'll bring it up anyway; there was issue with firefox/other programs on alpine linux a couple weeks ago where the MESA package's upgrade in combination with using the link time optimization feature under gcc-14.x caused garbled previews and other graphical anomolies on my Firefox and my sway window manager. Not sure which compiler / mesa is used to build firefox on FreeBSD but could be part of the problem I guess or a place to look at the dependencies. It looks like they disabled LTO on the mesa build to fix the issue. That was using mesa-24.2.2. Dan From nobody Tue Sep 17 14:36:41 2024 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 4X7PW574jqz59XfJ for ; Tue, 17 Sep 2024 14:37:05 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from gid2.gid.co.uk (ns0.gid.co.uk [IPv6:2001:470:94de::240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gid2.gid.co.uk", Issuer "gid2.gid.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X7PW53dczz4lTF for ; Tue, 17 Sep 2024 14:37:05 +0000 (UTC) (envelope-from rb@gid.co.uk) Authentication-Results: mx1.freebsd.org; none Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) by gid2.gid.co.uk (8.15.2/8.15.2) with ESMTP id 48HEavSx061967; Tue, 17 Sep 2024 15:36:57 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from smtpclient.apple ([89.248.30.154]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id 48HEapJo047295; Tue, 17 Sep 2024 15:36:51 +0100 (BST) (envelope-from rb@gid.co.uk) Content-Type: text/plain; charset=utf-8 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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\)) Subject: Re: issues with syslogd include redirecting wg0 output to custom location From: Bob Bishop In-Reply-To: Date: Tue, 17 Sep 2024 15:36:41 +0100 Cc: "freebsd-stable@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <82DA970E-36C5-4151-937B-F119D43484AB@gid.co.uk> References: To: fuxjez X-Mailer: Apple Mail (2.3776.700.51) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-Rspamd-Queue-Id: 4X7PW53dczz4lTF Hi, > On 17 Sep 2024, at 12:06, fuxjez wrote: >=20 > Hi, >=20 > I'm experimenting with FreeBSD's 14.1's wireguard implementation. >=20 > So far i've been quite satisfied with using it locally (over an = unsecured network). I would like to set up a PoC using wg as a VPN = provider (replacing openvpn) next. >=20 > Before opening wireguard endpoints up for global connectivity I would = like wireguard logs to be parsed by something like Fail2ban (so I can = have pf ward off baddies). I've managed to get wireguards' logs into = /var/log/messages by issueing: >=20 > /sbin/ifconfig wg0 debug >=20 > Since they are quite verbose and are polluting /var/log/messages, I'd = like for them to land in /var/ramdisk_log/wireguard.log instead. I've = instructing newsyslog to create the logfile : >=20 > [root@system:/]# cat /var/ramdisk_log/wireguard.log > Sep 17 00:27:36 system newsyslog[55203]: logfile first created > [root@system:/]# ls -laht /var/ramdisk_log/wireguard.log > -rw-rw---- 1 root wheel 66B Sep 17 00:27 = /var/ramdisk_log/wireguard.log > [root@system:/]# >=20 > and have since attempted to redirect the "wg0" logs to = /var/ramdisk_log/wireguard.log by using these syslog includes: >=20 > :msg, contains, ".*wg0: .*" > *.* /var/ramdisk_log/wireguard.log I think the value for =E2=80=9Ccontains=E2=80=9D has to be a simple = string > and >=20 > :msg, regex, "wg[0-9]{1,2}\:\ " > *.* /var/ramdisk_log/wireguard.log regex uses a basic RE so it would have to be "wg[0-9]\{1,2\}\:\ =E2=80=9C (ie escape the { } ) ; or if you want an extended (modern) RE: :msg, ereregex, "wg[0-9]{1,2}\:\ " >=20 > Unfortunately, the includes are not redirecting the wg0 logs to my = preferred location (the includes are placed in = /etc/syslog.d/wireguard.conf which is parsed by syslogd) and I'm out of = ideas / logs on how to further troubleshoot why the logstream doesn't = get redirected :( >=20 > Im hoping somebody - a little better versed in syslog - could provide = me with some insights / pointers... >=20 > Feedback appreciated! >=20 > ruben >=20 -- Bob Bishop rb@gid.co.uk From nobody Tue Sep 17 21:39:37 2024 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 4X7b1J5jrZz5W2xk for ; Tue, 17 Sep 2024 21:45:24 +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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X7b1J30s1z4KHW; Tue, 17 Sep 2024 21:45:24 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Authentication-Results: mx1.freebsd.org; none Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840:0:0:0:0:0:12]) by uucp.dinoex.org (8.18.1/8.18.1) with ESMTPS id 48HLj859021499 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 17 Sep 2024 23:45:08 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) ARC-Seal: i=1; a=rsa-sha256; d=uucp.dinoex.org; s=M20221114; t=1726609510; cv=none; b=ZZ5iVa/tH0wgejFwKbAmjSJp7Y/ZzqJ+XQhNnow7MEp59vd/Or2f0MC5YOOEv0G2tXYATrWLJTI4FV5dlMNFRQzM8E6UWx4lU5Y0w4ZvntHANxBxxSH8DDo/9dWI2tQg+8A+Czmu9XbY+4W3YGFsQ89trEZkA27iBOnNy2G6LMM= ARC-Message-Signature: i=1; a=rsa-sha256; d=uucp.dinoex.org; s=M20221114; t=1726609510; c=relaxed/simple; bh=mF3d50PyIoXJjRjLDGo0yf+qLlRwXkjBERIlGYN99AE=; h=Received:Received:Received:Received:X-Authentication-Warning:Date: From:To:Cc:Subject:Message-ID:References:MIME-Version:Content-Type: Content-Disposition:In-Reply-To:X-Milter:X-Greylist; b=L9xlHqxyR7Qih2DhTm288m4NT10yaEb1GsfnDUeq7ptGJVXtAaDrtHu6o3l8YE4MWDSqbpeKGbQo1S12Ic++txgOPFRHA4Tn5VHrxPm1tR++qNATGcWfqfLB+22sS1OoweAf+3W2s+kJJIs9+piqseZNZmYA0S757PR+kyfqNO4= ARC-Authentication-Results: i=1; uucp.dinoex.org Received: (from uucp@localhost) by uucp.dinoex.org (8.18.1/8.18.1/Submit) with UUCP id 48HLj86E021498; Tue, 17 Sep 2024 23:45:08 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Received: from cora.intra.daemon.contact (cora-v1.intra.daemon.contact [IPv6:fd00:0:0:0:0:0:0:1206]) by admn.intra.daemon.contact (8.18.1/8.18.1) with ESMTPS id 48HLfCYA022023 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Tue, 17 Sep 2024 23:41:14 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Received: from cora.intra.daemon.contact (localhost [127.0.0.1]) by cora.intra.daemon.contact (8.18.1/8.18.1) with ESMTPS id 48HLdb2D002205 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 17 Sep 2024 23:39:37 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Received: (from pmc@localhost) by cora.intra.daemon.contact (8.18.1/8.18.1/Submit) id 48HLdbPZ002204; Tue, 17 Sep 2024 23:39:37 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) X-Authentication-Warning: cora.intra.daemon.contact: pmc set sender to pmc@citylink.dinoex.sub.org using -f Date: Tue, 17 Sep 2024 23:39:37 +0200 From: Peter To: Dan Mack Cc: freebsd-stable@freebsd.org, cmt@freebsd.org Subject: Re: 13.4 compiles firefox functionally different Message-ID: References: <0e6c0c09-907c-26f3-fb78-287231661952@macktronics.com> 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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0e6c0c09-907c-26f3-fb78-287231661952@macktronics.com> X-Milter: Spamilter (Reciever: uucp.dinoex.org; Sender-ip: 0:0:2a0b:f840::; Sender-helo: uucp.dinoex.org;) X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (uucp.dinoex.org [IPv6:2a0b:f840:0:0:0:0:0:12]); Tue, 17 Sep 2024 23:45:10 +0200 (CEST) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:205376, ipnet:2a0b:f840::/32, country:DE] X-Rspamd-Queue-Id: 4X7b1J30s1z4KHW On Tue, Sep 17, 2024 at 08:35:59AM -0500, Dan Mack wrote: ! On Tue, 17 Sep 2024, Peter wrote: ! ! > Hi, ! > ! > after upgrading to 13.4-RC2-p1, I recompiled all ports. ! > ! > Today I found my firefox can no longer render a certain webpage; ! > the output is garbled as if the CSS were missing/defective. ! > Here is details and picture: ! > https://forums.freebsd.org/threads/firefox-displays-unintellegible-garbage-only-on-freebsd.94963/post-671994 ! > ! > The firefox version is -esr-115.15.0,1, from 2024Q3 as of a ! > week ago. ! > ! > Investigation showed: ! > * firefox from package as of today (130.something) works well. ! > * firefox-esr from package as of today (128.something) works ! > well. ! > * firefox-esr from ports as of today (128.2.0esr) freshly compiled ! > on 13.4-RC2-p1 also works well (prereqs still from last week) ! > * firefox-esr 115.14.0_1,1 locally compiled a few weeks ago on ! > Rel. 13.3 also works well. ! > ! > So I did verify: I restarted a Rel.13.3-p5, fetched all ! > prereqisite ports from backup (so these were also compiled on 13.3), ! > and then compiled firefox-esr-115.15.0,1, the very same that now ! > renders garbage, using the very same ports tree, with OS running ! > 13.3-p5. And that one now works! ! > ! > So bottomline is: ! > firefox-esr 115.15.0,1 - the one that was in 2024Q3 until about a ! > week ago - works correct when compiled on 13.3 (along with all it's ! > prereq ports), but renders garbage for a certain webpage when ! > compiled on 13.4-RC2 (along with all it's prereq ports). ! > ! > I don't like this, because now the question is: what else might 13.4 ! > compile so that it suddenly functions differently? ! > ! > ! > (I glanced thru PR 277021 - but it doesn't seem to mention anything ! > about webpages displaying broken, or any functional difference) ! > ! > Any idea how this might come to happen, anybody? ! ! Probably not related but I'll bring it up anyway; there was issue with ! firefox/other programs on alpine linux a couple weeks ago where the MESA ! package's upgrade in combination with using the link time optimization ! feature under gcc-14.x caused garbled previews and other graphical anomolies ! on my Firefox and my sway window manager. Hi Dan, thanks for Your feedback. This reflects what I happen to say: we're sitting on a huge pile of code, and almost nobody does still understand all the possible interdependencies - we only hunt them when something does visibly malfunction. In my case, this specific webpage brings along some 40k lines of CSS code, and from what I could figure out, firefox downloads them successfully, but then after a few hundred lines they are not applied any further. ! Not sure which compiler / mesa is used to build firefox on FreeBSD but could ! be part of the problem I guess or a place to look at the dependencies. It ! looks like they disabled LTO on the mesa build to fix the issue. That was ! using mesa-24.2.2. Firefox builds rust and llvm-17 from ports as prereq. It could be that these work someway different when built on 13.4. And that is exactly where my belly starts hurting: these compilers are used for other software too. From nobody Wed Sep 18 09:35:33 2024 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 4X7tmn6VBNz5Wp30 for ; Wed, 18 Sep 2024 09:35:37 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.osfux.nl (vm1982.osfux.nl [IPv6:2a03:5500:1724:55:79:99:187:212]) (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 4X7tmn1Vm0z4Yck for ; Wed, 18 Sep 2024 09:35:37 +0000 (UTC) (envelope-from mail@osfux.nl) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=osfux.nl header.s=default header.b=Sy9eFibz; dmarc=pass (policy=reject) header.from=osfux.nl; spf=pass (mx1.freebsd.org: domain of mail@osfux.nl designates 2a03:5500:1724:55:79:99:187:212 as permitted sender) smtp.mailfrom=mail@osfux.nl Received: from vm1982.osfux.nl (localhost [127.0.0.1]) by vm1982.osfux.nl (Postfix) with ESMTP id 8F1147F; Wed, 18 Sep 2024 11:35:34 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1726652134; bh=1cWcrSeKjUIGOSvzLQrEgUDV3Y7X10hhbE0yFEs1JmQ=; h=Date:Subject:From:To:References:In-Reply-To; b=Sy9eFibztZBPBFLnZDjuuMHrWFUf2haiCpzgNuEyaKL9a+AwNNfaqj4ttmVSxce3Q B6HVwIQCl4z6mFmBRSbAFA/MexUItWEceI0eDKtINIDgUYjIfGNsR0uaIDrsb0Z5Oe ji0UZoHbBgJB/4BF0RZxL71J3pPQLY+q8lGit1fQJk+aeratfOSgnIODllEpE0bklU P5VNhgJNt9jup25c8f6lTBpFS1KLjkik3dFGyw0y7nQ8L+h7ld64kp/DgizcC5PJ9+ F9P1nyJmLGi+azOjJe8lTQ15HjdE4prLAd4Oqcqss3vBGj734XY0djG4kQhhsKEmPC LR4PoGWPEt1y7MrInUvpK2mXu2XUOSBTCevTbVFVcyzkiT96VXN+p51mGVAqdrDUdv wEsmTeTdMxCoU3Rto1Wc9RvVu/aqdctmhGLL3GSRH8DkWuZPBKj9LceWeJ6yX2uxnv F8GmG4NnmyYeT5ow+ILJs36SAWH4oS9F00X6e4rVx0eFeTMYkZ6SVTdEmvaRN4yCRW f3V4CcIN64WYF2O90Vw/6MbCvX6lMw5DYw+PrQNc7eocIHm0FGndrFFAIduGhaE7A0 pI2JQblEbzIVBXnaaUyz+F5ZWZ08yakJXw2Hz1l98qhMbOEAa99SOC7RyphGVC5ED6 CWAMZzPCD/B2f03Lfc9jifQ8= X-Spam-Status: No, score=0.0 required=5.0 tests=none shortcircuit=no X-Spam-Checker-Version: SpamAssassin 4.0.0 Received: from [0.0.0.0] (unknown [193.187.128.159]) (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) (No client certificate requested) by vm1982.osfux.nl (Postfix) with ESMTPSA; Wed, 18 Sep 2024 11:35:34 +0200 (CEST) Message-ID: <0019d1f0-0b84-448d-8ecd-5b1619103139@osfux.nl> Date: Wed, 18 Sep 2024 11:35:33 +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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: issues with syslogd include redirecting wg0 output to custom location From: fuxjez To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-stable@freebsd.org References: <4250c967-61c7-419a-b542-455a8f655dd1@osfux.nl> Content-Language: en-US In-Reply-To: <4250c967-61c7-419a-b542-455a8f655dd1@osfux.nl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[osfux.nl,reject]; R_DKIM_ALLOW(-0.20)[osfux.nl:s=default]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:8315, ipnet:2a03:5500::/31, country:NL]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; TO_DN_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[osfux.nl:+] X-Rspamd-Queue-Id: 4X7tmn1Vm0z4Yck Hi, I ended up replacing : *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages with !-wg0 *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages !wg0 in /etc/syslog.conf and placing this: # Log wgX messages :msg, ereregex, "wg[0-9]{1,2}\:\ " *.* /var/ramdisk_log/wireguard.log in /etc/syslog.d/wireguard.conf (TnX Bob for pointing out the issues with my previous attempts). I'm probably filtering out too much information with the "!-wg0 construction" (regular, non-debug information regarding wgX interfaces for instance) but at this point I'm satisfied with the construction. Thank you for your feedback Miroslav / Bob! Regards, ruben From nobody Wed Sep 18 16:04:56 2024 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 4X83QB6tkQz5WhjM for ; Wed, 18 Sep 2024 16:05:06 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4X83QB13DNz4PXB for ; Wed, 18 Sep 2024 16:05:05 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=catflap.org; spf=pass (mx1.freebsd.org: domain of jamie@catflap.org designates 2001:19f0:7400:8808:123::1 as permitted sender) smtp.mailfrom=jamie@catflap.org X-Catflap-Envelope-From: X-Catflap-Envelope-To: freebsd-stable@FreeBSD.org Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 48IG4vbe023402; Wed, 18 Sep 2024 17:04:57 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 48IG4u74023401; Wed, 18 Sep 2024 17:04:56 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202409181604.48IG4u74023401@donotpassgo.dyslexicfish.net> Date: Wed, 18 Sep 2024 17:04:56 +0100 Organization: Dyslexic Fish To: mail@osfux.nl, freebsd-stable@FreeBSD.org Subject: Re: issues with syslogd include redirecting wg0 output to custom location References: In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Wed, 18 Sep 2024 17:04:57 +0100 (BST) X-Spamd-Result: default: False [-1.36 / 15.00]; NEURAL_HAM_SHORT(-0.66)[-0.660]; DMARC_POLICY_ALLOW(-0.50)[catflap.org,none]; R_SPF_ALLOW(-0.20)[+mx:dyslexicfish.net]; MIME_GOOD(-0.10)[text/plain]; RCVD_NO_TLS_LAST(0.10)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; HAS_ORG_HEADER(0.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US]; FREEFALL_USER(0.00)[jamie]; MIME_TRACE(0.00)[0:+]; TO_DN_NONE(0.00)[]; ARC_NA(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-stable@FreeBSD.org] X-Rspamd-Queue-Id: 4X83QB13DNz4PXB X-Spamd-Bar: - > :msg, contains, ".*wg0: .*" > *.* /var/ramdisk_log/wireguard.log It works for me. Presumably your use of regex patterns is the problem: +* !* :msg, contains, "wg0:" *.* /tmp/smeg From nobody Wed Sep 18 22:59:06 2024 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 4X8Dbx3WQYz5W8xh for ; Wed, 18 Sep 2024 22:59:09 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (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 4X8Dbx1Bp5z3xf2 for ; Wed, 18 Sep 2024 22:59:09 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=citron; t=1726700347; x=1727367013; h=date:author:from:to:cc:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: author:from:subject:date:to:cc:resent-author:resent-date:resent-from: resent-sender:resent-to:resent-cc:resent-reply-to:resent-message-id: in-reply-to:references:mime-version:content-type: content-transfer-encoding:content-disposition:content-id: content-description:message-id:mail-followup-to:openpgp:blahblahblah; bh=spHwSB6l/3lhoFB5RWdamEfwixdT2Vc6dV+z8zOoo+s=; b=awxY5fUgCPVFu/RXOngjt9WZ8KOJyju2jalh+HzadXBCWN5fCWPy8lOKU5B+IKzFBTz0j4ZR aeaYC+IyPnY/06drvPI6OhhMWPDsyrXv7cQDU2nEDsnd7PGKIASnQurF59qBiovVkr7dl78+M2 9nr+BjMKrXtpgHNCVrNB3VLRZOo6FB3DyKkvAQEt1ufuzp6bq5AiDLqD0qUQiWJwE+kQvlwDRX oFuwZ6XdvFMM4g3shuNNG6WFzNYAHLBDuEOuNlMJYhT5dGeIFTGJvQsUwQhYN8wUvrgaeeleDz fcChbz5cDYqp/y03Q84fwOIkSdnXCTq9savAlUBkL/FteX8Q== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=orange; t=1726700347; x=1727367013; h=date:author:from:to:cc:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: author:from:subject:date:to:cc:resent-author:resent-date:resent-from: resent-sender:resent-to:resent-cc:resent-reply-to:resent-message-id: in-reply-to:references:mime-version:content-type: content-transfer-encoding:content-disposition:content-id: content-description:message-id:mail-followup-to:openpgp:blahblahblah; bh=spHwSB6l/3lhoFB5RWdamEfwixdT2Vc6dV+z8zOoo+s=; b=8jlR+kEh+NMQK06LdBQVHq4rnOTilBAyR5Dh+nQ/joPBuzcwyF5vCB7jWjxYt8S/fqhvT+3y dF5ZnRn/BgvhCQ== Date: Thu, 19 Sep 2024 00:59:06 +0200 Author: Steffen Nurpmeso From: Steffen Nurpmeso To: fuxjez Cc: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-stable@freebsd.org Subject: Re: issues with syslogd include redirecting wg0 output to custom location Message-ID: <20240918225906.Npft_PNY@steffen%sdaoden.eu> In-Reply-To: <0019d1f0-0b84-448d-8ecd-5b1619103139@osfux.nl> References: <4250c967-61c7-419a-b542-455a8f655dd1@osfux.nl> <0019d1f0-0b84-448d-8ecd-5b1619103139@osfux.nl> Mail-Followup-To: fuxjez , Miroslav Lachman <000.fbsd@quip.cz>, freebsd-stable@freebsd.org User-Agent: s-nail v14.9.25-608-ge479530e8d OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15987, ipnet:217.144.128.0/20, country:DE] X-Rspamd-Queue-Id: 4X8Dbx1Bp5z3xf2 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated 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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org fuxjez wrote in <0019d1f0-0b84-448d-8ecd-5b1619103139@osfux.nl>: It is on Linux aka iptables, and maybe the implementations differ in that respect, but i have super strict rules for my WireGuard ports, which is easy because WireGuard moves established connections to different ports (and to outside "normal" FILTER table matching, aka, they become "invisible" to these rules). Like that i can allow some tries in a certain amount of time, otherwise (log and) block the source, without any textual log parser doing work behind the scenes. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) From nobody Wed Sep 18 23:09:01 2024 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 4X8DqP2fKbz5WBRD for ; Wed, 18 Sep 2024 23:09:05 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X8DqN1YCLz41GM for ; Wed, 18 Sep 2024 23:09:04 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=sdaoden.eu header.s=citron header.b=RzzhxW6a; dkim=pass header.d=sdaoden.eu header.s=orange header.b=PQnifSfF; dmarc=none; spf=pass (mx1.freebsd.org: domain of steffen@sdaoden.eu designates 217.144.132.164 as permitted sender) smtp.mailfrom=steffen@sdaoden.eu DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=citron; t=1726700943; x=1727367609; h=date:author:from:to:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: mime-version:content-type:content-transfer-encoding:author:from:subject: date:to:cc:resent-author:resent-date:resent-from:resent-sender:resent-to: resent-cc:resent-reply-to:resent-message-id:in-reply-to:references: mime-version:content-type:content-transfer-encoding:content-disposition: content-id:content-description:message-id:mail-followup-to:openpgp: blahblahblah; bh=3ytmLrDAhcMv38q5F+xVw/qKxo5dTYqMzdOLHY1iT74=; b=RzzhxW6a/9/r238c0raKJeUHhox+f8hJDZOuvflL4hUbr5Zd+8WiebdMOG4UqUFIrzqj+DG1 nSge3E+F19bcv2Sf7ljOfD/IVSELG6bvyz6DFC6/ceJSNM8ceshzb5cuG1omLrucvcKxmdtpUR hFWOyEOwBzsqIB6q09HXH04Tu5KnRyOQ/2Tj0NWaRQ+PQ3kSlVYdit1uoxvR72GSUQfI7elM0t T1jNLaRq9gZRpeNyztwA0TK0VPBxRncnJ2cUZbRLuU000n4h2kclw4+UBXpeNzZdvqiQGK594l 8rzUcO0EJhLez/eYjpFSnvmMQX0OGkHGqIfjElRwp4Xvso5g== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=orange; t=1726700943; x=1727367609; h=date:author:from:to:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: mime-version:content-type:content-transfer-encoding:author:from:subject: date:to:cc:resent-author:resent-date:resent-from:resent-sender:resent-to: resent-cc:resent-reply-to:resent-message-id:in-reply-to:references: mime-version:content-type:content-transfer-encoding:content-disposition: content-id:content-description:message-id:mail-followup-to:openpgp: blahblahblah; bh=3ytmLrDAhcMv38q5F+xVw/qKxo5dTYqMzdOLHY1iT74=; b=PQnifSfF9Q2yy/WvCgB3Ag/j5/p3F2Ls9fL6Xac7Tgt79bbjNQCSOxUw5hd09/vjvmoJYepH h3cnEW77Oo5TDQ== Date: Thu, 19 Sep 2024 01:09:01 +0200 Author: Steffen Nurpmeso From: Steffen Nurpmeso To: fuxjez Subject: Re: issues with syslogd include redirecting wg0 output to custom location Message-ID: <20240918230901.P2V-MyI6@steffen%sdaoden.eu> In-Reply-To: <20240918225906.Npft_PNY@steffen%sdaoden.eu> References: <4250c967-61c7-419a-b542-455a8f655dd1@osfux.nl> <0019d1f0-0b84-448d-8ecd-5b1619103139@osfux.nl> <20240918225906.Npft_PNY@steffen%sdaoden.eu> Mail-Followup-To: fuxjez User-Agent: s-nail v14.9.25-608-ge479530e8d OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. 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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-2.41 / 15.00]; NEURAL_HAM_MEDIUM(-0.98)[-0.977]; NEURAL_HAM_SHORT(-0.93)[-0.935]; R_SPF_ALLOW(-0.20)[+a]; R_DKIM_ALLOW(-0.20)[sdaoden.eu:s=citron,sdaoden.eu:s=orange]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15987, ipnet:217.144.128.0/20, country:DE]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; DMARC_NA(0.00)[sdaoden.eu]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[sdaoden.eu:+] X-Rspamd-Queue-Id: 4X8DqN1YCLz41GM X-Spamd-Bar: -- Ha. Steffen Nurpmeso wrote in <20240918225906.Npft_PNY@steffen%sdaoden.eu>: I got back : host vm1982.osfux.nl[79.99.187.212] said: 554 5.7.1 Serv= ice unavailable; Client host [217.144.132.164] blocked using sbl.spamhaus= .org; Error: open resolver; https://check.spamhaus.org/returnc/pub/141.101.= 75.8/ (in reply to RCPT TO command) Which somehow got me going .. and *they* say in turn Your email has bounced back from the recipient Public resolver If you are viewing this page, you have likely sent an email that was not = delivered to the recipient. In the resulting bounced email message you have= found and clicked this link: https://check.spamhaus.org/returnc/pub/141.10= 1.75.8 The problem doesn=E2=80=99t relate to your email set-up. ^Good. Why has my email not been delivered? The problem is with the recipient=E2=80=99s email server configuratio= n. This is not due to an issue with your email set-up. It is not because you are listed on one of our blocklists.=20 ^That is what i wanted to know, thank you. What do I need to do next? If the email is urgent or essential: Call the recipient and tell them that they have an issue with receivi= ng emails. Ask the recipient to urgently contact their email server administrato= r. This page provides the information required to correct this issue: Using= our public mirrors? Check your return codes now. For non-urgent emails Try and resend the email in 24 hours, allowing the recipient=E2=80=99s= email administrators time to resolve the problem.=20 Want more technical details? We=E2=80=99ve provided the above information for the everyday email user;= however, if you=E2=80=99re technically minded and want to learn more, keep= reading=E2=80=A6 Queries cannot successfully be made to the Spamhaus free = infrastructure via public/open resolvers. This is to protect the infrastruc= ture from abuse by large-volume queriers. If you=E2=80=99d like to take a d= eeper dive into this, check out successfully accessing Spamhaus=E2=80=99 fr= ee blocklists using a public DNS. Some users continue to query Spamhaus blo= cklists via public resolvers, unaware that this means that our data does no= t actually protect their mail stream. We have introduced an error code for = these users to provide a clear signal that there is an issue, and that the = mailserver configuration needs to be updated. A free upgrade: Spamhaus DQS To succesfully query Spamhaus via public/open resolvers, there is a FREE = service which delivers the intelligence faster and with additional blocklis= ts available to increase catch-rates: Spamhaus Data Query Service. Here are= the details of how to make the change: Sign up for the free Spamhaus Data Query Service. The same usage term= s apply. Make the relevant change to your server configuration. The Spamhaus T= echnical Documentation site has full configuration details for many mail se= rvers and anti spam solutions.=20 Alternatively, if you=E2=80=99d like to continue using the free public in= frastructure, please ensure that your queries come from a dedicated IP with= attributable reverse and forward DNS. Here is information on how to correc= tly configure commonly used MTAs for use with the public mirrors. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) From nobody Thu Sep 19 08:17:33 2024 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 4X8T0R72PRz5XVdr for ; Thu, 19 Sep 2024 08:17:43 +0000 (UTC) (envelope-from joachim@durchholz.org) Received: from www382.your-server.de (www382.your-server.de [78.46.146.228]) (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 4X8T0Q73tBz49cl for ; Thu, 19 Sep 2024 08:17:42 +0000 (UTC) (envelope-from joachim@durchholz.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=durchholz.org header.s=default2202 header.b=T5qZV2fp; dmarc=none; spf=pass (mx1.freebsd.org: domain of joachim@durchholz.org designates 78.46.146.228 as permitted sender) smtp.mailfrom=joachim@durchholz.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=durchholz.org; s=default2202; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:From:References:To:Subject:MIME-Version:Date:Message-ID:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=Uzl0Q6mDYJ6TyheoN5AUC94hYX3zNGdlAtEWzQDgjeE=; b=T5qZV2fp3m7Ndj0EZztGEo+ZQP vipCof8Bqn5xdHHgGGbVMqyTAKVnvtV2ylTTeVCgp52tsJEJDVg1nqI3timKx3ckPVdPeTAD26o2J 6e/RgKebm8ihKUEPYnxTIzCALVIEwvpKvbC8Ena2TBtnn4QFh/kVaqV0piRunKsJvdnjq0fcjT5xX V69q0MdPhtKZ96vjzA4yuPYDJ/nyTnJ7/sFZ2+XFVWIo407vH9ffNbgsPh3O69WGRgsdDp1buco2j h5RORrw8oq8lB0F1gS3HuH78YTGk7BxApfxhDDDzECN4b7LEr3e++qQQiUKAJO2M9o22A85ZnwoYp n+qKMTpg==; Received: from sslproxy07.your-server.de ([78.47.199.104]) by www382.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1srCM2-0007tO-OE for stable@freebsd.org; Thu, 19 Sep 2024 10:17:34 +0200 Received: from [81.221.201.210] (helo=[192.168.178.48]) by sslproxy07.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1srCM1-0008Sn-1c for stable@freebsd.org; Thu, 19 Sep 2024 10:17:33 +0200 Message-ID: <627f0b4f-6d55-4872-9435-07109a9a6aa0@durchholz.org> Date: Thu, 19 Sep 2024 10:17:33 +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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: issues with syslogd include redirecting wg0 output to custom location Content-Language: en-US, de-DE To: stable@freebsd.org References: <4250c967-61c7-419a-b542-455a8f655dd1@osfux.nl> <0019d1f0-0b84-448d-8ecd-5b1619103139@osfux.nl> <20240918225906.Npft_PNY@steffen%sdaoden.eu> <20240918230901.P2V-MyI6@steffen%sdaoden.eu> From: Joachim Durchholz In-Reply-To: <20240918230901.P2V-MyI6@steffen%sdaoden.eu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Sender: jo@durchholz.org X-Virus-Scanned: Clear (ClamAV 0.103.10/27402/Wed Sep 18 12:32:17 2024) X-Spamd-Result: default: False [-3.49 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.996]; R_SPF_ALLOW(-0.20)[+a]; R_DKIM_ALLOW(-0.20)[durchholz.org:s=default2202]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:24940, ipnet:78.46.0.0/15, country:DE]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[durchholz.org]; HAS_X_AS(0.00)[]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[stable@freebsd.org]; DKIM_TRACE(0.00)[durchholz.org:+] X-Rspamd-Queue-Id: 4X8T0Q73tBz49cl X-Spamd-Bar: --- On 19.09.24 01:09, Steffen Nurpmeso wrote: > Ha. > > Steffen Nurpmeso wrote in > <20240918225906.Npft_PNY@steffen%sdaoden.eu>: > > I got back > > : host vm1982.osfux.nl[79.99.187.212] said: 554 5.7.1 Service > unavailable; Client host [217.144.132.164] blocked using sbl.spamhaus.org; > Error: open resolver; https://check.spamhaus.org/returnc/pub/141.101.75.8/ > (in reply to RCPT TO command) Oh, that's a problem on vm1982.osfux.nl, who rely on Spamhaus to identify IP addresses that have sent spam in the past. Spamhaus is pretty well-known for being unreliable; the spam filters in your mail client work much better, and if they misclassify a mail you can easily find it in the spam folder instead of rejecting the mail and making life difficult for the admin on the sending side. Regards, Jo From nobody Thu Sep 19 08:55:40 2024 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 4X8TrQ37h3z5Vcth for ; Thu, 19 Sep 2024 08:55:50 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.osfux.nl (vm1982.osfux.nl [IPv6:2a03:5500:1724:55:79:99:187:212]) (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 4X8TrP5PsVz4Hpn for ; Thu, 19 Sep 2024 08:55:49 +0000 (UTC) (envelope-from mail@osfux.nl) Authentication-Results: mx1.freebsd.org; none Received: from vm1982.osfux.nl (localhost [127.0.0.1]) by vm1982.osfux.nl (Postfix) with ESMTP id 0B24A7F; Thu, 19 Sep 2024 10:55:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1726736141; bh=doI7cKPls5fvB7l6zPSsKjOqKgDAGiE1dD6AE6Ec764=; h=Date:Subject:To:References:From:In-Reply-To; b=QW+8fIr/h6GdBq9RjLtCYvQ4YBaO118Yragm4IZevrrw4+pErNfr+tZm1BU5u63aO IyeJWYqxto8gRVDA0MNzLlsIKvnYcjazmDo2OB+Za+724GDNBzN3Itk+PvcjMkn3oJ M5csardRW/2v655kowhgEjTynb6dg6MX9ZjSl+v2CErg5YXvr34mibutWk6mNTvwPC ol9lqY0esCIEemP1EX6r4+DV1mszilqFMZjFiP4Y3Sxgjz/O7PbKu4KTd62u/Ct/Da KdFHU3Y4rAGEIHR8droF/OOMQtqHZVS7UXxFmanDUqvPwXHiIn01Xi1i4PJnap61h4 PVxnojOJmIDHmbRfhVjB4dDgTkmgtqnyDMlmU6OCIsxvId31FafGRFvBBgdmMrPsXF vnuomp0U3r9uv5yj+TUbM38/BtNUX4rJh0VEu4xtCPUPJuf/Zm+wK9Fy2+cbobl1fI 3yIqGGnzxjxecHxcf4UZCbeVBGX32VjS4PHYIhj6BL9xqOFxE0rqpkHECHI1TlN8sc YeRmeQsIioiFplQmVyOcawRYAB2HqAj5nCn47R9vY9q5td6wvBDhcUPvjCTiwMz8nA WMORkObP90m8F0CrGojh4mzXprjP289/3IU5uw0FzuV+B4VfUyznFckOpMQRTgdSww zdyWarVP8DRCGrXU5QX5b5pw= X-Spam-Status: No, score=0.0 required=5.0 tests=none shortcircuit=no X-Spam-Checker-Version: SpamAssassin 4.0.0 Received: from [0.0.0.0] (unknown [193.187.128.159]) (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) (No client certificate requested) by vm1982.osfux.nl (Postfix) with ESMTPSA; Thu, 19 Sep 2024 10:55:40 +0200 (CEST) Message-ID: Date: Thu, 19 Sep 2024 10:55:40 +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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: issues with syslogd include redirecting wg0 output to custom location To: stable@freebsd.org, joachim@durchholz.org, steffen@sdaoden.eu References: <4250c967-61c7-419a-b542-455a8f655dd1@osfux.nl> <0019d1f0-0b84-448d-8ecd-5b1619103139@osfux.nl> <20240918225906.Npft_PNY@steffen%sdaoden.eu> <20240918230901.P2V-MyI6@steffen%sdaoden.eu> <627f0b4f-6d55-4872-9435-07109a9a6aa0@durchholz.org> Content-Language: en-US From: fuxjez In-Reply-To: <627f0b4f-6d55-4872-9435-07109a9a6aa0@durchholz.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8315, ipnet:2a03:5500::/31, country:NL] X-Rspamd-Queue-Id: 4X8TrP5PsVz4Hpn X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated Hi Joachim/Steffen, That specific check was causing issues some time ago as well, removed it from my mail setup. Thanks for your feedback :) ruben On 9/19/24 10:17, Joachim Durchholz wrote: > On 19.09.24 01:09, Steffen Nurpmeso wrote: >> Ha. >> >> Steffen Nurpmeso wrote in >>   <20240918225906.Npft_PNY@steffen%sdaoden.eu>: >> >> I got back >> >>    : host vm1982.osfux.nl[79.99.187.212] said: 554 >> 5.7.1 Service >>        unavailable; Client host [217.144.132.164] blocked using >> sbl.spamhaus.org; >>        Error: open resolver; https://check.spamhaus.org/returnc/ >> pub/141.101.75.8/ >>        (in reply to RCPT TO command) > > Oh, that's a problem on vm1982.osfux.nl, who rely on Spamhaus to > identify IP addresses that have sent spam in the past. > Spamhaus is pretty well-known for being unreliable; the spam filters in > your mail client work much better, and if they misclassify a mail you > can easily find it in the spam folder instead of rejecting the mail and > making life difficult for the admin on the sending side. > > Regards, > Jo > From nobody Thu Sep 19 11:06:59 2024 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 4X8Xlx33gnz5WFJF for ; Thu, 19 Sep 2024 11:07:09 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.osfux.nl (vm1982.osfux.nl [79.99.187.212]) (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 4X8Xlw36v0z4bgW for ; Thu, 19 Sep 2024 11:07:08 +0000 (UTC) (envelope-from mail@osfux.nl) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=osfux.nl header.s=default header.b=ciLaS77b; dmarc=pass (policy=reject) header.from=osfux.nl; spf=pass (mx1.freebsd.org: domain of mail@osfux.nl designates 79.99.187.212 as permitted sender) smtp.mailfrom=mail@osfux.nl Received: from vm1982.osfux.nl (localhost [127.0.0.1]) by vm1982.osfux.nl (Postfix) with ESMTP id BA5C180 for ; Thu, 19 Sep 2024 13:06:59 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1726744019; bh=GJYZSEX7izS/44WZcKfu8o+W11Lsj/zaf18fmIphb20=; h=Date:To:From:Subject; b=ciLaS77b6ne5fC34q6wbeid0+PpP/DZCprI7IChS52UWh6xjo9bF3puGVvY/wKQop lUrZm7BQaYuzVTtZoSTi26tqHLDKKCYQFrK+UzQ8Ormb0nqdN0YmOkAJLv9kMo9VuH mCz5HkOCmtb/UvZf6+3ONKrhs2A+IPDcWuTSnGbqiofzM+g2X8TXG6YKgpVRweoLvS vk3hnA4UyultyvmDQROMQcYZ2vQm/TV45S+wwY3DNYfsmoSBMUmQtbNzgNcsQz0tud GAXFqthK59G20Ivy659CFo56nJU0n5GqbFRUZSYm0YwUY5lZEyZtJBTI/yFnsEk5SI OKmbC8iH12TehrWoDGR+kR5nsUeYCW674FgTf9VEOlyeYIVjyZg/bNuX0ERTvlqrkC 8/x3/o7VszikpMxEFhqLolj3kaQy+w53h9wMmNax81p+UH2XJa64OyPzkGk+/2B1Q3 HjPBTr9kNGzLW6yB+H816Wa3w2Ik/8b6pMnNGZw7j48uGw6bABJnlhVQU9BJxozBUk JbGNu62qAIGvgYFpUneYTAxhkY0hmfcm41bzQ8tgKPf6eEbRMg+Tbtnnvhq5vt9DJL q1jXJK2QMGaXKPkX8NA74YygusTdgulJExty3kSrK35g6/5bFrVywsYXqeO1qaRE/t Rns6zJS8FAgYbFxL772pXebw= X-Spam-Status: No, score=0.0 required=5.0 tests=none shortcircuit=no X-Spam-Checker-Version: SpamAssassin 4.0.0 Received: from [0.0.0.0] (unknown [193.187.128.159]) (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) (No client certificate requested) by vm1982.osfux.nl (Postfix) with ESMTPSA for ; Thu, 19 Sep 2024 13:06:59 +0200 (CEST) Message-ID: Date: Thu, 19 Sep 2024 13:06:59 +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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: freebsd-stable@freebsd.org From: fuxjez Subject: Controlling verbosity of wireguard logs Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[osfux.nl,reject]; R_DKIM_ALLOW(-0.20)[osfux.nl:s=default]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:8315, ipnet:79.99.184.0/21, country:NL]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; DKIM_TRACE(0.00)[osfux.nl:+] X-Rspamd-Queue-Id: 4X8Xlw36v0z4bgW X-Spamd-Bar: --- Hi List, Somebody managed to get Wireguard logging running vebosely on 14.1? I've tried setting the LOG_LEVEL (mentioned in the wg 8 manpage, albeit directed at "userspace implementations") to debug, but I wasn't able to identify any ip information (for instance) looking at the debug information generated :( I've only managed to find information regarding linux WG implementations that generate verbose logging ( https://superuser.com/questions/1774092/wireguard-connectivity-between-handshakes for instance ). On FreeBSD 14.1 I've tried enabling the debug logging required like this: === LOG_LEVEL=verbose /sbin/ifconfig wg0 debug LOG_LEVEL=DEBUG /sbin/ifconfig wg0 debug LOG_LEVEL=debug /sbin/ifconfig wg0 debug === but the only generated messages I'm seeing are regarding wireguard handshakes / wireguard keepalive functionality. I tried simulating faulty connection attempts by connecting to the wg endpoint using an "invalid" publickey. With LOG_LEVEL=debug this only generates: wg0: Invalid initiation MAC messages in the logs. I'm after the source ip addresses that fail to establish correct crypto with this servers' wg endpoint so the messages do not contain sufficient information for my purposes. Any thoughts? Feedback appreciated! ruben From nobody Thu Sep 19 17:16:43 2024 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 4X8hyX233Wz5Wcwv for ; Thu, 19 Sep 2024 17:16:52 +0000 (UTC) (envelope-from mack@macktronics.com) Received: from mail.macktronics.com (coco.macktronics.com [209.181.253.65]) (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 4X8hyV3S5Gz42FR for ; Thu, 19 Sep 2024 17:16:50 +0000 (UTC) (envelope-from mack@macktronics.com) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=macktronics.com; spf=pass (mx1.freebsd.org: domain of mack@macktronics.com designates 209.181.253.65 as permitted sender) smtp.mailfrom=mack@macktronics.com Received: from olive.macktronics.com (olive.macktronics.com [209.181.253.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.macktronics.com (Postfix) with ESMTPS id C814E11F7; Thu, 19 Sep 2024 12:16:43 -0500 (CDT) Date: Thu, 19 Sep 2024 12:16:43 -0500 (CDT) From: Dan Mack To: sthaug@nethelp.no cc: bzeeb-lists@lists.zabbadoz.net, freebsd-stable@freebsd.org Subject: Re: BIND 9.19.24 not listening to rndc port (953) In-Reply-To: <20240702.191333.1782316333681428598.sthaug@nethelp.no> Message-ID: <35410f21-8e52-a853-ad21-4fd05d0f8b3c@macktronics.com> References: <38321p06-q966-p811-oqpq-q679qpo9pp31@yvfgf.mnoonqbm.arg> <20240702.112250.268297637701792446.sthaug@nethelp.no> <18s0oq25-816s-84ns-41np-47402182ns46@yvfgf.mnoonqbm.arg> <20240702.191333.1782316333681428598.sthaug@nethelp.no> 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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Spamd-Result: default: False [-1.66 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_LONG(0.99)[0.992]; NEURAL_HAM_SHORT(-0.95)[-0.952]; DMARC_POLICY_ALLOW(-0.50)[macktronics.com,none]; R_SPF_ALLOW(-0.20)[+ip4:209.181.253.64/29]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:209, ipnet:209.181.252.0/23, country:US]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_NONE(0.00)[]; RCPT_COUNT_THREE(0.00)[3] X-Rspamd-Queue-Id: 4X8hyV3S5Gz42FR X-Spamd-Bar: - On Tue, 2 Jul 2024, sthaug@nethelp.no wrote: >>> So we set uid 53 (bind) at 0.083518302, and then try to bind to port >>> 953 at 0.093282161. >> >> Are you going to poe a bug with the bind people? > > Already did: https://gitlab.isc.org/isc-projects/bind9/-/issues/4793 > > Steinar Haug, AS2116 Probably everyone knows but this still happens in the bind920-9.20.1 package. However, BIND 9.20.2 was released yesterday with a change to when bind drops privilege levels so perhaps we will have a working version when the port / package is updated. Dan From nobody Thu Sep 19 18:00:28 2024 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 4X8jwz2RnLz5WkGd for ; Thu, 19 Sep 2024 18:00:35 +0000 (UTC) (envelope-from matthew@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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X8jwz1yThz47hD for ; Thu, 19 Sep 2024 18:00:35 +0000 (UTC) (envelope-from matthew@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1726768835; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:autocrypt:autocrypt; bh=udZA8dnf2qhUPN/M8lokwf8aL4BwVh5ULUnICyt+tNU=; b=LIm3qdS3AUSwZlJRI/2BP1gzC/2y4UJOVog7dhTAJU/4AFf6xJdfHoB5xuXsYQK3QcXlc/ 0qQHG8F3UaOwreKGyQ56TQ8dP1MZgqAky+CMFSGBadPyd7AHuqQo+lXrZhFiNB194krBLI mYysc8npVgy2jJUQCYWcY72JH3PDKmLh6iU/Cdc+ManYih3pUub5pTV9LM5p0qXAURTXB6 PAjbtlwg0P8PKbctSu+UEZfQMY60mpPFyaTyHT8dfE52Q2m6C7uPBdX7D+uk6Zl5dXuQm4 0I9dhPm/rvxRr9zUxvMrN/MmLB2E3ePubchinGz8+WsHi7PZnqYHG5zJ/+EpwA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1726768835; a=rsa-sha256; cv=none; b=qX2YU/Bh1BZNJQzSW68o71d9Ri5KhPF2zqHYMI+VcgOyzm3BSclcaIYMgsP7DgMGziBSRf rkTFqUR/IyQE27VoajW/EE/cRamuVRRofzAK1tqrdGym08heiEwD1hnthpAQFkNqxSMdQT dFganmkeTy05tmZngohR1NCmDIfQLKHtEBbe8sR2GIU0MkdBOkjGV3A2DtjPPTBwjFdLoY O34JGmAmaAclZh/ySP6w0h05ZqH4gDE1VRHu0AYvTwtdLn10+39QBXsdxX7JIqPklvaGc/ fnJUUCm5BWojwSo+KB4/3vPF8GqjATwKkoIeFhQa/ACkQWMA/Em9z0NJhlAFkA== ARC-Authentication-Results: i=1; smtp.infracaninophile.co.uk; dmarc=fail (p=none dis=none) header.from=FreeBSD.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1726768835; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:autocrypt:autocrypt; bh=udZA8dnf2qhUPN/M8lokwf8aL4BwVh5ULUnICyt+tNU=; b=XsswePHFcVpukNAmnb4Dw1ATEaLhrFaEkS3hpOD7FBwUZrg7VXU2Im7ymwgDoK0G1IjkJ6 WrXE9hHvWoxz0ctNR/XNlEcbReSTmFMb+6x7360PKPu4ooR/iHA+Ox/CUQyeV2BMJfuMpK tsCrH24Te10gDytPPreLLYszHwE7x51GGjGsUuvhXkmDiEDockUIp9rtnNg/pbhvZU5nzp c0JMSWQQo13O4gZgWJRNBfXXPN80O0yU4AZtDgLlMo7vltEYfh0XNNBvcpF07HpR7il+QT RzqwvX4UP43yjW1QLlCEOkpVzYMhqloxhQmsq+4L7G9KZYmUh1YAj3ES4q8O+w== Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (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) (Authenticated sender: matthew/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4X8jwz0pVmz14m0 for ; Thu, 19 Sep 2024 18:00:35 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from [172.16.10.199] (unknown [185.57.101.147]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 1CE2AA29C for ; Thu, 19 Sep 2024 19:00:29 +0100 (BST) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=fail (p=none dis=none) header.from=FreeBSD.org Message-ID: Date: Thu, 19 Sep 2024 19:00:28 +0100 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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: BIND 9.19.24 not listening to rndc port (953) Content-Language: en-GB To: stable@freebsd.org References: <38321p06-q966-p811-oqpq-q679qpo9pp31@yvfgf.mnoonqbm.arg> <20240702.112250.268297637701792446.sthaug@nethelp.no> <18s0oq25-816s-84ns-41np-47402182ns46@yvfgf.mnoonqbm.arg> <20240702.191333.1782316333681428598.sthaug@nethelp.no> <35410f21-8e52-a853-ad21-4fd05d0f8b3c@macktronics.com> From: Matthew Seaman Autocrypt: addr=matthew@FreeBSD.org; keydata= xsFNBFJIL80BEADi7/VbnnErDU6pjEhI/SzEZ/HbDRkJ5g7HroAtqIRm6nj8ZwOAgZ/2ZnWn 5F+fXTuLsG0FLNtkd17FoVcuCi5e/GPliXI5cmamV7E1Yz4T8UsJ7RQolimyxVexccKd16Tc AA7B9bFlJSKkBUSD0buj7VjT07xWhRzu6Vgi5r0UjLALYJz977uZA0F1aOGOXREDEAOhdcNc kSNjynqAwDA6dCT1Elpi4key1fYjv4jyDF+GU/YXul2Y/rguA8FCkHd9vyym5eAsLQ5mG00V V9fkEHIpH5KorNVnl/ufHXnkZqmHAZVpFDcrshb7aZ/pL45PXyWgLj+e6etelgj3a2bZi0JF cVdXCnBZVP2oIyYblM11ugTbfCwodORU8a5KfPeztMdAtDr4e+32NTrPdPi5rLT+GUsYz+PL 3A3m3u8bdsFp40DlIrBtSByVjqERxcfhphrEB4J8BXHUG7OAtXkZMlW/PGKDwXJq0O6Z5Tcg YHAoEiSWbXiexHgXNJyP+sqnIlhLWhSJGeJ+C83wqI6oYlZUCW00NkPxcIHnQPV/z+5wQVci TMyaWC2YCIHz4Ljs+TnwWMz0E8PNFDfHVbQ0W4PRGV7gRAqxfL+yKufauIEGbEq8rNDbSwL3 bcUCxR4ZDlaUEUwT4J8naf7rjdgiEYHs2Ig3jeK1+ER4FPG1sQARAQABzSRNYXR0aGV3IFNl YW1hbiA8bWF0dGhld0BmcmVlYnNkLm9yZz7CwZQEEwEKAD4CGwMFCwkIBwMFFQoJCAsFFgMC AQACHgECF4AWIQRyz6whebywJLW1RZADb2ye5/OevwUCZidQVgUJFcBUAQAKCRADb2ye5/Oe v7hXD/sHeYOYYCQsv8urMfbQCjUXPgP9UzPVBDudVT4VlPjsg4kRzTJC4aCDcpV1s5kVaMc3 nDN1TOOjV8Fmo3kFCsoow8U+uqX3+41ODPG01/i7+SDtCABhDlXtRPpFPsN0O/wdwWz6URV8 Pcfb3Uvo7hqgMWhaLfzdJeSdbZoU3qU5nGYcRrW4ojYCUKYCICmnG9af3H4RDSUzhxpcvUiG Gf0eiO6j80YYFx4kAyL6g2IkRSQ+HYAJc8bX4z/unJqBP154PxcHPvyLIQjYouDHTE0EX/Kw tIk1uwFuOWeC417ZinJuI5/Fsei8COmb7+axIDeqt+63ytxZAB3fiK3V1qmQwBf+H3H3fuXe 7cd9NML8gbXRsjRBzuKDsHfJyJwNU47DlbRXhUlWALfawCndU8Ka+4FbhS5WfO7m/bd3/A0k 6gqnUhRr07V1kds25gIwyBjvUF2MdCkdk3VrzEmU5oXBI9jfBK3s0j8DXESWHKJTf5hwmGDX 6rjzyRh0Nv9ZVQYFUwypBAP4koklZLEjh8Gme7dr3qbmcl+r1pBD6M6EFYfFqDI3kr7FwH0e wsspX6FoX+OPBMsit4CmqR4T2HuTD0ayn5kMQk9lmScJNVjdoLH1yf/KDFBfKuAL+gOyaKnB lGmbEfSqsXCnBue8wfDZOxr4bxQFg+HQ88YdH6032s7BTQRSUUK4ARAA1FhWoOejtwmsnGsh oIbda2FmM+z/f97OzpagLhACHfP5Es/I18wG/0G+rdNuO2tjA9IMZ44GUMtjokDrDk63N9S+ rVKy1QEy+UN6CiIfYTpTTAPnEY7IGN1JjGksPhn7aeuBCQwUMAV1k+wklBCcOD6s8DD4kx0Z JqkH83XzWoBSVamdHvnM56C8yPVr5HHMC1tZInAWBMrF+cjl1EPfz3CqkVnG8Sxc5ydeibMS 9Q3lHLeVkVlMRAmNqzNLfgJDUWtzac7JIjFEsxYYhpiaPcsstUUuHa4zIRJ/yHDNbDttWRf1 lrlFZLpeuap4BZ2hQw0UOZVNwGoFoS4ZqaZiv8mm0lX6s9/AdQD6AVrpXWKa7JU2wDiay9sR bYh+5vVWGz9mhncK/Vfwtu5IjVp5v5WMz/WfnUxZMcNlfgTo4i1swww+qRBO2A4Yj8qKKWnT sl7aCX92itTiPgwbt6YgQPwgww72r67jPt5o8VMXDqPMPKzGicw1AyxtMjsoSlnn91FuZctw il3vPpvzGXtBmrzQSbdDmy0KT5p5/W9pD/8UtLLLM6PLs5X0jIhovQHnQKEUO7xV3yNDAW9D PICeh7f/o9W+QJfQAXngNz0brvmgScAUXRaeAFeQbAmtEG92qlSVD7gb7WOemllgfbEn0Nan rv5aEcZCWx4WjybMLHEAEQEAAcLBfAQYAQoAJgIbDBYhBHLPrCF5vLAktbVFkANvbJ7n856/ BQJmJ1DIBQkVt0GQAAoJEANvbJ7n856/SOkP/iocAFde4BUQ8D8WQuG+dXum75rwlV1NutwI dzZyzLDF6l5ItV9t1VtWVOpd7lgWqHtUBGqjm6mw6qR9YoXNMeycnokBq2YSunLuV2K/UEij NES6deNYYu1HIb4GbfeEODiK2xQ40dDPwpucSQmZ0FeHfnkO7hgIRlywbIyG8p4HHuKR01/W 07pOGGRA6F8GRoI+m38ARe+r/2W4HlrJnS/+POKm6lu67wdtcBNqeYF3rcgrvh08bqZtIaEt GoyZ54tRpoWq6aTXvI88T5oABwZKn95m5KAvUlQ15IOGF049uAN4APOExOtqVNcvQPypeRCo OTShW20C1ZM3ZaRc39alDu3bj1S24K/Ldav8Qe+kzWs744Tu+QytbWtpr+gvkrpPVXdFiFiD uCF3WQZrTdTr3Nm5ES2ePV2YW02M837VnmW8hm9id3iiBawyhdUyNtSPXXGTZSMD/TZ8urv2 R3xMkpoh2j5PIJ4cF2ZJEz/VOaWv6LN4/+MgC7icVyUldoOZeWFjLS2YBgy50ICICmCefF4e kMGcbPi9+OAd1lLYwkLd1AAhQu1JPU163KW8/Bkc/FqrzE0iJxX9N3I3Zyt3uswd1+7Lxisw WZdkvBJvTpHtp1CeiA794MDJEVQfI9o5icfRBNOoPJM8c56FTs19JmiH35KSh45LpcSbDr3t In-Reply-To: <35410f21-8e52-a853-ad21-4fd05d0f8b3c@macktronics.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 19/09/2024 18:16, Dan Mack wrote: > On Tue, 2 Jul 2024, sthaug@nethelp.no wrote: > >>>> So we set uid 53 (bind) at 0.083518302, and then try to bind to port >>>> 953 at 0.093282161. >>> >>> Are you going to poe a bug with the bind people? >> >> Already did: https://gitlab.isc.org/isc-projects/bind9/-/issues/4793 >> >> Steinar Haug, AS2116 > > Probably everyone knows but this still happens in the bind920-9.20.1 > package. > > However, BIND 9.20.2 was released yesterday with a change to when bind > drops privilege levels so perhaps we will have a working version when > the port / package is updated. The update was already committed: https://cgit.freebsd.org/ports/commit/?id=06790657ec8a80f894db824e7a9cadd71ec4e292 Cheers, Matthew From nobody Thu Sep 19 18:04:13 2024 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 4X8k1B2ccdz5Wl2q for ; Thu, 19 Sep 2024 18:04:14 +0000 (UTC) (envelope-from mack@macktronics.com) Received: from mail.macktronics.com (coco.macktronics.com [209.181.253.65]) (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 4X8k1B0xBZz49vk; Thu, 19 Sep 2024 18:04:14 +0000 (UTC) (envelope-from mack@macktronics.com) Authentication-Results: mx1.freebsd.org; none Received: from olive.macktronics.com (olive.macktronics.com [209.181.253.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.macktronics.com (Postfix) with ESMTPS id 6A95B1204; Thu, 19 Sep 2024 13:04:13 -0500 (CDT) Date: Thu, 19 Sep 2024 13:04:13 -0500 (CDT) From: Dan Mack To: Matthew Seaman cc: stable@freebsd.org Subject: Re: BIND 9.19.24 not listening to rndc port (953) In-Reply-To: Message-ID: <1c138b97-2cc3-992c-f9ad-a944c0638163@macktronics.com> References: <38321p06-q966-p811-oqpq-q679qpo9pp31@yvfgf.mnoonqbm.arg> <20240702.112250.268297637701792446.sthaug@nethelp.no> <18s0oq25-816s-84ns-41np-47402182ns46@yvfgf.mnoonqbm.arg> <20240702.191333.1782316333681428598.sthaug@nethelp.no> <35410f21-8e52-a853-ad21-4fd05d0f8b3c@macktronics.com> 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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:209, ipnet:209.181.252.0/23, country:US] X-Rspamd-Queue-Id: 4X8k1B0xBZz49vk X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated On Thu, 19 Sep 2024, Matthew Seaman wrote: > On 19/09/2024 18:16, Dan Mack wrote: >> On Tue, 2 Jul 2024, sthaug@nethelp.no wrote: >> >>>>> So we set uid 53 (bind) at 0.083518302, and then try to bind to port >>>>> 953 at 0.093282161. >>>> >>>> Are you going to poe a bug with the bind people? >>> >>> Already did: https://gitlab.isc.org/isc-projects/bind9/-/issues/4793 >>> >>> Steinar Haug, AS2116 >> >> Probably everyone knows but this still happens in the bind920-9.20.1 >> package. >> >> However, BIND 9.20.2 was released yesterday with a change to when bind >> drops privilege levels so perhaps we will have a working version when the >> port / package is updated. > > The update was already committed: > > https://cgit.freebsd.org/ports/commit/?id=06790657ec8a80f894db824e7a9cadd71ec4e292 > > Cheers, > > Matthew Thank you! Was about to try a build myself but now I don't have to :-) From nobody Thu Sep 19 22:32:48 2024 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 4X8qzH09cXz5XdNL for ; Thu, 19 Sep 2024 22:32:59 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (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 4X8qzG4Ykdz4wLK for ; Thu, 19 Sep 2024 22:32:58 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=citron; t=1726785170; x=1727451836; h=date:author:from:to:cc:subject: message-id:in-reply-to:references:openpgp:blahblahblah:author:from: subject:date:to:cc:resent-author:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-reply-to:resent-message-id:in-reply-to: references:mime-version:content-type:content-transfer-encoding: content-disposition:content-id:content-description:message-id: mail-followup-to:openpgp:blahblahblah; bh=VVGQ0XEptLM8uxGgm5HA6Uj/ZfNS96DhJMAqDXMyZJY=; b=Tj/VjabJHqdVhymosunUBdECUyS0X6nejrMGxtiwtG9XrEKQJpuPt+8Aa6fvV8ACDNbZWyx8 PHnpcgTWXRdZ497gC7s4ZVWPi2zXVbhUnu+NM3WOJd0JL9Qw+rOA85o8OiBzrpbc63ONY7xCj6 pX4MYBXvEZ7vHprj7Oss/rDVg0Lnlnx6uzYDHN3/5KPxgevEW8pifVnne4ztejsvuIE3PxN+2l D5ZPF113ZtRbCf3qDPz2JwUGCPx/CKH/7paMHEqwiJyMCuuEoxmQMrTHmSydiK3PHFa3qS2RRL ANUnIurW8XEL2ATHsaPSx3FmlFPXLiHV6oU+R3+eKKZBCAmw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=orange; t=1726785170; x=1727451836; h=date:author:from:to:cc:subject: message-id:in-reply-to:references:openpgp:blahblahblah:author:from: subject:date:to:cc:resent-author:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-reply-to:resent-message-id:in-reply-to: references:mime-version:content-type:content-transfer-encoding: content-disposition:content-id:content-description:message-id: mail-followup-to:openpgp:blahblahblah; bh=VVGQ0XEptLM8uxGgm5HA6Uj/ZfNS96DhJMAqDXMyZJY=; b=g91WWwO/il/fVHr8Q3gY8v+twBMdyrpA31hD9UmSKAx4j6/Sf2GNnmkbLI7Igvw2FFU60Iwo 7vWYSxTJRIJAAg== Date: Fri, 20 Sep 2024 00:32:48 +0200 Author: Steffen Nurpmeso From: Steffen Nurpmeso To: Joachim Durchholz Cc: stable@freebsd.org Subject: Re: issues with syslogd include redirecting wg0 output to custom location Message-ID: <20240919223248.Hr-N0jar@steffen%sdaoden.eu> In-Reply-To: <627f0b4f-6d55-4872-9435-07109a9a6aa0@durchholz.org> References: <4250c967-61c7-419a-b542-455a8f655dd1@osfux.nl> <0019d1f0-0b84-448d-8ecd-5b1619103139@osfux.nl> <20240918225906.Npft_PNY@steffen%sdaoden.eu> <20240918230901.P2V-MyI6@steffen%sdaoden.eu> <627f0b4f-6d55-4872-9435-07109a9a6aa0@durchholz.org> User-Agent: s-nail v14.9.25-608-ge479530e8d OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15987, ipnet:217.144.128.0/20, country:DE] X-Rspamd-Queue-Id: 4X8qzG4Ykdz4wLK X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated 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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org Joachim Durchholz wrote in <627f0b4f-6d55-4872-9435-07109a9a6aa0@durchholz.org>: |On 19.09.24 01:09, Steffen Nurpmeso wrote: |> Ha. |> |> Steffen Nurpmeso wrote in |> <20240918225906.Npft_PNY@steffen%sdaoden.eu>: |> |> I got back |> |> : host vm1982.osfux.nl[79.99.187.212] said: 554 \ |> 5.7.1 Service |> unavailable; Client host [217.144.132.164] blocked using sbl.spamh\ |> aus.org; |> Error: open resolver; https://check.spamhaus.org/returnc/pub/141.1\ |> 01.75.8/ |> (in reply to RCPT TO command) | |Oh, that's a problem on vm1982.osfux.nl, who rely on Spamhaus to |identify IP addresses that have sent spam in the past. |Spamhaus is pretty well-known for being unreliable; the spam filters in Ooh? For my postfix i use smtpd_client_restrictions = # permit_inet_interfaces, OR permit_mynetworks, permit_tls_clientcerts, #[RELAY] permit_sasl_authenticated, check_client_access lmdb:$meta_directory/client_restrict, reject_unknown_client_hostname, # in case you want reject DNS blacklists rather than greylist them, # exchange sleep (maybe) and uncomment the lines below sleep 1, #reject_rbl_client cbl.abuseat.org, #reject_rbl_client sbl.spamhaus.org, reject_rbl_client zen.spamhaus.org, zen. since 2015 and it never caused problems, as far as i know? (It does, however, not find that many positives .. i have none in my logs, which however go back two days only (rotated logs go out via email, and rotate keeps five).) Maybe i should simply stop using that. #reject_rbl_client bl.spamcop.net, #reject_rbl_client list.dsbl.org, reject_unauth_pipelining, #reject permit |your mail client work much better, and if they misclassify a mail you |can easily find it in the spam folder instead of rejecting the mail and |making life difficult for the admin on the sending side. Maybe i really should do this, too. |Regards, |Jo Ciao Jo, --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) From nobody Sat Sep 21 09:28:02 2024 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 4X9kSt13fKz5Xh6f for ; Sat, 21 Sep 2024 09:28:14 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from mx.sdf.org (mx.sdf.org [205.166.94.24]) (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 ECDSA (P-256) client-digest SHA256) (Client CN "mx.sdf.org", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X9kSs1L1Lz4Ty5 for ; Sat, 21 Sep 2024 09:28:13 +0000 (UTC) (envelope-from bennett@sdf.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=sdf.org header.s=sdf.org header.b=qPPZvbs4; dmarc=pass (policy=quarantine) header.from=sdf.org; spf=pass (mx1.freebsd.org: domain of bennett@sdf.org designates 205.166.94.24 as permitted sender) smtp.mailfrom=bennett@sdf.org Received: from sdf.org (IDENT:bennett@rie.sdf.org [205.166.94.4]) by mx.sdf.org (8.18.1/8.14.3) with ESMTPS id 48L9S3l5017252 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Sat, 21 Sep 2024 09:28:04 GMT DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sdf.org; s=sdf.org; t=1726910884; bh=jfDdWCyMg7vbUHaGEuwMa52EJZAn8eOPnAmRB4EU2TQ=; h=From:Date:To:Subject:Cc; b=qPPZvbs4l3/vOWitdcD2Pak/R/03ou+Tmcr5fHBkQUKcbsNMSoKJmCF+Arz+69Twg kIxToWNz6uc+Gd/j2s58iMO1s9q8mCgc+XVLQ/4kNx4t1fE7odKQM3kcxGEGWcWltN OWMD9QSZXq7P03Av/9ugmVIGPIRMmfCNMnKNEtRw= Received: (from bennett@localhost) by sdf.org (8.18.1/8.12.8/Submit) id 48L9S2YO015150; Sat, 21 Sep 2024 04:28:02 -0500 (CDT) From: Scott Bennett Message-Id: <202409210928.48L9S2YO015150@sdf.org> Date: Sat, 21 Sep 2024 04:28:02 -0500 To: pete@twisted.org.uk Subject: Re: 13.3R's installworld killed system--please help! Cc: freebsd-stable@freebsd.org User-Agent: Heirloom mailx 12.5 6/20/10 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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-2.48 / 15.00]; FAKE_REPLY(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.96)[-0.965]; NEURAL_HAM_MEDIUM(-0.51)[-0.515]; DMARC_POLICY_ALLOW(-0.50)[sdf.org,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:205.166.94.0/24]; R_DKIM_ALLOW(-0.20)[sdf.org:s=sdf.org]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; SUBJECT_ENDS_EXCLAIM(0.00)[]; ASN(0.00)[asn:14361, ipnet:205.166.94.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[sdf.org:+] X-Rspamd-Queue-Id: 4X9kSs1L1Lz4Ty5 X-Spamd-Bar: -- On Mon, 16 Sep 2024 23:39:53 +0100 Pete French wrote: >On 15/09/2024 06:23, Scott Bennett wrote: > >> Thank you very much for this suggestion! It hadn't crossed my mind, >> likely because I thought I had thrown all those old CD-Rs and DVD+/-Rs away >> when I moved to a different apartment in February. After seeing your message, >> though, I went looking. In the very first place I checked, lo and behold, I >> found a DVD-R I had labeled "PC-BSD 8.2 (64-bit) Installer, LiveCD, and Repair >> Disk" and "PCBSD8.2-x64-DVD.iso Disk 1 of 1". 8-D So I then did as you >> suggested. Unfortunately, it made no change in the resulting boot behavior. >> :-( At least I now know I have such a disk at hand to try such things. > >Am gald you found the disc - I was also going to say that I am quite >happy to burn one for you and post it, though thats a slow method of >acquiring a CD! I remember posting someone in the US a copy of Minix >on 5.25 floppies back in 1989, and it took a while to get there, but >did indeed boot on arrival. > >Am dissapointed that the updated boot sectors didnt help though. I >would have bet money on that being the issue (and lost the bet!) > > >> Thank you both for that reassuring information. After all this, it is >> now clear that the boot code was not the problem and that I *still* have no >> idea what went wrong. I do not remember ever having an upgrade from source >> actually fail before this experience. Even the trickiest one many years ago-- >> a merged procedure to upgrade from i386 to amd64 in place and from, I *think*, >> 9.x to 10.x, went well. (Trust me, I was as nervous as I would be on a >> non-precision approach in nighttime IMC in a non-radar, mountainous environment >> with flashes of light around me (yes, that happened to me once), but I had >> planned all the steps carefully, and my combined procedure was successful.) > >!!!! umm, yeah, I really would not like to try that! not that I would, >never having got an IMC rating, but the little bits I did with foggles >on convinced me that this was not the kind of flying I wanted to do ;) > I understand. Many creepy tales from issues of _NTSB_Reporter_ loomed in the back seat and outside in the cloud in the dark. 8-| > >i386 -> amd64, however, I did that, and that worked fine, despite also >being very nervous. I;ve only ever done source upgrades, going right >back to FreeBSD 3, and the only times it failed to boot were when I It has been a long time, but I think I upgraded from 5.2.1, which was my starting release of FreeBSD, to 5.3 to 5.4 to 5.5 to 6.1 by binary upgrades with sysinstall(8). I had a dual-boot setup at the time with Win/XP. Then I upgraded from 6.1 to 6.2, also with sysinstall(8) but screwed something up and decided to re-install from scratch for some reason. (My memory of the time is foggy because I had 5 or 6 broken bones and was heavily doped up for several weeks.) In the process I apparently gave an erroneous partition specification to sysinstall and managed to wipe out the WinXP partition, whereupon I decided that I was dangerously fed up with WinXP anyway and would live more happily without it. Since that time I've always done upgrades from source on my main machine. As noted earlier, I did try freebsd-update(8) on the laptop because I run a GENERIC kernel on that machine and that machine is even slower than this tower for running buildworld. As also noted earlier, I learned to ignore that freebsd-update(8) even exists and that it is basically a direct route to way too much repair work and general grief. >forgot to upgrade the boot code for a newer ZFS pool. > >> rolled every file system back to that snapshot. After reinserting the drives >> into the tower, I booted it and ... my 12.4-RELEASE-p2 system was up and >> running again. What a relief! > >Aha! Fantastic! > >OK, so, you rolled back the filesystems .... but left the boot code >intact ? So this is now running your old filesystems but booting Yes. >using the updated 14.2 code that you wrote using PC-BSD, yes ? > Not 14.2, but 13.3. I have yet to do anything with 14.x, except to switch my src tree to the releng/14.1 branch. >> So I'm back to where I was before attempting the upgrade. It's a good >> system, but it is out of support, so thank you very much to everyone who >> responded anyway. I am pondering what my next step should be. > > >OK, I have forgotten the start of this thread, but you went from the >last version of 12 to a build of 13.0 release, which you compiled under 13.3-RELEASE-p1, not 13.0. I don't do .0 releases. I learned at least 35 years ago not to bother with those. >the installed 12? > Yes. >How far did it get in the boot process - did it even find the pool and >try and load the kernel, or not even that far? If it is now booting off It asked for the GELI passphrase, I entered that, it began to "turn" the cursor a couple of moves, then began moving the cursor with long delays between moves to various locations up and down along the lefthand side of the screen. After several moves the cursor stopped, and that was as far as it went. So I *think* it successfully completed the verification of the GELI passprase, but whether it then was able to understand the pool or find a valid kernel in that pool I have no idea. All I know is that somewhere early in the normal train of events it goes off the rails and stops. >the installed latest boot code, then we know it can run code which >should find the pool. Yes. > >Do you have the 'bootfs' property set on the pool ? > AFAIK, yes. I didn't change it while doing any of this, so it *should* be set properly still. Likewise for the GELI setting on the partition that holds the "system" pool, which is why the boot code asked for the passphrase. > >This is a puzzle - I've done this repeatedly, going from 3 all the way >to 14, and its always worked. > Yes. It's the first time I've seen an upgrade from source fail, too. Two different fiascos with 13 are enough to scare me off and send me on to 14, bypassing further contact with 13. My tentative plan is a source upgrade to 14.1-RELEASE or whatever is now the current patch level of 14.1-RELEASE, but I'm waiting a bit longer to see whether anyone on the list has reasons to offer as to why that route would be inadvisable. If nobody does, then I'll try to get to that fairly soon. Scott From nobody Sun Sep 22 15:34:56 2024 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 4XBVYj3Y1Nz5Wgk9 for ; Sun, 22 Sep 2024 15:35:05 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (smtp.digiware.nl [176.74.240.9]) by mx1.freebsd.org (Postfix) with ESMTP id 4XBVYh0nlNz4slV; Sun, 22 Sep 2024 15:35:04 +0000 (UTC) (envelope-from wjw@digiware.nl) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=digiware.nl header.s=medusa-2017 header.b=XsnWJ9yc; dmarc=pass (policy=quarantine) header.from=digiware.nl; spf=pass (mx1.freebsd.org: domain of wjw@digiware.nl designates 176.74.240.9 as permitted sender) smtp.mailfrom=wjw@digiware.nl Received: from [IPV6:2001:4cb8:3:1:a5f4:aedf:5a35:ee5b] (unknown [IPv6:2001:4cb8:3:1:a5f4:aedf:5a35:ee5b]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail.digiware.nl (Postfix) with ESMTPSA id 381859AF1E; Sun, 22 Sep 2024 17:34:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=digiware.nl; s=medusa-2017; t=1727019297; bh=dxpWOxaBTs01a+PJea68wy/IjZVlvkK6qPLg4Fb1IFM=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=XsnWJ9yce/h8ll4nisw5ehiY74Bffo0LpWXXbpZi2HdBsuqzK6fKwUXNr8+L/k6Gu WsgK9IAY7p56nS7t/jkna/b0/3MzIZaa4bkO4EbxawVYlrYGMPHds4pNiFCKT1OBgq vClecgpSp2FW/HFqBpklvVa6wdHTx2rdbUb/ze5kpGXmgsBeu6xKJm92YP6jAf3DnD FP//ri0IirDLckZEpTO3DKDykgpGzwdzdqjCBHAY4s1M7tmxVxT3oJj/BjsbG4QK2w 8fzwjTS67V6rfJmkuXqiQGOlUhqhBojkF39Q3pTDspbDaBey1q0SaYjQdcvPamCECN SUvorR3LyHD5Q== Message-ID: Date: Sun, 22 Sep 2024 17:34:56 +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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: BIND 9.19.24 not listening to rndc port (953) Content-Language: en-US, nl To: Dan Mack , Matthew Seaman Cc: stable@freebsd.org References: <38321p06-q966-p811-oqpq-q679qpo9pp31@yvfgf.mnoonqbm.arg> <20240702.112250.268297637701792446.sthaug@nethelp.no> <18s0oq25-816s-84ns-41np-47402182ns46@yvfgf.mnoonqbm.arg> <20240702.191333.1782316333681428598.sthaug@nethelp.no> <35410f21-8e52-a853-ad21-4fd05d0f8b3c@macktronics.com> <1c138b97-2cc3-992c-f9ad-a944c0638163@macktronics.com> From: Willem Jan Withagen In-Reply-To: <1c138b97-2cc3-992c-f9ad-a944c0638163@macktronics.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Server: router10G.digiware.nl X-Rspamd-Action: no action X-Spamd-Result: default: False [-3.79 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[digiware.nl,quarantine]; R_DKIM_ALLOW(-0.20)[digiware.nl:s=medusa-2017]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; RCVD_NO_TLS_LAST(0.10)[]; ONCE_RECEIVED(0.10)[]; XM_UA_NO_VERSION(0.01)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; TO_DN_SOME(0.00)[]; ASN(0.00)[asn:28878, ipnet:176.74.224.0/19, country:NL]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ARC_NA(0.00)[]; MLMMJ_DEST(0.00)[stable@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[digiware.nl:+] X-Rspamd-Queue-Id: 4XBVYh0nlNz4slV X-Spamd-Bar: --- On 19/09/2024 20:04, Dan Mack wrote: > On Thu, 19 Sep 2024, Matthew Seaman wrote: > >> On 19/09/2024 18:16, Dan Mack wrote: >>>  On Tue, 2 Jul 2024, sthaug@nethelp.no wrote: >>> >>>>>>  So we set uid 53 (bind) at 0.083518302, and then try to bind to >>>>>> port >>>>>>  953 at 0.093282161. >>>>> >>>>>  Are you going to poe a bug with the bind people? >>>> >>>>  Already did: https://gitlab.isc.org/isc-projects/bind9/-/issues/4793 >>>> >>>>  Steinar Haug, AS2116 >>> >>>  Probably everyone knows but this still happens in the bind920-9.20.1 >>>  package. >>> >>>  However, BIND 9.20.2 was released yesterday with a change to when bind >>>  drops privilege levels so perhaps we will have a working version >>> when the >>>  port / package is updated. >> >> The update was already committed: >> >> https://cgit.freebsd.org/ports/commit/?id=06790657ec8a80f894db824e7a9cadd71ec4e292 >> >> >>     Cheers, >> >>     Matthew > > Thank you!   Was about to try a build myself but now I don't have to :-) > Untill that time I choose to set the highest privileged port to 952...     net.inet.ip.portrange.reservedhigh=952 --WjW From nobody Sun Sep 22 22:32:31 2024 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 4XBgqg37Dzz5Xgrb for ; Sun, 22 Sep 2024 22:32:47 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic312-24.consmr.mail.gq1.yahoo.com (sonic312-24.consmr.mail.gq1.yahoo.com [98.137.69.205]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XBgqf1TKqz4bgr for ; Sun, 22 Sep 2024 22:32:46 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=Jd9sZ46l; dmarc=pass (policy=reject) header.from=yahoo.com; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.69.205 as permitted sender) smtp.mailfrom=marklmi@yahoo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1727044364; bh=JuFuVAe+UEYXDKW4+vHUYKn9xM0mHWrvvFl0Xg4KuZc=; h=From:Subject:Date:To:References:From:Subject:Reply-To; b=Jd9sZ46l76vUlkJiLPvlpxJDWIutE31LBh/d3+tzDniLx9DMB3SV0kqu+2sywhJzaV2qyttPwMXROhCNYH5kWeThDZzQln82xWczzG12w0J8Nq6DQ295JlauPRfcuGc73gC7gRLLK2i1Scrf4pFRiC9zFKofZ1OWsmRTV0G7QxHOgZX1T9GoXHgcKKwcNFR62dvgRLT2CIurxSvxZuhey59T5VfDc7XzfJmA5RFKEVpiReITUig20Skn1J3RilXgPNGDxCBGodtRx61z7tRk/rQTnA8K2BtLNfs/beKu2hSU7REhUOs0UR8GUt53EOTL7oBp0rnNx8ccIXvhKb2NiA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1727044364; bh=T30hvnvqfcs9vwAgvRkmJsvYwypTLeucoITh/rmkKb+=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=c9X3sQ2Dnz5nXCBuriwSPOgDYtUYMnSRMgTkkT3CyE43O2d6RJg6/L/mEEEy4O0fE+rKcjg9xRTaJJZqrQPNLwUkF+ZNLgV5zY1cdaMKXYgd8idweEH7xvDNiGXRHWHUk4M4Jq6H2m8bMCROsMgP2rrX3xRt20XkerCKVh9ZG56ScQkN4RBf/7CJJmdm3apRaCz96m0J5vwtr+EoVkPAhI2OpB8Zes+XzI4faEinXKLvFWP3cUeQ5ySf2Iw1ilKHBAtKB5Ip2CevPSNzP2rfxGBJ2/6eaZBeELOO8xJopk0VUu0VLrtrcD7spiKvDdNeoGG+vBbQ1svFht7e8+QZfQ== X-YMail-OSG: oPA7FzgVM1nl5YajvA2PrDn9ZrbcUYN9lLygcvt3IzXWDMSFJR2fqigqf64rxri gfGt.gTP4fZcNbv1dAlBY7ofuOy7A3f9xw.405OBoi.1tKWte0DFpmSVFev6JOuKzm8NyoLwKRfr keGProfsbaB7sHCjjagfWftaGvMBSoO7nak6Nbo_DLbqOEjnkXKDLMHs0eG9i.dMeZ6zElo6rGcp vmugwJ.VVJ5kihJhIoM_omO0nI1hSAG2akkjPM4ctxNVFM7zTGjpbNhO3Ujfn3SQSwSENP9g5zJ9 Mg2BWOajfxy1lPyxf8OWE.f4CblRrkKrrIa3.MP1QkkkF6pfGjEboYVsa7d5F21SXzNlqmzwml16 j33MsewBC0FybdxerBQ41n8NLyyx42C3nz2goxA6epw.SgGdIRK1TKCweP2AscU.Swhn0xMzV.Z_ ZDGAA8JXlPHcQw3h91o2cinAU1YQ42k_.qMgJIjKQoIVFcV76YSJeAQ6THPKWbjCGzkSoca2ry7M iMfRq.SQVNKoyYv66MmQp83_c52_0TSj8AsWLii_T2K5f1iE5sFkhhkXH.RlYi0BJEMkvzozruSp SKrulxFwNHEc0bSeMpac5MgUP0h0aeuoFr3BHDFlXVBXtcOfoUIJEgKkaOXs16LAbiMHywAaQMcg u9vIuyE1SrUUoVt6JfpK4ZfVCgpQhlIPTKNk67LNQgAXjVK.Q6zcf9yFYaDsYpVZIl0qZWy143GH KavYorV5Ljf6MviKVOz6kP2fIeO6KXi7CSS9ba7PgulSPHu70IfPSefRo0EYt56AaDhKkvVwk7iF wzpzFPq2KyNtaAIeqxLNYEPxMd8i3xVAt6b7GluQ7ENRY3k6qQnzEettxHzjzRdBjXscjcvyxX6N Qnrkvdbh37cELLgWPDs8rU6s.gHBYVVw0FNSjl1BE5AQRgN9jI.hoo1e6cUB.wZQ65XC4C6M4W_G UGi65GLpSnNAPmXDFGal.yVde59yv8V_rWycRZeUr0gbAo2GISR05rUPQsLASH7L8mxycRZekmYT 4yPxIgjjwzFvR2fRn2jjGwVQOSFMytj2EguET74eAYexHeDrauLEjBsygJUAEHXTJH6ICxWmuiEZ oJ2hcW8QlLly15R6fIE4H6A5FeiPiF8.VbgcrTBpITNwTr37dGh0.8403O_BotqZhsiSOL90jJlu h0vJwF61qZhX9X4LG8OirXIN4.xRMy14r2YZ4UVJPrQZKR3v2GK2Owx9.ZxPTqCr42aarkgqHaKl KkvWmgTm9jPUYlokB2d4pl7WoX0yuB.09yjSqdNDjLj5jL2YZAlXlipYlwj.3XjUxymyPp9dr_9h 18S0pruo_RCKo4Js20ccJ3z2Hr7yrjWuCf8r58QYAARdHhIiCf07TSuzHNeenwCmqmbCcHwYIHmf Eq42MHChF_TlGmFDrHThRkIU2.DrGSArPkKoN8Q6BKOzrLjueOoVYwxexxraCsDaqpVLaaVAE254 dE1FI97k..5V8KPbWEfYbbMC.RSc5909cQv8.K8OiS7TGa.wwNgU_DuqdrV0SGIwIyGlREr_bHTb KnGAOxPlbSFv59153AZUToBllYq4Uq.KnOkjE06J_zKGxjBKFYZJqZ1SBBOglyDxwQfoJ9S6dLK3 qt2U90s0wXIm78B4dOONbX8GOl2P5N.fDgVDlhlrpONQV3GYMUqbdJzN8EtkLW22qbp7IilUw.Jn 5JVJCHkME1Z2aYPawOnyX3x61wL4JZbwcW9pv9SteINQbL2bMuxGpklh6Z52WAOlRAe5eKGXn9I5 RhT5UinrjhbE52sg.ICbZhMUFcZ68LMVX7ssV4MMqCCJuj2wx9.wEY3um3tDLeh1xHTJXlh93mus K9_5B6sLehwXg9wTlY_HJAUhEOn3i1G1iw7JVrx3RXLbYsvgajAZlJ_r_So1_tsxthA73kkuFshx 9gX2j0J3O6zKpzrlO9_ptTgInu8VMtvVoHJ9AvfZ8pGhIBwebhmamJji.FJmmjzSB2BqO4SFxuX1 JuUxrLk.NBbf.juPeblMmQAiSIZecTxKkCkrdig2Z9bJvgEkUZrMlerFFtCbZPUo19hOC4Iw7mjg 8rWjH4eCdWNcyXSbIiycZnZCqN9YbKSI5uvsvrOrtqjg_qQ9Ixo0Tw1aj75YLEkXKADukt0qnHCx UwYKSYjsTvNV18KDK5Ai3qoJNBjVl7IAgcUSt3zOIaoLkP_AkKDmL1agPpNaZ4mymHwrVSJk39NI sxgVqvR7am1RQciv4PCPPIKfJjc1y.HxlnloUoYGGPo4oc7EniutumFduYjuOLFRuZlFMVVUms0s gXVor.KO94WC_ X-Sonic-MF: X-Sonic-ID: 61f72bbc-b3d0-4a5c-9537-59d21380dd19 Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.gq1.yahoo.com with HTTP; Sun, 22 Sep 2024 22:32:44 +0000 Received: by hermes--production-gq1-5d95dc458-kk28l (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 668dc57a5105633eae4ea354244932e4; Sun, 22 Sep 2024 22:32:42 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable 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: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\)) Subject: RE: Change to FreeBSD release scheduling and support period vs. Message-Id: <2653A8B4-0CE9-4FEE-B816-74C5F34864E5@yahoo.com> Date: Sun, 22 Sep 2024 15:32:31 -0700 To: FreeBSD-STABLE Mailing List , Colin Percival , "gordon@freebsd.org" X-Mailer: Apple Mail (2.3776.700.51) References: <2653A8B4-0CE9-4FEE-B816-74C5F34864E5.ref@yahoo.com> X-Spamd-Result: default: False [-3.20 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.70)[-0.698]; SUBJECT_ENDS_SPACES(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; ARC_NA(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; TO_DN_SOME(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; APPLE_MAILER_COMMON(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.69.205:from]; RCVD_IN_DNSWL_NONE(0.00)[98.137.69.205:from] X-Rspamd-Queue-Id: 4XBgqf1TKqz4bgr X-Spamd-Bar: --- h= ttps://lists.freebsd.org/archives/freebsd-announce/2024-July/000143.html From: Colin Percival Date: Thu, 11 Jul 2024 02:16:14 UTC lists: > Release EoL > 13.3: Mar 2024 Dec 2024 > . . . > 13.4: Sep 2024 Jun 2025 > . . . > 13.5: Mar 2025 Apr 2026* > . . . > * 13.5 and 14.6 are supported until 5 years after 13.0 and 14.0 = respectively. Note the explicit 13.5 release mentions. However, https://www.freebsd.org/security/ makes no mention of 13.5: > Branch Release Release Date Expected EoLstable/14 n/a n/a November 30, = 2028 > . . . > stable/13 n/a n/a April 30, 2026 > releng/13.4 13.4-RELEASE September 17, 2024 June 30, 2025 > releng/13.3 13.3-RELEASE March 5, 2024 December 31, 2024 It reads is as if releng/13.4 was to be the last 13.*-RELEASE . I'll note that: https://www.freebsd.org/security/unsupported/ lists: releng/13.0 13.0-RELEASE n/a April 13, 2021 August 31, 2022 and the announcement's wording with "supported until 5 years after 13.0" is not explicit about the 2021-April-13 vs. 2022-Aug-31 for the start of the 5 years --but the security table suggests the 2021-Apr-13 as the start of the about 5 years. So it looks to me like releng/13.4 possibly should have "Expected EOL" listed as something like "13.5-RELEASE + 3 months", much like releng/14.1 lists "14.2-RELEASE + 3 months". In other words: it probably should mention the next 13.* release number (13.5) in some way. =3D=3D=3D Mark Millard marklmi at yahoo.com