From owner-freebsd-stable@freebsd.org Wed Jan 16 17:33:32 2019 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8989148F494 for ; Wed, 16 Jan 2019 17:33:32 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (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 91BEB77021 for ; Wed, 16 Jan 2019 17:33:31 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [2a02:b90:3002:411::6] (helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1gjp4C-000Ac9-41; Wed, 16 Jan 2019 17:33:28 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1gjp4C-000ErD-1K; Wed, 16 Jan 2019 17:33:28 +0000 To: freebsd-stable@freebsd.org, killing@multiplay.co.uk, petefrench@ingresso.co.uk, thomas@gibfest.dk Subject: Re: CARP stopped working after upgrade from 11 to 12 In-Reply-To: Message-Id: From: Pete French Date: Wed, 16 Jan 2019 17:33:28 +0000 X-Rspamd-Queue-Id: 91BEB77021 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dmarc=pass (policy=none) header.from=ingresso.co.uk; spf=pass (mx1.freebsd.org: domain of petefrench@ingresso.co.uk designates 2a02:b90:3002:411::3 as permitted sender) smtp.mailfrom=petefrench@ingresso.co.uk X-Spamd-Result: default: False [1.02 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RDNS_NONE(1.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip6:2a02:b90:3002:411::3]; NEURAL_HAM_LONG(-0.75)[-0.751,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_MEDIUM(-0.35)[-0.350,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: ingresso-co-uk.mail.protection.outlook.com]; DMARC_POLICY_ALLOW(-0.50)[ingresso.co.uk,none]; NEURAL_HAM_SHORT(-0.55)[-0.549,0]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16082, ipnet:2a02:b90::/32, country:GB]; HFILTER_HOSTNAME_UNKNOWN(2.50)[]; IP_SCORE(-0.02)[country: GB(-0.09)] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2019 17:33:32 -0000 > I have confirmed that pfsync is the culprit. Read on for details. Excellent work. I;m home now, so won't get a chnace to out this into practice until tomorrow unfortunately, but it's brilliant that you have confirmed it. > I tried disabling pfsync and rebooting both nodes, they came up as > MASTER/SLAVE then. This is very useful to know - I willprobably try tomorrow running my firewalls back up with pfsync disabled to see if it works for me too. > Then I tried enabling pfsync and starting it, and on the SLAVE node I > immediately got: That kind of confirms it really doesnt it ? So, is it possible to get r342051 backend out of STABLE for now ? This is a bit 'gotcha' for anyone running a firewall pair with CARp after all. -pete. PS: are you going to file a PR ?