From owner-freebsd-stable@freebsd.org Mon Mar 19 10:27:49 2018 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 3F585F63397 for ; Mon, 19 Mar 2018 10:27:49 +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 D1276681ED for ; Mon, 19 Mar 2018 10:27:48 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from cpc73666-dals20-2-0-cust303.20-2.cable.virginm.net ([82.47.237.48] helo=foula.drayhouse.twisted.org.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1exs14-0001Mj-Md for freebsd-stable@freebsd.org; Mon, 19 Mar 2018 10:27:46 +0000 Subject: Re: HAST, configuration, this actually looks insane To: freebsd-stable@freebsd.org References: From: Pete French Message-ID: <2383bbc2-0efe-288a-99b6-cc35c23bcd16@ingresso.co.uk> Date: Mon, 19 Mar 2018 10:27:46 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 10:27:49 -0000 I aalways found hast very easy to configure - I stopped using it a couple of weeks ago, but up until then we had used it heavily in production. Have found some old config files, which do work, as examples: two machines - catbert-active, catbert-passive. catbert-active is 192.168.10.3, passive is 192.168.10.4. on catbert-active: resource cbert0 { replication memsync local /dev/gpt/catbert-active-hast-a on catbert-active { remote tcp4://192.168.10.4 source tcp4://192.168.10.3 } on catbert-passive { remote tcp4://192.168.10.3 source tcp4://192.168.10.4 } } on catbert-passive: resource cbert0 { replication memsync local /dev/gpt/catbert-passive-hast-a on catbert-active { remote tcp4://192.168.10.4 source tcp4://192.168.10.3 } on catbert-passive { remote tcp4://192.168.10.3 source tcp4://192.168.10.4 } } As you can see, its the same config file on both machines, just my gpt name is different. If I were using device names then it would be identical. I always fix both source and remote addresses as I was using a pair of dedicted cards to connect themmachines - they had other Ip addresse and could see each eother over a different LAN too. I always put by 'local' outsid the 'on' definitionse, and had different config files on each machine. I havent tried it with 'local' inside, but your config does look OK to me, assumng that works. try adjusting it to have the soucre addess and local outside of th definition like I do though, as I do know that works. -pete.