Jump to content

dhcp problem with Mandriva 2006 [solved]


aioshin
 Share

Recommended Posts

ok, here's the scenario:

 

well, these is the result of my previous post about replacing Xandros with Mandriva.. now Im replacing it..and the problem:

 

Configured 2006 as dhcp server.

.

I have several ThinClients PC and 2 DiskLess Desktop.. the thinclient boot directly from mandy 2006 via dhcp and fine, its working. Now I have here a remaining 2 Desktop acting as thinClients, Im using a floppy to boot to 2006 using Rom-O-Matic. I know there's no problem with the client since it already been booting fine on the Previous OS, Xandros. But now, on 2006, it just gave me a message :

 

Searching for DHCP Server... NO IP address

then how come that happened?, while the other had been able to connect to dhcp server.

ok, here's my Config below and please help me, Im scratching my head now :wall:

ddns-update-style			   none;
default-lease-time			  21600;
max-lease-time				  21600;
option subnet-mask			 255.255.255.0;
option broadcast-address	 172.16.0.255;
option routers					 172.16.0.1;
option domain-name-servers   2x.xx.xx.xx;
option domain-name		   "mydomain.com";		  # <--Fix this domain name
option root-path			 "172.16.0.150:/opt/ltsp/i386";
option option-128 code 128 = string;
option option-129 code 129 = text;
subnet 172.16.0.0 netmask 255.255.255.0 {
use-host-decl-names	  on;
range	   172.16.0.150	172.16.0.180;
filename	"/lts/2.6.16.1-ltsp-2/pxelinux.0";
## If you want to use static IP address for your worksations, then un-comment
## the following section and modify to suit your network.
## Then, duplicate this section for each workstation that needs a static
## IP address.
		  }
#
host ws151	  {
	hardware ethernet	   00:00:90:63:96:39;
	fixed-address		   172.16.0.151;
	filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
			}
#
host ws152
			{
hardware ethernet	 00:46:t7:7E:4p:2D;
fixed-address		 172.16.0.152;
filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
				}
#
host ws153	 {
	hardware ethernet	 00:07:55:B3:91:41;
	fixed-address		   172.16.0.153;
	filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
			}
#
host ws154
	 {
	hardware ethernet	   00:11:5B:2A:94:CE;
	fixed-address		 172.16.0.154;
	filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
	  }
#
host ws155
			{
   hardware ethernet	   00:40:C3:74:84:0B;
  fixed-address		   172.16.0.155;
 filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
		 }
#
host ws156	 {
	hardware ethernet	   00:07:55:63:76:2C;
	fixed-address		   172.16.0.156;
	filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
			}
}

 

hosts ws152 and ws155 are the ones that cannot see the dhcp server, Is there something wrong with the config?

Even if I will comment on the entries of those hosts, so it will just be offered by dhcp with dynamic address, but still it wont be able to see the dhcp server...

.

Firewall supposedly is not an issue here since the other were able to connect to the dhcp server, and they are on the same network, :wall:

.

Ok, I tried to build another dhcp server (for testing), I have a running centos, installed dhcp-server there and copy and paste the entries of the said hosts on its dhcp.conf then restart those said hosts, you know what?, it was able to see that Dhcp server.. I really dont know what is the problem with 2006..

 

any help here is very much appreciated..

 

TIA!

Link to comment
Share on other sites

host ws152

{

hardware ethernet 00:46:t7:7E:4p:2D;

fixed-address 172.16.0.152;

filename "/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";

}

 

#

host ws155

{

hardware ethernet 00:40:C3:74:84:0B;

fixed-address 172.16.0.155;

filename "/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";

}

#

 

hardware for ws152 cannot be t7 check what the card mac address is.

 

and check your bracketing and spacing not sure but the others are all the same not these two..

Link to comment
Share on other sites

hardware for ws152 cannot be t7 check what the card mac address is.

 

and check your bracketing and spacing not sure but the others are all the same not these two..

 

actually, I just scrumbled those mac address since those are directly connected to internet, so there is nothing wrong with those.. but thanks for the reply anyway..

.

well, I found it, the culprit of my config.. almost a day I tried to look for the cause... and here it is

 

Link

The default value of the Siaddr field has changed

 

The ISC guys have decided to change the default behaviour of the Siaddr field between release 3.0.2 and 3.0.3.

 

Note that this change was considered to harmful by the ubuntu development team (its not nice to break user configurations with a minor version upgrade), it was reverted in ubuntu, so the following can be ignored by ubuntu users.

 

Fortunately, there's a simple fix.

 

The fix:

 

In the dhcpd.conf file, you need to add a line like this:

 

next-server 192.168.0.254;

 

 

That entry should go near the top, so that it applies to ALL terminals. Make sure you put your server IP address in that entry..

 

 

 

The reason for the breakage:

 

In the DHCP reply offered by the server, there's a field called siaddr. This field is supposed to contain the IP address of the boot server. In versions of ISC dhcpd prior to 3.0.3, this field always defaulted to the value of the IP address of the dhcp server. As of ISC dhcpd version 3.0.3, it is now being zero filled.

 

Here's the entry in the release notes that describe the change that was made:

 

- The siaddr field was being improperly set to the server-identifier when

responding to DHCP messages. RFC2131 clarified the siaddr field as

meaning the 'next server in the bootstrap process', eg a tftp server.

The siaddr field is now left zeroed unless next-server is configured.

 

 

I've submitted a bug report to ISC, explaining that I think the field shouldn't default to zeros. We'll see if they accept it as a bug, and fix it for the next version. If not, then at least we have the easy fix of adding the 'next-server' entry to dhcpd.conf.

 

Thanks to Anselm Martin Hoffmeister, for spending the time last weekend tracking down this issue.

 

Jim McQuillan - Sept 9, 2005

 

So on my config...for example on the host ws152 entry...

 

host ws152
			{
hardware ethernet	 00:46:t7:7E:4p:2D;
fixed-address		 172.16.0.152;
filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
				}

I inserted next-server 172.16.0.150; on it

host ws152
			{
hardware ethernet	 00:46:t7:7E:4p:2D;
fixed-address		 172.16.0.152;
next-server			172.16.0.150;
filename				"/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0";
				}

 

which actually the same server that gaves those other thinclients a dhcp offer, while not using that particular entry...

.

.

.

:D

Edited by aioshin
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...