Date: Wed, 16 Jan 2019 14:59:49 +0000 From: Pete French <petefrench@ingresso.co.uk> To: freebsd-stable@freebsd.org, petefrench@ingresso.co.uk, thomas@gibfest.dk Subject: Re: CARP stopped working after upgrade from 11 to 12 Message-ID: <E1gjmfV-000DjX-4E@dilbert.ingresso.co.uk> In-Reply-To: <a7b651e4-68a9-e52c-0033-e8d46508590e@gibfest.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
> Indeed. I am seeing the same thing. Which revision of 12 are you running? Ah, now that is very interesting - I wasnt expecting a reply so fast! I am running r342847 - not though, that this is also the version I am running on the two test systems which do work. > I am currently (yesterday and today) bisecting revisions to find the > commit which broke this, because it worked in 12-BETA2 but doesn't work > on latest 12-STABLE. Well done, thats takes a lot of effort to do. Thankyou for doing this. > MFC r340394: ipfw.8: Fix part of the SYNOPSIS documenting > LIST OF RULES AND PREPROCESSING that is still referred > as last section of the SYNOPSIS later but was erroneously situated > in the section IN-KERNEL NAT. Docs only, so cant be this one I think. > MFC r341638: > Let kern.trap_enotcap be set as a tunable. Also cant be this one from eyeballing the code. It simply makes it writeable. > MFC r340405: > Add accounting to per-domain UMA full bucket caches. This is not touching networking, so seems unlikely, though it is an actaul significant code chnage. > r342051 | kp | 2018-12-13 20:00:11 +0000 (Thu, 13 Dec 2018) | 20 lines > > pfsync: Performance improvement ahh..... now, this is where things like likely, as the difference between my test amchines and my live machines is that the live machines are using pf with pfsync enabled. > Of these I thought r342051 sounded most likely, so I am currently > building r342050. Thats my feeling too going through the above. Have you also tried simply disabling pfsync to see if CARP returns to normal ? I could live without pfsync to be honest, if thats what it takes to make this work. > I will write again in a few hours when I have isolated the commit. Thankyou again for outting in the effort to bisect this - if you can isolate it then we can back the change out and try it again and see if that helps. -pete.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1gjmfV-000DjX-4E>