Re: dhclient.conf or DHCP

K Anderson Sat, 29 Nov 2003 21:59:25 -0800

Mike Maltese wrote:

I have my freebsd DHCP server set up and working great. Well great for
Windows clients, but not much so for BSD clients.

Under the Windows clients I just set the host name and when the DHCP
gets a request it dutifully does the job of assigning an IP address as
well as putting in the proper DNS entries. I have tried the same for
another BSD computer and it gets the IP address just fine but the
request doesn't get passed on to DNS for updating.

I tried the dhclient.conf being blank and then also tried putting in
entries as suggested by man 5 dhclient.

Any ideas on getting BSD to have the same behavior as Windows?

This is what I have for dhcpd.conf

option domain-name "squeaks.net";
option domain-name-servers msmouse.squeaks.net,204.127.198.4;
server-name "msmouse";
server-identifier 192.168.100.250;
key rndc-key {
 algorithm hmac-md5;
 secret "wouldn't you like to know";
};

zone squeaks.net. {
 primary 192.168.100.250;
 key rndc-key;
}

zone 100.168.192.in-addr.arpa. {
 primary 192.168.100.250;
 key rndc-key;
}

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;

# 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.

# This is a very basic subnet declaration.

subnet 192.168.100.0 netmask 255.255.255.0 {
  range 192.168.100.1 192.168.100.99;
  next-server 192.168.100.250;
  option routers 192.168.100.105;
  use-host-decl-names on;
}

dhclient.conf is...
interface "ed0" {
           send host-name "pixie.squeaks.net";
           request subnet-mask, broadcast-address, time-offset, routers,
                domain-name, domain-name-servers, host-name;
           script "/sbin/dhclient-script";
           require subnet-mask, domain-name-servers;
}

Try ommiting the domain name. All you should really need in dhclient.conf is

send host-name "pixie";

You the man! Thanks.

Probably never would have figured that one out. I was assuming that when the DHCP request was made that something would have picked up the hostname from someplace else like, ooooh, hostname. I happen to do a tcpdump and could have sworn I saw the hostname or something looking like it in the dump during the request phase.

_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: dhclient.conf or DHCP

Reply via email to