moving from 3.1.1 to 4.1.0
Ray Phillips
r.phillips at jkmrc.com
Sun Nov 30 23:53:36 UTC 2008
I'm currently running a pair of version 3.1.1 ISC dhcp servers in
failover mode. I've no complaints, but am thinking of upgrading to
version 4.1.0 when it comes out of release candidate status. I have
no use for IPv6 as yet but the regex capability in 4.1.0 could be
handy.
The dhcpd man page for 4.1.0rc1 says dhcpd must be executed with the
-4 switch to get it to run in IPv4 mode. That will be a nuisance for
me--a bit of extra typing each time the server is killed and
restarted to make it recognise config file changes. (What would the
result be if I forget to type -4 and the server started in IPv6
mode?) If ./configure is run with the --disable-dhcpv6 option
would the dhcp server then default to IPv4 mode if no switches were
supplied? Would it be possible to use a setting in dhcpd.conf to
tell the server which mode to run in?
By the way, running 4.1.0rc1's ./configure on a NetBSD/i386 4.0.1
machine produces the warnings appended to this message at the end of
its output. Can they just be ignored? make seems to run without any
problems but I haven't actually run the server yet.
Ray
checking for sys/socket.h... yes
checking net/if_dl.h usability... yes
checking net/if_dl.h presence... yes
checking for net/if_dl.h... yes
checking net/if6.h usability... no
checking net/if6.h presence... no
checking for net/if6.h... no
checking regex.h usability... yes
checking regex.h presence... yes
checking for regex.h... yes
checking for library containing MD5_Init... -lcrypto
checking for library containing MD5Init... none required
checking for library containing socket... none required
checking for library containing inet_ntoa... none required
checking for library containing inet_aton... none required
checking for library containing regcomp... none required
checking for library containing if_nametoindex... none required
checking for /dev/random... yes
checking for struct sockaddr.sa_len... yes
checking for struct iaddr *... yes
checking size of struct iaddr *... 4
checking for struct msghdr.msg_control... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: WARNING: Makefile.in seems to ignore the --datarootdir setting
config.status: creating client/Makefile
config.status: WARNING: client/Makefile.in seems to ignore the
--datarootdir setting
config.status: creating common/Makefile
config.status: WARNING: common/Makefile.in seems to ignore the
--datarootdir setting
config.status: creating common/tests/Makefile
config.status: WARNING: common/tests/Makefile.in seems to ignore the
--datarootdir setting
config.status: creating dhcpctl/Makefile
config.status: WARNING: dhcpctl/Makefile.in seems to ignore the
--datarootdir setting
config.status: creating dst/Makefile
config.status: WARNING: dst/Makefile.in seems to ignore the
--datarootdir setting
config.status: creating includes/Makefile
config.status: WARNING: includes/Makefile.in seems to ignore the
--datarootdir setting
config.status: creating minires/Makefile
config.status: WARNING: minires/Makefile.in seems to ignore the
--datarootdir setting
config.status: creating omapip/Makefile
config.status: WARNING: omapip/Makefile.in seems to ignore the
--datarootdir setting
config.status: creating relay/Makefile
config.status: WARNING: relay/Makefile.in seems to ignore the
--datarootdir setting
config.status: creating server/Makefile
config.status: WARNING: server/Makefile.in seems to ignore the
--datarootdir setting
config.status: creating tests/Makefile
config.status: WARNING: tests/Makefile.in seems to ignore the
--datarootdir setting
config.status: creating includes/config.h
More information about the dhcp-users
mailing list