ISC dhcpd serve configuration question

2004-01-01 Thread stan
I'm still trying to get ISC dhcp to work in a redundnat fashion where I
have 2 machines, and they share an address pool. 

Here's where I am on this.

Well I thoguht I had it working for a minute. 

The executbale is _really_ picky about the syntax od the config file, and I
found some help at:

http://www.lithodyne.net/docs/dhcp/dhcp-4.html#ss4.3

So, I wound up with this on the master machine:


# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#

# option definitions common to all supported networks...
option domain-name fas.com;
option domain-name-servers 205.159.77.224, 205.159.77.225;

default-lease-time 600;
max-lease-time 7200;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;

# ad-hoc DNS update scheme - set to none to disable dynamic DNS updates.
ddns-update-style interim;
ignore client-updates;
option domain-name fas.com;
ddns-domainname fas.com;

zone fas.com. {
primary 127.0.0.1;
}

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
# log-facility local7;

# No service will be given on this subnet, but declaring it helps the 
# DHCP server to understand the network topology.

subnet 10.152.187.0 netmask 255.255.255.0 {
}


failover peer pool {
 primary;
 address black.fas.com;
 port 519;
 peer address cindy.fas.com;
 peer port 520;
 split 128;
 max-response-delay 60;
 max-unacked-updates 10;
 mclt 3600;
 load balance max seconds 3;
   }

subnet 205.159.77.0 netmask 255.255.255.0 {
pool {
failover peer pool;
range 205.159.77.50 205.159.77.75;
deny dynamic bootp clients;
}
option routers 205.159.77.234;
}

And this on the slave:


# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#

# option definitions common to all supported networks...
option domain-name fas.com;
option domain-name-servers 205.159.77.224, 205.159.77.225;

default-lease-time 600;
max-lease-time 7200;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;

# ad-hoc DNS update scheme - set to none to disable dynamic DNS updates.
ddns-update-style interim;
ignore client-updates;
option domain-name fas.com;
ddns-domainname fas.com;

zone fas.com. {
primary 127.0.0.1;
}

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
# log-facility local7;

# No service will be given on this subnet, but declaring it helps the 
# DHCP server to understand the network topology.

subnet 10.152.187.0 netmask 255.255.255.0 {
}


failover peer pool {
 secondary;
 address cindy.fas.com;
 port 519;
 peer address black.fas.com;
 peer port 520;
 max-response-delay 60;
 max-unacked-updates 10;
 mclt 3600;
 load balance max seconds 3;
   }

subnet 205.159.77.0 netmask 255.255.255.0 {
pool {
failover peer pool;
range 205.159.77.50 205.159.77.75;
deny dynamic bootp clients;
}
option routers 205.159.77.234;
}

And both sides started up OK. But when I booted one of the OpenBSD machines
as a client it failed to get an address.

Looking at tcpdump it _si_ a bootp packet that it sends, so I'm wondering
if this line is the problem?


deny dynamic bootp clients;

Any ideas?

-- 
They that would give up essential liberty for temporary safety deserve
neither liberty nor safety.
-- Benjamin Franklin
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ISC dhcpd serve configuration question

2004-01-01 Thread Lowell Gilbert
stan [EMAIL PROTECTED] writes:

 Looking at tcpdump it _si_ a bootp packet that it sends, so I'm wondering
 if this line is the problem?
 
 
   deny dynamic bootp clients;
 
 Any ideas?

How do you know that the packet is BOOTP?  BOOTP and DHCP use the same
protocol type, so tcpdump(1) (for example) won't be able to
distinguish between them.

Did the server respond at all?

-- 
Lowell Gilbert, embedded/networking software engineer, Boston area: 
resume/CV at http://be-well.ilk.org:8088/~lowell/resume/
username/password public
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ISC dhcpd serve configuration question

2004-01-01 Thread stan
On Thu, Jan 01, 2004 at 08:26:00PM -0500, Lowell Gilbert wrote:
 stan [EMAIL PROTECTED] writes:
 
  Looking at tcpdump it _si_ a bootp packet that it sends, so I'm wondering
  if this line is the problem?
  
  
  deny dynamic bootp clients;
  
  Any ideas?
 
 How do you know that the packet is BOOTP?  BOOTP and DHCP use the same
 protocol type, so tcpdump(1) (for example) won't be able to
 distinguish between them.

OK, I just was going by what the tcpdump said.

So, the line should just prevent bootp clients from getting a lease, right?
 
 Did the server respond at all?

The client nver got a lease, at all. I don't believe I saw a reply in the
tcpdump.

Can I bump up the debuging level on the server?

-- 
They that would give up essential liberty for temporary safety deserve
neither liberty nor safety.
-- Benjamin Franklin
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]