svn commit: r239356 - head/sbin/dhclient

[Andrey Chernov]

On Mon, Aug 20, 2012 at 02:09:55PM -0400, John Baldwin wrote:
> > RFC 2131 (if you mean it) describes DHCP process itself, it does not 
> > define contents of 'supersede' or other override options for dhclient.
> 
> The supersede handling bits are all based on what the protocol can actually
> send, which the RFC defines as IPv4.

'supercede' itself not based on DHCPv4, it simple override anything 
protocol can actually send and in general case overriding contents can be 
any IP. 

But... I agree with you that it looks like quick hack.

Having dual-stack machine it seems proper way for me to run both DHCP and 
DHCPv6 clients (net-mgmt/wide-dhcp? net/dhcp6?). But I fear they both will 
interact with single /etc/resolv.conf overriding each other there.

> > 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.
> 
> Eh?  DHCP can't return an IPv6 address in the protocol.

As I already mention, perhaps it is router bug combined with the lack of 
validity checking in dhclient itself. As result I currently have
/etc/resolv.conf:
nameserver 192.168.1.1
nameserver <ipv6 address of the tunnel NS>

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