Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The server starts up just fine. And it seems like the client pc's get contact with the server. When I run the server with the tags -d and -f, I get this output:
Code:
/usr/sbin/dhcpd -d -f
Internet Systems Consortium DHCP Server V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file
Wrote 0 leases to leases file.
No subnet declaration for eth2 (10.0.0.9).
** Ignoring requests on eth2. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface eth2 is attached. **
Listening on LPF/eth1/00:0a:cd:09:15:6d/10.0.1/24
Sending on LPF/eth1/00:0a:cd:09:15:6d/10.0.1/24
Sending on Socket/fallback/fallback-net
DHCPDISCOVER from 00:08:a1:2e:1b:cf via eth1
DHCPOFFER on 10.0.1.253 to 00:08:a1:2e:1b:cf (MAPSTER) via eth1
DHCPDISCOVER from 00:08:a1:2e:1b:cf (MAPSTER) via eth1
DHCPOFFER on 10.0.1.253 to 00:08:a1:2e:1b:cf (MAPSTER) via eth1
And the two last lines repeat as I try to update the ip on the client pc's, which are running windows btw.
Anybody who can explain to me why the clients doesn't receive the ip my server sends?
There's the old standby of wondering if there is a firewall isssue. But I also wonder if it is possible that your MS machine just doesn't like the address you are assigning. (I am most definitely not a MS guru.) You might try reducing your upper address a little and see if the problem clears up.
You can make sure the offers are actually leaving your machine using tcpdump. If they are leaving your machine, then I would think the problem would have to be with the MS box.
You can use the ethereal on the MS-box to capture packets and see whether ur getting things send by Linux on ur MS-box.
This may help you to narrow down( either on Linux or MS-box). then proceed to fix the issue..
(there are a few other DHCP messages but they are not usually part of the initial exchange)
It would appear that your client does not like the address it is being offered or it is not seeing the DHCPOFFER since it is continually issuing a DHCPDISCOVER request. More likely than not the client is not seeing the DHCPOFFER. I would use ethereal on both ends and see what packets each end is seeing.
Well, I just can't understand why it won't work... According to ethereal, my client does receive the dhcp offer.
dhcpd output:
Code:
DHCPDISCOVER from 00:08:a1:2e:1b:cf via eth1
DHCPOFFER on 10.0.1.253 to 00:08:a1:2e:1b:cf (MAPSTER) via eth1
DHCPDISCOVER from 00:08:a1:2e:1b:cf (MAPSTER) via eth1
DHCPOFFER on 10.0.1.253 to 00:08:a1:2e:1b:cf (MAPSTER) via eth1
DHCPDISCOVER from 00:08:a1:2e:1b:cf (MAPSTER) via eth1
DHCPOFFER on 10.0.1.253 to 00:08:a1:2e:1b:cf (MAPSTER) via eth1
DHCPDISCOVER from 00:08:a1:2e:1b:cf (MAPSTER) via eth1
DHCPOFFER on 10.0.1.253 to 00:08:a1:2e:1b:cf (MAPSTER) via eth1
TcpDump on server computer:
Code:
IP 169.254.113.139.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:08:a1:2e:1b:cf (oui Unknown), length 300
arp who-has 10.0.1.253 tell 10.0.1.1
IP 10.0.1.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
arp who-has 10.0.1.253 tell 10.0.1.1
arp who-has 10.0.1.253 tell 10.0.1.1
IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:08:a1:2e:1b:cf (oui Unknown), length 300
IP 10.0.1.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
IP 169.254.113.139.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
IP 169.254.113.139.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
IP 169.254.113.139.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:08:a1:2e:1b:cf (oui Unknown), length 300
IP 10.0.1.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
IPX 00000000.00:08:a1:2e:1b:cf.0453 > 00000000.ff:ff:ff:ff:ff:ff.0453: ipx-rip-resp 663045250/1.2
IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:08:a1:2e:1b:cf (oui Unknown), length 300
IP 10.0.1.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
IP 169.254.113.139.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
IP 169.254.113.139.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
Have you checked the settings on the the client pcs' firewalls? Specifically can a general broadcast message get through? If it is safe to do so (perhaps after disabling internet connection), you might try just dropping the firewall entirely as a troubleshooting technique.
If this doesn't work, try using the line
Code:
range dynamic-bootp 10.0.1.16 10.0.1.250;
in your dhcpd.conf file and restarting dhcpd in case (for whatever reason!) the MS computer doesn't like the address 10.0.1.253.
I've tried it without firewall, it doesn't do any difference. I've also tried to decrease the size of the subnet, I've even tried to specify an ip based on the fysical address of the ethernet card on the client computer.
The client does accept the ip assigned from my Netopia 3351 router, though. I'll try with another client soon...
That conf file doesn't seem to work either, so I believe that it isn't the conf file that is the problem. I see that I don't have a 255.255.255.255 route on the server computer and I believe I've read somwhere that it needs to be there, is that correct?
Edit: Somehow I got it working To be honest I don't really now what was wrong though. Newbie as I am with linux, I did a re-install of the distro... And suddenly it works I do believe it had something to do with iptables, I looked at it before I re-installed and discovered that it was empty. I don't know squat about iptables so I decided to do a re-install.
Oh, and thankz for all the help I got
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
To be honest I don't really now what was wrong though. Newbie as I am with linux, I did a re-install of the distro... And suddenly it works 
I do believe it had something to do with iptables, I looked at it before I re-installed and discovered that it was empty. I don't know squat about iptables so I decided to do a re-install. 
