Expiring leases

[Stulic,Damjan]

Simon, David, 
This statement is in use.
server-identifier 172.17.163.80;
Hosts are mostly xp workstations and 3com switches. I will take a closer
look at what is going on.
Thank you for pointing this out for me!

Thanks,
Damjan Stulic
IS Security Identity Management
515-3429


 
 If you are not the intended recipient of this message (including attachments), or if you have received this message in error, immediately notify us and delete it and any attachments.  If you no longer wish to receive e-mail from Edward Jones, please send this request to messages at edwardjones.com.  You must include the e-mail address that you wish not to receive e-mail communications.  For important additional information related to this e-mail, visit www.edwardjones.com/US_email_disclosure
 
-----Original Message-----
 

From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On
Behalf Of Simon Hobson
Sent: Tuesday, April 01, 2008 2:38 PM
To: dhcp-users at isc.org
Subject: RE: Expiring leases

Stulic,Damjan wrote:
>My problem stems from the use of virtual ip.
>While dhcpd listens on that ip, it sends out packets from physical ip.
>Clients use that ip as their dhcp server. Then we swap servers, virtual
>ip moves, but clients still use the old ip to communicate on t1 and t2.
>so on lease expire they broadcast hit a new server and get a new lease.
>
>As far as I know there is no know solution for "multiple ips per
>interface" problem. Right?

I believe "server-identifier" should do what you want, specify the 
virtual IP to be used in outgoing packets.