help: booting a computer with bootp/dhcpd

help: booting a computer with bootp/dhcpd

Post by tilmanglotz.. » Sun, 08 Aug 1999 04:00:00



Hello,

I set up two computers, one as as bootp/dhcpd server:

EtherNetAdr Server: 00:00:F4:5C:70:9E
Card: PCMCIA Corega Ether PCC-T
The card is assigned to an IP addess and running in promisc mode
(for tcpdump to scan for any activity on the line)
BootpServer: I tried both, dhcpd, and bootp.

and the other one as client:

EtherNetAdr Client: 00:40:26:3F:DA:0D
ne2k-pci.c* PCI NE2000 clone 'Via 82C926' at I/O 0xd400, IRQ 10
eth0: PCI NE2000 found at 0xd400, IRQ 10, 00:40:26:3F:DA:0D
.

A)Experiment 1:
===============
The client machine is booted from floppy disk, and uses a kernel
with the bootp option compiled in. After uncompressing the kernel,
the client is sending bootp request on the ethernet. At least this
what it tells it does.

Client Side:
------------
EtherNetAdr Client: 00:40:26:3F:DA:0D
ne2k-pci.c* PCI NE2000 clone 'Via 82C926' at I/O 0xd400, IRQ 10
eth0: PCI NE2000 found at 0xd400, IRQ 10, 00:40:26:3F:DA:0D
Sending BOOTP requests...eth0: timeout waiting for Tz RDC
.eth0: timeout waiting for Tx RDC.

Server Side:
------------
tcpdump -evvn -i eth0  on the server gives me this for each bootp
request that is sent from the client:

8:8:1:1:40:40 ff:ff:ff:ff:26:26 3939 406:
                         0000 ffff 0000 0000 0606 eaea 0000 0000
                         0000 0000 0000 2626 0000 0000 0000 0000
                         0000 0000 0000 0000 0000 0000 0000 0000
                         0000 0000 0000

Questions:
----------

Question 1: What kind of package is this ? Bootp ? Why do I not
find the client's ethernet address in this packet ?

Question 2: I ran both, dhcpd and bootpd in debug mode. Why do the
bootp request not get to the  bootpd/dhcpd server which would surely
show up in a debug message ?

Question 3: How does bootpd know the interface to listen at ? It is
not given on the comand line nor in the configuration file
(/etc/bootdtab). I did not find any remark on that in the how-to's or
in the man page.

B) Experiment 2 (Pinging):
==========================

1)I booted the client with a boot/root disk system.
2) The client is assigned IpAdr 130.149.5.2, the server gets 130.149.5.1
3) The route tables are set on both machines.

Pining from the server to the client does nothing (expect producing a
lot of arp-tell me requests), because there is no Inetd setup on the
client's
side

Pinging from the client to the server gives this:

Client side:
------------

PING 130.149.5.1 (139.149.5.1): 56 data bytes
eth0: timeout waiting for TxRDC
eth0: timeout waiting for TxRDC
eth0: timeout waiting for TxRDC
neighbor table overflow
neighbor table overflow
neighbor table overflow

Server Side (tcpdump -evvn -i eth0)
-----------------------------------

14:44:05.973908 8:8:8:8:0:0 ff:ff:ff:ff:26:26 2626 60:
                         8282 0000 0000 0501 0606 eaea 0000 0000
                         0000 0000 0000 2626 0000 0000 0000 0000
                         0000 0000 0000 0000 0000 0000 000

Questions:
----------

Question 1: Why did ping not work ?
Question 2: Why is the client's Ethernet Address not in the package ?

Help is appreciated, as I am struggeling with this for a month by now.
The first hurdle was the PCMCIA network card not working. It got
detected
by cardmgr, and looked well in the system logs - Nevertheless, it
wasn't working at all. This I could fix. Bootp seems to be the next
quest.

Thanks,

Tilman

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

 
 
 

1. Help needed: DHCPD does not answer BOOTP requests

Hi there,

I'm trying to configure a simple DHCP setup (1 PC running the demon,
another one as embedded client).
The DHCPD shall answer to BOOTP requests of a client.
Unfortunately it does not work. I see the clients boot requests (using
ethereal) but I
do not see any answer of the DHCP demon.

The DHCPD config file is this:
------------------------------------------------------------------
#option broadcast-address 192.168.100.255;
#option subnet-mask 255.255.255.0;

#ddns-update-style ad-hoc;
allow bootp;

subnet 192.168.100.0 netmask 255.255.255.0 {
#    range 192.168.100.10 192.168.100.250;
#    option routers 192.168.100.1;

host emb0 {
    hardware ethernet 00:80:29:e5:b7:1f;
    fixed-address 192.168.1.50;
#    filename "/tftpboot/X86PC/UNDI/BStrap/bstrap.0";
#        option dhcp-client-identifier 00:80:29:e5:b7:1f;
#        option root-path "/emb/root-fs";
--------------------------------------------------------------------

With version 2.0.xx of the DHCP demon we saw the following information
in /var/log/message:
#Mar  5 09:36:52 localhost dhcpd: BOOTREQUEST from 00:80:29:e5:b7:1f via
eth0
#Mar  5 09:36:52 localhost dhcpd: No applicable record for BOOTP host
00:80:29:e5:b7:1f via eth0

With the lates verison (3.0.pl1) from www.isc.org we got the same
behavior but no
error log in the message file.

We studdied the man pages and other sources of information but now run
out of ideas.

Please help,  any suggestions are wlcome.

    Guenter

2. Lex and Yacc

3. DHCPD as a replacement to BOOTP

4. network card problem

5. bootp vs DHCPD

6. 3Com SuperStack II Router

7. bootp/dhcpd

8. Where to Find PBMPLUS for SunSparc (SunOS4.1.x)???

9. dhcpd ignores bootp requests

10. linux-2.1.122 and nfsroot via dhcpd BOOTP

11. Running a DHCP server (in.dhcpd) while BOOTP server (bootps) is in inetd.conf?

12. Dhcpd failover - no bootp allowed.

13. Boot from EEPROM @ PCI-Card --> Boot from DHCPD/BOOTPD via Linux