DHCPv6 and MAC Address inclusion

[scott_stone at trendmicro.com]

fortunately for us, we only have a small number of hosts that need IPv6 addresses at this point so it's not a huge issue *yet*.. hopefully by the time it is, this will be addressed, or if not, I will have to rewrite the DHCP client package myself and push it to our custom yum repo for our clients, which I've been considering doing anyway.. ;)

 

====================

Scott Stone <scott_stone at trendmicro.com>

Manager, DCS-RD

Trend Micro, Inc. http://www.trendmicro.com

 

From: dhcp-users-bounces+scott_stone=trendmicro.com at lists.isc.org [mailto:dhcp-users-bounces+scott_stone=trendmicro.com at lists.isc.org] On Behalf Of Ted Lemon
Sent: Wednesday, January 25, 2012 8:39 AM
To: Users of ISC DHCP
Subject: Re: DHCPv6 and MAC Address inclusion

 

On Jan 24, 2012, at 6:25 PM, <scott_stone at trendmicro.com> wrote:

	am I missing something here in terms of how this client and this server are implemented...?
	
	

 

It sounds like a real problem, although part of it is that the DHCP client sounds like it's broken.   You might want to make sure it's up to date.   As far as I know, the state of the art in DHCPv6 support is a fast-moving target, so the fact that it doesn't work for you in CentOS doesn't mean that the problem you are having hasn't been solved.   Windows would be a huge problem at this point, though if you can't make what's there work.   I suppose there's a window of opportunity (yuk yuk) for getting a fix into Windows 8 if the current version isn't doing the right thing.   You might also want to look at ways of solving this in the relay agent.

 

However, I would like to reiterate that while there is interest in sending the MAC address in an option in the IETF, there's no active push going on in the working group; if you want this, you should consider doing some pushing.

 


TREND MICRO EMAIL NOTICE
The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20120125/c951fc83/attachment.html>