From owner-freebsd-net@FreeBSD.ORG Fri Apr 24 18:04:40 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA195106566B for ; Fri, 24 Apr 2009 18:04:40 +0000 (UTC) (envelope-from m.jakeman@lancaster.ac.uk) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.freebsd.org (Postfix) with ESMTP id 4AC628FC0C for ; Fri, 24 Apr 2009 18:04:40 +0000 (UTC) (envelope-from m.jakeman@lancaster.ac.uk) Received: from [10.0.30.4] (client-86-25-235-212.mcr-bng-011.adsl.virginmedia.net [86.25.235.212]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0MKuxg-1LxPZ02Htj-0000oo; Fri, 24 Apr 2009 19:51:51 +0200 Message-ID: <49F1FCF1.9000903@lancaster.ac.uk> Date: Fri, 24 Apr 2009 18:54:57 +0100 From: Matthew Jakeman User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: Bob Van Zant References: <49F1128A.3080501@comcast.net> <49F1E2E7.5010703@lancaster.ac.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+HEbwUenFyk0XUo4JCNQLWaBtZ2iX4x+HbqVP Etst1bb/XrZ/RdFfDlsblKEPtK1Mr0XCDUeS7z88f7G8tYNF3r oT5Uj04JB4hGTMSVva5BKob+sSCc0XguP6HqYuH9xA= Cc: freebsd-net@freebsd.org, Nathan Lay Subject: Re: IPv6 Ideas X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Apr 2009 18:04:41 -0000 Bob Van Zant wrote: >> What are your problems with using radvd? I have used it quite a bit on >> FreeBSD (6.1) without any hassle. It's even written quite nicely in my >> experience so working on patches for it should be quite do-able if >> there are features missing. > > He's saying that the router announcements don't contain any DNS server > information. There's an extension/option that can be enabled with router > advertisements to make it send this information, similar in function to > how DHCP sends out extra info like the default gateway, DNS server, NTP > server, WINS servers, etc. Yes but he was also saying that support for the existing RFC to provide the RA option does not seem to be present in any of the tools (from what I gathered). If the RFC is there then surely this functionality could be added. From the original message I thought he was having problems getting radvd to work at all. This could just be me misunderstanding the mail however. From my perspective this is one thing that needs significant improvement for v6. There are many RFC's/ietf drafts out there that add some nifty functionality but support for them in the real world applications seems to be lacking somewhat. > > To my knowledge this wasn't around when the Kame guys were working on > this stuff. I don't think a lot of time has been spent updating the v6 > support applications since then and that's why we don't have this feature. > > This isn't a big deal in dual-stack networks because the clients just do > DNS over v4 with whatever the DHCP server gave. In a pure-v6 world... In > hindsight it's an obvious oversight that it wasn't included in the first > place. > > -Bob > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"