Failover without shared-network?

Ken Roberts ken at hoverclub.net
Tue Jul 18 17:30:39 UTC 2006


Content-Type: text/plain
Content-Transfer-Encoding: 7bit
On Tue, 2006-07-18 at 12:03, David W. Hankins wrote:

> On Tue, Jul 18, 2006 at 11:57:09AM -0500, Ken Roberts wrote:
> > The first problem started with me trying to configure it, and the server
> > refused to start because the stuff wasn't inside a shared-network.  At
> > that point I discovered the documentation on that requirement, I thought
> > in the man page for dhcpd.conf(5) but it doesn't seem to be there now.
> 
> Can you provide a config snippet of what didn't work?
> 
> That might make the problem obvious to us.


OK, I have a dhcpd.conf and a dhcpd.master here.  Hopefully I didn't
chop out too much.

Note that DDNS does not work, so some of the declarations won't make
sense.  That's a much smaller issue to me, so I'll work on that later.




-- Attached file included as plaintext by Ecartis --
-- File: dhcpd.conf

failover peer "dhcp" {
  primary;
  address dhcp1.my.net;  # Address THIS server listens on for failover traffic.
  port 12345;                # port is not yet defined in standards, so we need this.
  peer address dhcp2.my.net; # Address of failover peer.
  peer port 12359;
  max-response-delay 60;
  max-unacked-updates 10;
  mclt 3600;  # max client lead time, defined on primary only.
  split 128;  # must be 128, defined on primary only.
  load balance max seconds 3;
}

include "/etc/dhcp/dhcpd.master";


-- Attached file included as plaintext by Ecartis --
-- File: dhcpd.master

ddns-update-style interim;

default-lease-time 2400;
max-lease-time 2400;
dynamic-bootp-lease-length 2400;

ddns-domainname "MY.DOMAIN";
do-forward-updates true;


option netbios-name-servers 192.168.2.21,172.19.200.105;          # wins server
option domain-name "my.net.";
option domain-name-servers 192.168.3.12,192.168.2.11;

update-static-leases true;
always-reply-rfc1048 true;


option fqdn.no-client-update false;                   # clients should not update dns dynamically.
option ntp-servers tick.my.net, tock.my.net; # time servers
option nntp-server nntp.xo.com;
option www-server w3.my.net;
deny unknown-clients;

subnet 192.168.2.0 netmask 255.255.255.0 {
  # NO DHCP!
  authoritative;
  deny unknown-clients;
  option routers 192.168.2.1;
  host mercury       { fixed-address 192.168.2.11; hardware ethernet 00:01:03:25:80:89; }
  host mars          { fixed-address 192.168.2.14; hardware ethernet 00:01:03:25:6F:93; }
  # more host declarations...
}

subnet 192.168.6.0 netmask 255.255.255.0 {
  # VLAN 6
  authoritative;
  ddns-updates on;
  allow unknown-clients;
  option routers 192.168.6.1;
  pool {
    deny dynamic bootp clients;
    failover peer "dhcp";
    range 192.168.6.100 192.168.6.254;
  }
}

subnet 192.168.8.0 netmask 255.255.255.0 {
  # VLAN 8
  allow unknown-clients;
  allow client-updates;
  authoritative;
  ddns-updates on;
  option routers 192.168.8.1;
  pool {
    deny dynamic bootp clients;
    failover peer "dhcp";
    range 192.168.8.100 192.168.8.254;
  }
}





More information about the dhcp-users mailing list