From owner-freebsd-questions@freebsd.org Sat Jun 11 20:04:47 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 549DDAF010C for ; Sat, 11 Jun 2016 20:04:47 +0000 (UTC) (envelope-from stdin@niklaas.eu) Received: from box-hlm-03.niklaas.eu (box-hlm-03.niklaas.eu [84.22.110.84]) by mx1.freebsd.org (Postfix) with ESMTP id 2306C2C0A for ; Sat, 11 Jun 2016 20:04:46 +0000 (UTC) (envelope-from stdin@niklaas.eu) Received: by box-hlm-03.niklaas.eu (Postfix, from userid 1001) id 9674A385519; Sat, 11 Jun 2016 22:04:48 +0200 (CEST) Date: Sat, 11 Jun 2016 22:04:48 +0200 From: Niklaas Baudet von Gersdorff To: freebsd-questions@freebsd.org Subject: Re: When your server boots too fast: How to slow it down? Message-ID: <20160611200448.GC2453@box-hlm-03.niklaas.eu> Mail-Followup-To: freebsd-questions@freebsd.org References: <20160611174849.GA2453@box-hlm-03.niklaas.eu> <20160611193225.GB2453@box-hlm-03.niklaas.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="/e2eDi0V/xtL+Mc8" Content-Disposition: inline In-Reply-To: <20160611193225.GB2453@box-hlm-03.niklaas.eu> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2016 20:04:47 -0000 --/e2eDi0V/xtL+Mc8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Niklaas Baudet von Gersdorff [2016-06-11 21:32 +0200] : > in rc.conf because the public IPv4 is assigned by the router. > However, changing it to SYNCDHCP helped only partly. Now, > tincd starts but both postfix and sshd still fail. Additionally to SYNCDHCP, I added the following three lines: netwait_enable="YES" netwait_if="" netwait_ip="" This solves the problem. But this also requires me to predict the IPv6 that the server gets from the router. In this special case I know it because my provider will only assign me one in particular. But maybe there's something like SYNCDHCP for IPv6 too? Niklaas --/e2eDi0V/xtL+Mc8 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXXG7ZAAoJEG2fODeJrIU/uZwQAJ8zAYbbx1B8ZU0eSWpDf7Nu TurBnLx2qL7WmDceYgsqUOs0Ggu1hIM/gyFxy6peL6QWnzr/d4X0wq2B+3tdGIor R7HYCy/hMUUO76d6SVtQgns6TbgGy1eG+CpjlvXYn3Ja8Tf1rzaKBTMMQFWULN+Y 9o8s7UFNmc5V4fxvbNaDOu/XAXW2P5FYO/a4v6FUJ//47bX//Rmby3RBhFb7jnaT 9S2fIRlwCKbdljFk0LOUBkoMdpkyQhZl6SkoWCJbrfOIOYSHtHxu/sViaP/TBXE7 ElqfgxArkMoSUJn3Lhe3BMe2Vi107o6SJT9V8snS8SeSokw2CPtlXLj8vsslhlKJ /GJLktTC6a1P+AD1XTpXL2uE89gBTFS5Zk1wcUC8aGvLqGVNJ4iCHWm2/eXVp+iU 0I302MPfnYVxZqgjgWb0ySs1p71NWAfjVwikMOpM6E4ClFQxBIf7SG7eSBP8jcEd Vkn2GDELoi5s6Zhrzt0O+hylQs04K9DhTT8L3tIo+LCfiYAvAN16s1UUKk/NNBRn EHVc9trLG/5vlY5/4nZ1jkxP8+3K++m9Wn7sA6a7+SzAYOv6x+/S64Pd0Gqc1vXw Gx1bX61DHrqFBt72Li8n3+qfOwxBy9j7zh3YV1htBqBwGgNYxKYULPXU2jgn87te XoQYNcCcDNPkj8S3IG8X =3vVy -----END PGP SIGNATURE----- --/e2eDi0V/xtL+Mc8--