From owner-freebsd-net@freebsd.org Wed Jul 1 04:40:47 2015 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 909D59918E0 for ; Wed, 1 Jul 2015 04:40:47 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 57B481CA3 for ; Wed, 1 Jul 2015 04:40:47 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by oift81 with SMTP id t81so23628215oif.3 for ; Tue, 30 Jun 2015 21:40:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=TF3OPQAQqmBD2BgnrwrloLThVhiaSwP5o7vrBH5c3Xc=; b=SgQosHvqa6wVZxnD0vBPFJTDta6ffk4iKtfPXUN21nMKN6HjKPVDCPN0pxyymV6CAk QBGqTcNwuG+jfW0vRjxdxGjSNXhPNp6xo3VNsDwOH+4Jy1PLoKCeCW63d8mvP93E4iyi kFtfbHXcIcJixM6yKbwqBKvZhhfO2CUdPUU2BTQgFWZTB2QCQBAuOeSKVHbo8zZfKOp+ wrmV73o9B71fRDLx8I2ZWHxLXYmHEj0b9+yF6O33L2xwNFGC38ZhQnwiAo3l/00ZntfW 8AtUpjpmXzn0HNk5RqpcSrBTCJ8zlT9yRzD48XFcpuxFh/RW1UlMdv6tsiyk8tRFbghU YemA== MIME-Version: 1.0 X-Received: by 10.202.214.20 with SMTP id n20mr14930569oig.91.1435725647032; Tue, 30 Jun 2015 21:40:47 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.202.221.69 with HTTP; Tue, 30 Jun 2015 21:40:46 -0700 (PDT) In-Reply-To: <20150701002949.GA79350@neutralgood.org> References: <20150701002949.GA79350@neutralgood.org> Date: Tue, 30 Jun 2015 21:40:46 -0700 X-Google-Sender-Auth: 7fQ-o3XzbmqRAZXOVWJY8jKru48 Message-ID: Subject: Re: rc settings for ipv6 in 9.3? From: Kevin Oberman To: kpneal@pobox.com Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2015 04:40:47 -0000 On Tue, Jun 30, 2015 at 5:29 PM, wrote: > I just got a /56 block of ipv6 addresses today and I'm trying to figure > out how to use it. > > Before I go rebooting my server I wanted to ask if the information in the > handbook "https://www.freebsd.org/doc/handbook/network-ipv6.html" is > correct > for 9.3-p14. > > I have a static address for my server and I've been given the static > address of the router. So I should just be able to set (in my rc.conf) > ifconfig_bce0_ipv6 and ipv6_defaultrouter, correct? > > Or do I really need these two lines from the handbook?: > ifconfig_bce0_ipv6="inet6 accept_rtadv" > rtsold_enable="YES" > > Also, can someone translate this statement from my provider for me: > "Note: [provider] is routing 2607:f758:2280::/56 to 2607:f758:2280::4/64" > > BTW, is the term "netmask" ever used in IPv6? I thought "prefixlen" was > the term and "netmask" was for v4 only? > > Thanks for any help! > -- > Kevin P. Neal http://www.pobox.com/~kpn/ > No, If your system has a static address (and a server should have one), you don't need SLAAC or Router Solicitation. You just need to set the address: ifconfig_bce0_ipv6="inet6 2607:f758:2280::n/64" and ipv6_defaultrouter="Router address". Netmasks are obsolete everywhere and really should not be used. CIDR addressing has been the standard for a quarter century. Netmasks really should not be used for either IPv4 or IPv6. I am unable to translate the statement from the provider with certainty. I am guessing that the /64 2607:f758:2280::/64 is used by their router with 2607:f758:2280::4 as the address on their router(s). The remainder of the /56 is yours but I could not swear to that. You will probably want more than one /64 for different purposes. Other than externally accessible servers, you should put systems in a different /64 and spread them at random around that space if they are statically addressed. (I don't recommend for or against statically addressing, though.) -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683