Setting up udhcpd on mdk 10.0

[_Qwerty_]

Hello!

I try to setup a dhcp server on my mdk 10.0 server. At first I tried "urpmi dhcpd" which have worked on some previous versions if I remember right. Now it said that I could choose between udhcpd and tcpdump, and I installed udhcpd (and later on I have installed tcpdump too, trying to troubleshoot)

 

 

This is my network setup:

 

Internet

|

Mdk 10.0 server (two nics and 192.168.5.1 on eth0, nat and ip masq is done with ipkungfu)

|

|---------- Windows ME client

|

|-----------My work laptop with win XP

 

Right now I only have an crossover cable from the linux server to the two clients. But Im planning on buying an switch, and thats why I really whant to get the dhcp server running/working so i can just plug in my cat5 cable and then bootup any client and start interact with the Internet.

 

I do have the windows me client connected to the internet, by telling it to use ip = 192.168.5.2

But my work laptop is set to get an ip automatically, since thats how it works at my work.

 

I tried to setup the /etc/udhcpd.conf and it seems to be fine, but still it doesent work yet...

 

# The start and end of the IP lease block
start           192.168.5.2     #default: 192.168.0.20
end             192.168.5.254   #default: 192.168.0.254
# The interface that udhcpd will use
interface       eth0            #default: eth0
# The location of the leases file
lease_file      /var/lib/udhcpd/udhcpd.leases
notify_file     dumpleases      # <--- usefull for debugging
opt     dns     192.168.5.1
option  subnet  255.255.255.0
opt     router  192.168.5.1
option  domain  local
option  lease   864000

The notify_file is empty I have noticed

 

The udhcpd server is running as i checked like this:

[root@qwerty qwerty]# service udhcpd status
udhcpd (pid 18128) is running...

 

And I also tried to look for request from the windows client with tcpdump and saw this:

[root@qwerty etc]# tcpdump -c 30
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
21:31:19.863912 IP 169.254.99.65.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
21:31:20.447580 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): RELEASE; REQUEST; BROADCAST
21:31:20.471101 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): RELEASE; REQUEST; BROADCAST
21:31:20.471269 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): RELEASE; REQUEST; BROADCAST
21:31:20.471435 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): RELEASE; REQUEST; BROADCAST
21:31:20.471599 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): RELEASE; REQUEST; BROADCAST
21:31:20.471769 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): RELEASE; REQUEST; BROADCAST
21:32:00.045516 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e4:4a:3d:e3, length: 300
21:32:03.049887 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e4:4a:3d:e3, length: 300
21:32:11.052003 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e4:4a:3d:e3, length: 300
21:32:28.057692 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e4:4a:3d:e3, length: 300
21:33:00.068977 arp who-has 169.254.99.65 tell 169.254.99.65
21:33:00.706890 arp who-has 169.254.99.65 tell 169.254.99.65
21:33:01.708410 arp who-has 169.254.99.65 tell 169.254.99.65
21:33:02.790559 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
21:33:03.541252 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
21:33:04.292387 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
21:33:04.743743 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e4:4a:3d:e3, length: 300
21:33:05.043522 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
21:33:05.795121 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
21:33:06.545792 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
21:33:07.296932 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
21:33:08.048068 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
21:33:08.749242 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e4:4a:3d:e3, length: 300
21:33:09.020461 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
21:33:09.037875 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
21:33:09.392311 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
21:33:09.770666 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
21:33:09.780630 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
21:33:10.141241 IP 169.254.99.65.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
30 packets captured
30 packets received by filter
0 packets dropped by kernel

But I dont know what to make of it. It seems that the windows client asks for dhcp info, but not gets it, at least thats my guess. But why?

 

my eth0 are configured right, otherwise I wouldent be able to get connected when i use the windows me client I assume, but here is the settings:

[root@qwerty qwerty]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:50:BF:E7:70:1A
         inet addr:192.168.5.1  Bcast:192.168.5.255  Mask:255.255.255.0
         inet6 addr: fe80::250:bfff:fee7:701a/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:15318412 errors:0 dropped:0 overruns:0 frame:0
         TX packets:19475910 errors:0 dropped:0 overruns:0 carrier:0
         collisions:15593 txqueuelen:1000
         RX bytes:1788580612 (1705.7 Mb)  TX bytes:1587943175 (1514.3 Mb)
         Interrupt:5 Base address:0xa000

 

Any Ideas?, someone?

I have had an working setup with dhcpd back on mdk 9.2 with the same computers/hardware, but right now it wont work for me.

[papaschtroumpf]

I assume that you have only 1 computer (the Me client or the laptop) connected with the crossover cable at a time? It's not very clear

 

Did you try restarting that computer the clients? At the very least do ipconfig /release followed by ipconfig /renew in a does box.

 

The 169.254.... address you see in tcpdump is from a windows conputer that couldn't find a DHCP serverat boot, or wasn't configured for DHCP. That IP address range is the signature of the DCHP-less automatic IP provisionning that M$ does.

 

The DHCP request I would have expected to be DHCP Discover. I'm guessing the client is asking for an IP adress it used to have, which might be why it's not getting an answer? A more detailed dump would be more useful.

 

Start by rebooting the clients while connected to the DCHP server.

Edited September 22, 2004 by papaschtroumpf