From owner-freebsd-questions@FreeBSD.ORG Tue Aug 6 16:48:51 2013 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 395F9F59; Tue, 6 Aug 2013 16:48:51 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0332B28B7; Tue, 6 Aug 2013 16:48:50 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id r76GmiLW011385 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 6 Aug 2013 11:48:44 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.135]) by LTCFISWMSGHT04.FNFIS.com ([10.132.206.15]) with mapi id 14.02.0309.002; Tue, 6 Aug 2013 11:48:43 -0500 From: "Teske, Devin" To: markham breitbach Subject: Re: .sh script code to determine IPv4 or IPv6 Thread-Topic: .sh script code to determine IPv4 or IPv6 Thread-Index: AQHOkDzj3H/8RokAXEKdt073gODRzpmDtomAgAAhnICABNzRgIAAB/8A Date: Tue, 6 Aug 2013 16:48:42 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D7202006F16@ltcfiswmsgmb21> References: <51FCE9C7.7020407@a1poweruser.com> <20988.61897.78070.312049@jerusalem.litteratus.org> <13CA24D6AB415D428143D44749F57D720200229A@ltcfiswmsgmb21> <52012235.3050006@ssimicro.com> In-Reply-To: <52012235.3050006@ssimicro.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.126] Content-Type: text/plain; charset="us-ascii" Content-ID: <25DDB5A166CEAA4B91D59A6F358C185A@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-08-05_07:2013-08-05,2013-08-05,1970-01-01 signatures=0 Cc: Devin Teske , questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 16:48:51 -0000 On Aug 6, 2013, at 9:20 AM, markham breitbach wrote: > On 13-08-03 8:04 AM, Teske, Devin wrote: >> Actually, there's /usr/share/bsdconfig/media/tcpip.subr >>=20 >>=20 > I don't seem to have that (FreeBSD 8.3-RELEASE). Where would I get that = from?=20 >=20 >=20 It's in up-coming 9.2-R (and present 9.2-* snapshots leading up to 9.2-R). You can snatch a copy of the code by installing sysutils/bsdconfig from the= ports tree. However, the port is marked (correctly-so) as requiring FreeBSD 9.0 or high= er. But don't let that stop you... the only reason it's marked as requiring 9.0= is because 9.0 brings in a new dialog(1) implementation. However, if you're interested in the TCP validation code... that will work = on any release. It's only the dialog(1) stuff that won't work on 8.x or old= er. Luckily, it'll be pretty easy to avoid the land-mines. All functions starti= ng with f_dialog_* should be avoided on 8.x or older. So here's the latest package to download (in case you're unsuccessful in ge= tting the port to behave -- afterall, it may just balk at you for not runni= ng 9.x): fetch http://druidbsd.sourceforge.net/download/bsdconfig/bsdconfig-0.9.0.t= bz That's a FreeBSD package. You can download it and say (as root): pkg_add bsdconfig-0.9.0.tbz Just be forewarned (again), on 8.x or older, executing "bsdconfig" will hav= e widely unexpected results (it won't eat your homework, but it may or may = not actually *run*). However, doing the above 2-step (fetch & pkg_add) will bring in the files y= ou're looking for and give you the functionality you're wanting on 8.x. --=20 Devin P.S. I really *can't* make the dialog(1) stuff backward compatible with 8.x= 's (or any older's) version of dialog(1). The new `cdialog' variant that wa= s brought into 9.x to replace the aging dialog(1)/libdialog pair is has a *= lot* of functionality that I depend on. It could potentially take months to= make bsdconfig *fully* backward compatible with 8.x. For now, it's safe if= you just use the libraries and avoid any/all functions beginning with "f_d= ialog_". _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.