On 02/15/2010 11:56 PM, Benjamin Scott wrote:
My guess is your /etc/hosts file is
misconfigured.
And plenty of distros will cheerfully misconfigure /etc/hosts for you.
For machines with static IP's, I've found the most reliable setup is like:
127.0.0.1 localhost localhost.localdomain
On Sun, Feb 14, 2010 at 12:26 PM, Todd Littlefield
t.littlefi...@comcast.net wrote:
The server-identifier statement
...
So, it needs to be set to the --hostname-- but they really mean --IP--
They really mean your hostname. Your hostname should resolve to an
IP address unique to your host.
I finally got some time to sit down with Wireshark and compare the bootp
packets between the D-Link
and the Linux box... The first thing that jumped out as different was
the source address on the DHCP Offer
packets.
D-Link: 192.168.1.1
Linux: 127.0.0.1
So, something wasn't right. I
On 2/14/2010 12:26 PM, Todd Littlefield wrote:
I finally got some time to sit down with Wireshark and compare the
bootp packets between the D-Link and the Linux box... The first
thing that jumped out as different was the source address on the DHCP
Offer packets.
D-Link: 192.168.1.1
On 01/29/2010 07:10 PM, Todd Littlefield wrote:
The server in question is running CentOS 5.4 with dhcp-3.0.5-21 running.
I have a similar server running fine for those kinds of clients. The
config looks like:
ddns-update-style interim;
ignore client-updates;
allow booting;
allow bootp;
On Fri, January 29, 2010 7:10 pm, Todd Littlefield wrote:
If I disable the daemon on the server and use the one on the router,
the Windows boxes are happy... But that makes me unhappy. I'm at my wits
end trying to get it figured out.
Can you get a wireshark capture of (a) the broken request
Hello,
I have a stupid question about how to configure the ISC DHCPD to
work with
Vista/Win7. At home I have XP and Linux systems running. They all will
broadcast
out to the network to find the server and request and address/lease.
The DHCPD server is configured to hand out the same
Hi! After perusing your e-mail, I have a few things to say, and one idea:
First, to the best of my knowledge, *no* major OS requires a broadcast
response from a DHCP server in response to a request, as per RFC 2131.
(It does leave some wiggle room, but this is almost certainly for clients
that
