RE: OS/2 DHCP client ID

Glenn Stump <stump@raleigh.ibm.com> Mon, 18 November 1996 22:35 UTC

Received: from cnri by ietf.org id aa17779; 18 Nov 96 17:35 EST
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa23402; 18 Nov 96 17:35 EST
Received: from reef.bucknell.edu by mail.bucknell.edu; (5.65v3.2/1.1.8.2/17Jul96-0109PM) id AA01163; Mon, 18 Nov 1996 17:25:41 -0500
Date: Mon, 18 Nov 1996 17:25:41 -0500
Message-Id: <01BBD56D.CA38EB20@glennlaptop.raleigh.ibm.com>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Glenn Stump <stump@raleigh.ibm.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: OS/2 DHCP client ID
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Mime-Version: 1.0

Hi Hank,

The OS/2 DHCP client does not allow a user to change the client-id and
currently only uses the adapter's MAC address.   I can't explain the 
problems you are having (second-hand).  I can tell you that, to date, we/IBM 
have not had a report on this behavior, so if this is a bug it's clearly in our
best interest to get it identified and fixed, and we'd very much appreciate
your help.

Unfortunately, I don't find the information in your note to be very helpful
in diagnosing a problem.  Even worse, I think the way you represent the 
problem unfairly puts into question OS/2's correctness of function 
(i.e., what you effectively accomplished in your note was to make a
baseless claim that OS/2 DHCP(?) client hosts have "strange 
problems").  

Since much of second-hand information is confused and often erroneous, 
I respectfully request that you please get a better handle on the problem 
data (first-hand) before reporting it, and then to please work through
the IBM product support  channel to resolve the problem.  I'll be glad to 
work with you directly if you'd prefer.

Thanks and regards, 
 Glenn Stump
 IBM Internetworking Solutions
 919-254-5616

----------
From: 	Henry Yung[SMTP:hyung@join.com]
Sent: 	Monday, November 18, 1996 2:12 PM
To: 	Multiple recipients of list
Subject: 	OS/2 DHCP client ID


I am having some strange "problems" with the OS/2 DHCP client.  I should
first say that I haven't seen them with my own eyes,  I am getting this
information second-handed but I am wondering if someone could explain to
me how OS/2 creates its client ID.

I have a customers who CLAIMS that the client sent two requests to the
server, both times with the same MAC address but once with a hardware
type of 1 (Ethernet) and once with a hardware type of 6 (Token Ring).
The machine suposedly has only one Token Ring card.  Exact same MAC
address but different hardware types!?  He also claims that the client
is using BOOTP and not DHCP so it might not have anything to do with client
ID at all.  It might very well be a BOOTP client that is changing the MAC
address fields in the BOOTP header.  However, I find that hard to believe.

I have also heard "rumors" that on OS/2, it is possible for the user
to change the client ID to anything he/she wants at any time.  Is that
true?  In general, what does the OS/2 DHCP client use as its client ID?

Any information will be greatly appreciated.

Thanks in advance.

Hank

Email: hyung@join.com