AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070823155227.4201bb8a@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<jonathan.goldick@onstor.com>,<maxim.kozlovsky@onstor.com>,<tim.gardner@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E051AF1C6@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 23 Aug 2007 15:52:34 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Jonathan Goldick" <jonathan.goldick@onstor.com>
Cc: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>, "Tim Gardner"
 <tim.gardner@onstor.com>
Subject: Re: Linux networking question
Message-ID: <20070823155234.608437c4@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E051AF1C6@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E051AF1C6@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I don't see why not, although I'm not reading the source code right
now.  But the client can create a dhclient.conf file and use it to send
out a host identifier.  That identifier can be unique per IP address,
but I don't believe it has to be unique per originating MAC address.
So you could create the client config file on the fly, run dhclient
specifying that config file, and you should get the IP address that you
want.  Also, different VLANs or LANs for that matter may have different
DHCP servers.  You could also just keep all the information in one
dhclient.conf file and specify the info per interface name.  man
dhclient.conf is your friend.

On Thu, 23 Aug
2007 15:42:58 -0700 "Jonathan Goldick" <jonathan.goldick@onstor.com>
wrote:

> 
>  <<Microsoft PowerPoint Slide>> 
> Do you know of any way in Linux to use DHCP to generate multiple IP
> addresses for the same interface?  
> In the above picture, the use case of 10.2.2.1 and 10.3.3.1 for DATA0
> can be thought of as either two different virtual servers, or one
> virtual server that has multiple IP addresses because of server
> consolidation from two original servers.  The use case of 10.1.1.3 for
> MGMT1 and 10.2.2.2 for DATA1 is having a different management IP
> address from the nfs/cifs traffic on DATA1...but in reality these
> interfaces are built from the same real interface FAIL1.
> 
> Making the above configuration with static IP addresses is simple,
> but I am less clear on how it could be done with DHCP.  I've done a
> fair amount of reading already, but nothing has leapt out.
> 
