*** From dhcp-server -- To unsubscribe, see the end of this message. ***
[EMAIL PROTECTED] wrote:
> *** From dhcp-server -- To unsubscribe, see the end of this message. ***
>
> Greetings, all! I have been having a lot of difficulty setting up my DHCP server,
>and I'm hoping someone can help.
>
> Let me give you some information about my system setup. First off, I own a Dell XPS
>400. It contains a Pentium2 processor with 128 MB RAM. I installed the workstation
>version of Red Hat 6.0 last June.
The first question would be what version of the dhcp server are you running. RH
distributed an outdated version (2.0b1pl6) for a while. The current 2.0 version is 2.0
final (which is newer than anything with a "b1pl"); Personally on a test network I
would use the 3.0 betas since they have MUCH more interesting features (pools)....
RH6.0 stock kernel DOES have all the required kernel options.
> Recently, I have embarked upon the creation of an Ethernet LAN in my home. To
>accomplish this, I purchased a CNET Ethernet card, and installed in my Dell. The
>card uses the tulip driver supplied on CNET's web site.
> The card had the default IP of 169.254.63.76. Using this default, I decided to make
>my network address 169.254.63.0. I named my Dell MUFan, and my domain name is
>Houston. I added MUFan.Houston at 169.254.63.76 into the Hosts list.
Where did you get this "default IP"?
169.254.0.0 is used for the Autonegotiation by win9x and other oses when there is no
dhcp server availible and the machine was configured to use DHCP. [Note that this
could also be caused by a misconfigured network card/driver, wrong speed on network
card, bad cabling, cable/dsl not allowing more than a certain number of IPs per cable
modem/adsl user]
The address ranges that you "should" be using for your internal network are the ones
from RFC1918.
Some "broken" stacks had 169.254.x.y as reserved, thus not "possible/blocked"...
Also, some stacks would not handle subnetting correctly.. [169.254.0.0 would be the
network address, 169.254.255.255 would be the broadcast address]
On a class C that has not been further subneted that is within the RFC1918 ranges are:
192.168.x.y where x=0-255, y=1-254...
The network address should be 192.168.x.0
the broadcast address should be 192.168.x.255
the netmask should be 255.255.255.0
> I set about creating a DHCP server to handle the testing of a new SNMP device. The
>SNMP device will issue a request every 20 seconds for the first minute after
>power-up. Then, the device will issue the request every minute.
>
> In order to use dhcpd, installed the package from the source disk. Then, I made the
>simple configuration files.
>
> Through reading the on-line documentation about DHCP server setup, it appeared to be
>a simple process. Merely create a dhcpd.conf file with valid lease addresses, and
>then create an empty dhcpd.leases file.
>
> So I did just that. I set up a /etc/dhcpd.conf of:
>
> subnet 163.254.69.0 netmask 255.255.255.0 {
> range 169.254.69.78 169.254.69.80;
> }
Since you are not using the default network configurations for that class (169.254.
was a class B in the OLD way of doing things) you need to also send a netmask option
and a broadcast option to the client. The device may also be asking for other options
that it needs..... Does the manufacturer have a list of the required/minimum options
for the device?
option netmask-address 255.255.255.0
option broadcast-address 169.254.69.255
[note, as mentioned above, using RFC 1918 addresses would be MUCH better]
>
> Then, I did a touch /etc/dhcpd.leases.
>
> Next, I started the daemon. I decided to run it in debug mode: # dhcpd -d -f
>
> Here are the messages I received:
>
> Nov 22 20:34:05 MUfan dhcpd: DHCPDISCOVER from 00:e0:d8:0c:10:cd via eth0
> Nov 22 20:34:06 MUfan dhcpd: DHCPOFFER on 169.254.63.78 to 00:e0:d8:0c:10:cd via eth0
> Nov 22 20:34:25 MUfan dhcpd: DHCPREQUEST for 169.254.63.78 from 00:e0:d8:0c:10:cd
>via eth0
> Nov 22 20:34:25 MUfan dhcpd: DHCPACK on 169.254.63.78 to 00:e0:d8:0c:10:cd via eth0
> Nov 22 20:34:35 MUfan dhcpd: DHCPDISCOVER from 00:e0:d8:0c:10:cd via eth0
> Nov 22 20:34:36 MUfan dhcpd: DHCPOFFER on 169.254.63.78 to 00:e0:d8:0c:10:cd via eth0
> Nov 22 20:34:55 MUfan dhcpd: DHCPREQUEST for 169.254.63.78 from 00:e0:d8:0c:10:cd
>via eth0
> Nov 22 20:34:55 MUfan dhcpd: DHCPACK on 169.254.63.78 to 00:e0:d8:0c:10:cd via eth0
> Nov 22 20:35:05 MUfan dhcpd: DHCPDISCOVER from 00:e0:d8:0c:10:cd via eth0
> Nov 22 20:35:06 MUfan dhcpd: DHCPOFFER on 169.254.63.78 to 00:e0:d8:0c:10:cd via eth0
> Nov 22 20:35:25 MUfan dhcpd: DHCPREQUEST for 169.254.63.78 from 00:e0:d8:0c:10:cd
>via eth0
> Nov 22 20:35:25 MUfan dhcpd: DHCPACK on 169.254.63.78 to 00:e0:d8:0c:10:cd via eth0
>
> The MAC address of the tested device is 00:e0:d8:0c:10:cd. My MUFan Ethernet card
>is at the eth0 interface.
>
Is your network card connected to the same hub as your xDSL/cable modem/apartment
network? If so, you may be conflicting with the DHCP server run by your ISP/apartment
complex {and possibly making a system admin somewhere very unhappy with you}. In such
a test network situation like yours I would say to have two network cards, one
connecting to the "external"
network, and the other connecting to the internal network [with all the wierd test
devices]..
Your cablemodem/ADSL/etc provider may only allow a limited number of ips via dhcp; and
declining the machine an address, which means that it uses a 169.254. address...
> I went to examine the dhcpd.leases file. Sure enough, there was an entry for the
>device listed.
>
> Here is where I get confused. All the messages on my screen appear to indicate that
>the request was acknowledged. To me, this means that the device should now contain
>the IP information that I have assigned it. However, when I hook a laptop up to the
>device to check its configuration info, I find that the device has not actually
>assumed the new IP information.
>
> To make sure that the DHCP of the device was working properly, I took it to work.
>At work, we have a DHCP server. Sure enough, within a few seconds of connecting to
>my work's network, the device had new IP information.
>
> I don't understand, and I have not been able to find any worthwhile help on-line.
>Please, ANY help would be greatly appreciated. I am out of ideas.
>
> Thank you very much! Have a good day.
>
> -Dennis K.
--
-
Sami Yousif
mailto:[EMAIL PROTECTED]
http://www.mav.net/teddyr/syousif/ Personal Page
http://www.alug.org/ Amarillo Linux Users Group
No Spam Please.
-----------------------------------------------------------------------
List Archives : http://www.isc.org/ml-archives/dhcp-server/
Unsubscribe : http://www.isc.org/dhcp-lists.html
-or- : mailto:[EMAIL PROTECTED]?Subject=unsubscribe
-----------------------------------------------------------------------
