| Subject: | Re: DHCP: multiple hardware address? |
|---|---|
| From: | gartmann@xxxxxxxxxxxxxxxxxxxxxxxx (Christoph Gartmann) |
| Date: | Tue, 15 Jul 2008 13:47:34 +0000 (UTC) |
| Newsgroups: | vmsnet.networks.tcp-ip.multinet |
In article <01MX547U58SG8Y55J4@xxxxxxxxxxxxxxxxxxxxx>, Selden E Ball Jr
<seb@xxxxxxxxxxxxxxxx> writes:
>Ken wrote
>> I have toyed with the idea of assigning the same IP to wired and
>> wireless nics of a single laptop, but haven't put that into production yet.
>
>We've done that for years.
The question is how to do it properly. If we do it like in my example it is
somehow working but takes a long time (around 80 seconds) for the client to
get its address.
So we do it differently and make a separate entry for each address, e.g.
host Mac485_E1 {
hardware ethernet 00:1f:5b:35:77:2c;
fixed-address 10.1.4.31;
option host-name "Mac485";
}
host Mac485_E2 {
hardware ethernet 00:1f:5b:35:77:2d;
fixed-address 10.1.4.31;
option host-name "Mac485";
}
But I would prefer to have it all in a single statement, e.g.
host Mac485_E1 {
hardware ethernet 00:1f:5b:35:77:2c;
hardware ethernet 00:1f:5b:35:77:2d;
fixed-address 10.1.4.31;
option host-name "Mac485";
}
It shouldn't be a big deal for Process to make the above thing work a bit
faster.
Regards,
Christoph Gartmann
--
Max-Planck-Institut fuer Phone : +49-761-5108-464 Fax: -452
Immunbiologie
Postfach 1169 Internet: gartmann@immunbio dot mpg dot de
D-79011 Freiburg, Germany
http://www.immunbio.mpg.de/home/menue.html
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Problem with Multinet cluster service names., Malcolm Dunnett |
|---|---|
| Next by Date: | Re: Problem with Multinet cluster service names., Jim |
| Previous by Thread: | Re: DHCP: multiple hardware address?, Selden E Ball Jr |
| Next by Thread: | MultiNet ECO kit available: NAMED-050_A052, bryant |
| Indexes: | [Date] [Thread] [Top] [All Lists] |