Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Aug 2012 23:57:24 +0400
From:      Andrey Chernov <ache@FreeBSD.ORG>
To:        John Baldwin <jhb@FreeBSD.ORG>
Cc:        svn-src-head@FreeBSD.ORG, svn-src-all@FreeBSD.ORG, src-committers@FreeBSD.ORG
Subject:   Re: svn commit: r239356 - head/sbin/dhclient
Message-ID:  <20120818195724.GA74684@vniz.net>
In-Reply-To: <201208171507.07699.jhb@freebsd.org>
References:  <201208171553.q7HFrhuf090457@svn.freebsd.org> <20120817182512.GA58051@vniz.net> <201208171507.07699.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 17, 2012 at 03:07:07PM -0400, John Baldwin wrote:
> On Friday, August 17, 2012 2:25:12 pm Andrey Chernov wrote:
> > On Fri, Aug 17, 2012 at 03:53:43PM +0000, John Baldwin wrote:
> > > Author: jhb
> > > Date: Fri Aug 17 15:53:43 2012
> > > New Revision: 239356
> > > URL: http://svn.freebsd.org/changeset/base/239356
> > > 
> > > Log:
> > >   Fix dhclient to properly exit and teardown the configured lease when
> > >   link is lost.  devd will start a new dhclient instance when link is
> > >   restored.
> > 
> > Is it any chance to teach dhclient IPv6 addresses in very basic parser 
> > level, f.e. to replace nameserver it sniffs from router? Currently 
> > dhcp-options(5) understands IPv4 addresses only and produce error on 
> > 'supersede' IPv6 address.
> 
> I think the RFC defines those to be IPv4, yes?  Presumably DHCPv6 adds
> new option types that support IPv6 addresses?

RFC 2131 (if you mean it) describes DHCP process itself, it does not 
define contents of 'supersede' or other override options for dhclient.

Moreover, current dhclient somewhow able to fetch my IPv6 tunnel DNS 
address from the roiter (I don't look deeper, maybe it is router bug), but 
I don't want IPv6 tunnel DNS, I want router fe80:... DNS instead.

-- 
http://ache.vniz.net/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120818195724.GA74684>