Alias IP

Randy Grimshaw rgrimsha at syr.edu
Tue Nov 21 14:10:50 UTC 2006


re-reading this I should have used a different term than default. It is a static route that overrides the primary (since two paths exist) the 'default route' may be an entirely different path.
<><Randy


<><Randall Grimshaw
Room 203 Machinery Hall
Syracuse University
Syracuse, NY   13244
315-443-5779
rgrimsha at syr.edu

>>> rgrimsha at syr.edu 11/21/2006 8:54:38 AM >>>

We do what you are attempting. The trick is that you must specify the device in your route command so that the Alias IP is the default route and not the primary. You must construct your heartbeat scripts so that this route is established each time the baton is passed between the nodes.

<><Randy

-----Original Message-----
From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On Behalf
Of Zachár Balázs
Sent: Monday, November 20, 2006 8:12 AM
To: dhcp-users at isc.org 
Subject: Alias IP

Hello @list!

I have the following problem:

active/passive cluster with one virtual IP address...

A node real IP: 192.168.1.2
B node real IP: 192.168.1.3
virtual common IP: 192.168.1.5

So I have an alias IP address in my interface. The dhcp requests come to
the alias IP (192.168.1.5) but the offers going out on the real
interface IP (e.g. 192.168.1.2).
Maybe the problem:
If I give an IP with my real interface, and before the client would like
to renew his IP address the cluster is failover, the dhcpd's IP address
will change... But if I send the offers trough the alias interface, If
the cluster fail over the IP address is still the same (the virtual IP)...

Can I send the offers with my alias interface?





More information about the dhcp-users mailing list