Roy Marples <r...@marples.name> wrote:
> On Tue, 2011-07-26 at 00:12 -0700, Geoffrey Sisson wrote:
> > This patch adds basic DHCPv6 support for openresolv. It's unlikely
> > that this is a comlete patch. For example, some applications might
> > resonably expect "resolvconf -d eth0" to remove both the IPv4 and
> > IPv6 interface information. However, it does provide basic DHCPv6
> > functionality.
>
> The patch looks good, but my understanding is that ISC dhclient can only
> operate for IPv4 OR IPv6 and not both at the same time.
Hi Roy,
That's correct.
> As such, why
> make a distinction in protocol when dealing with resolvconf?
DHCPv4 can't be used to transport IPv6 config info, and DHCPv6 can't be
used to transport IPv4 config info, so for a dual-stack DHCP client you
have to run two instances of ISC dhclient -- one DHCPv4 session and
one DHCPv6 session. (More of course if you have more than one interface
under DHCP control.) If you want both IPv4 and IPv6 addresses for
resolvers in resolv.conf at the same time, openresolv has to distinguish
between by protocol as well as by interface; otherwise you end up with
the same race between protocols that you had among interfaces.
I'm not sure whether appending "_ipv6" to interface names is the most
elegant fix, but I wanted to provide a simple proof-of-concept. It may
be cleaner to make the interfaces into directories, e.g.:
/var/run/resolvconf/interface/eth0/ipv4
/var/run/resolvconf/interface/eth0/ipv6
/var/run/resolvconf/interface/eth1/ipv4
/var/run/resolvconf/interface/eth1/ipv6
. . .
Geoff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
