Date: Thu, 16 Jun 2011 23:36:30 +0900 From: Hajimu UMEMOTO <ume@mahoroba.org> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: Hiroki Sato <hrs@FreeBSD.org>, net@FreeBSD.org Subject: Re: [RFC] resolvconf(8) interface id Message-ID: <ygeaadh6dxt.wl%ume@mahoroba.org> In-Reply-To: <F36DB85C-BA31-49D2-A5E0-FA001E7D6774@lists.zabbadoz.net> References: <20110616.015317.781291617533474654.hrs@allbsd.org> <6FE95AC6-CCB2-45B0-8347-AB31283EE144@lists.zabbadoz.net> <20110616.142834.63956571381923731.hrs@allbsd.org> <F36DB85C-BA31-49D2-A5E0-FA001E7D6774@lists.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
>>>>> On Thu, 16 Jun 2011 13:00:32 +0000
>>>>> "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> said:
bzeeb> I can imaging ports like mpd, ... to join this scheme and by then
bzeeb> there might be different "ppp" or "dhcpv4", "dhcpv6" or even different
bzeeb> "slaac". The advantage of this one is that if I prefer dhcpv6 on one
bzeeb> interface it doesn't make a difference if I am going to use dippler,
bzeeb> isc or wide.
The IPv6CP doesn't treat DNS things, and it is DHCPv6 thing. So,
about IPv6 over IPv6, dhcpv6 is enough.
Further, the mpd uses ngN which is a dynamic interface. The
resolvconf has a feature to treat a dynamic interface as special. So,
it is treated as special by resolvconf.
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ygeaadh6dxt.wl%ume>