From owner-freebsd-net@freebsd.org Thu Oct 12 22:16:33 2017 Return-Path: Delivered-To: freebsd-net@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 A6FE4E367DA for ; Thu, 12 Oct 2017 22:16:33 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [IPv6:2607:f740:c::4ae]) (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 948CA6A3C8; Thu, 12 Oct 2017 22:16:33 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (c-73-240-250-185.hsd1.or.comcast.net [73.240.250.185]) by echo.brtsvcs.net (Postfix) with ESMTPS id 3781538F48; Thu, 12 Oct 2017 15:16:33 -0700 (PDT) Received: from [IPv6:fe80::7102:4df8:1f13:5c55] (unknown [IPv6:fe80::7102:4df8:1f13:5c55]) by chombo.houseloki.net (Postfix) with ESMTPSA id 2A8AD1771; Thu, 12 Oct 2017 15:16:32 -0700 (PDT) Subject: Re: 6rd: when in Base FreeBSD? To: Don Lewis , ler@lerctr.org Cc: freebsd-net@FreeBSD.org, hrs@FreeBSD.org References: <201710120211.v9C2Ba0Y084870@gw.catspoiler.org> From: Mel Pilgrim Message-ID: <8eb440fa-389a-038b-1b71-c80345ceb94f@bluerosetech.com> Date: Thu, 12 Oct 2017 15:16:32 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <201710120211.v9C2Ba0Y084870@gw.catspoiler.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2017 22:16:33 -0000 On 10/11/2017 19:11, Don Lewis wrote: > On 11 Oct, Larry Rosenman wrote: >> The WAN address is DHCP. > > The DHCP WAN address could be problematic. To do this with a DHCP WAN address, create a dhclient hook script that destroys and recreates the gif tunnel if the WAN address changes. I used to have to do something similar with my previous provider (they also used 6rd).