From owner-freebsd-net Sun Mar 25 22:23:15 2001 Delivered-To: freebsd-net@freebsd.org Received: from starfruit.itojun.org (p84.usslc11.stsn.com [63.161.206.84]) by hub.freebsd.org (Postfix) with ESMTP id EE5D237B718 for ; Sun, 25 Mar 2001 22:23:09 -0800 (PST) (envelope-from itojun@itojun.org) Received: from itojun.org (localhost [127.0.0.1]) by starfruit.itojun.org (Postfix) with ESMTP id 481FA7E73; Mon, 26 Mar 2001 13:59:02 +0900 (JST) To: Alfred Perlstein Cc: net@freebsd.org In-reply-to: bright's message of Sun, 25 Mar 2001 12:57:10 PST. <20010325125710.S9431@fw.wintelcom.net> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: proper way to test for INET/INET6? From: Jun-ichiro itojun Hagino Date: Mon, 26 Mar 2001 13:59:02 +0900 Message-Id: <20010326045902.481FA7E73@starfruit.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I'm wondering how one is supposed to test for INET6 support in the >kernel. Currently a few places do it in a somewhat bogus fashion >like this: what are you planning to do after checking IPv6 support in the kernel? applications should be written so that it would work on both IPv4-only, IPv6-only and IPv4/v6 dual stack kernels, by using getaddrinfo(3) and getnameinfo(3). you do not need to check if you write applications properly. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message