Hi im trying to configure centos to run as a dhcpd daemon but it simply doesnt work I'm using the default configuration file from dhcdp (and tried multiple alternatives). problem is that pxe clients do not aquire dhcp addresses in the log i can see that there are 3 or 4 dhcp offers per boot atempt but no dhcp requests anyone? i'm going crazy here... .i've tryed 3 diferent machines (servers) and 4 or 5 diferent clients sometimes windows clients are able to catch the ip but only sometimes. maybe this is a route problem? the machine(s) was freshly installed with centos 4.3 please advise! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20061124/7d5815bd/attachment-0002.html>
sorry... i've finaly figured out dhcpd needs a working dns server or entries in the hosts file no comments. _____ From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Daniel Teixeira Sent: sexta-feira, 24 de Novembro de 2006 19:04 To: 'CentOS mailing list' Subject: [CentOS] dhcpd Hi im trying to configure centos to run as a dhcpd daemon but it simply doesnt work I'm using the default configuration file from dhcdp (and tried multiple alternatives). problem is that pxe clients do not aquire dhcp addresses in the log i can see that there are 3 or 4 dhcp offers per boot atempt but no dhcp requests anyone? i'm going crazy here... .i've tryed 3 diferent machines (servers) and 4 or 5 diferent clients sometimes windows clients are able to catch the ip but only sometimes. maybe this is a route problem? the machine(s) was freshly installed with centos 4.3 please advise! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20061124/4ef86b80/attachment-0002.html>
sorry but this is really strange my dhcpd daemon only works sometimes!!!!!! the problem is the same as before dhcpoffer is beeing sent but with no further actions --------------my dhcpd.conf: ddns-update-style ad-hoc; option subnet-mask 255.255.0.0; option broadcast-address 10.0.255.255; option routers 10.0.150.100; option domain-name-servers 10.0.150.100; option domain-name "domain.lan"; option option-128 code 128 = string; option option-129 code 129 = text; get-lease-hostnames true; next-server 10.0.150.100; option root-path "10.0.150.100:/opt/ltsp/i386"; subnet 10.0.150.0 netmask 255.255.255.0 { range 10.0.150.200 10.0.150.254; if substring (option vendor-class-identifier, 0, 9) = "PXEClient" { filename "/lts/2.6.16.1-ltsp-1/pxelinux.0"; } else{ filename "/lts/vmlinuz-2.6.16.1-ltsp-1"; } host teste { hardware ethernet 44:4d:50:e1:25:a9; fixed-address 10.0.150.234; } ----------ifcfg-eth0: DEVICE=eth0 BOOTPROTO=none BROADCAST=10.0.255.255 HWADDR=00:04:76:28:95:AB IPADDR=10.0.150.100 NETMASK=255.255.0.0 NETWORK=10.0.0.0 ONBOOT=yes TYPE=Ethernet USERCTL=no IPV6INIT=no PEERDNS=yes GATEWAY=10.0.0.1 ---------route Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.0 * 255.255.0.0 U 0 0 0 eth0 PLEASE Help ! :-( _____ From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Daniel Teixeira Sent: sexta-feira, 24 de Novembro de 2006 19:04 To: 'CentOS mailing list' Subject: [CentOS] dhcpd Hi im trying to configure centos to run as a dhcpd daemon but it simply doesnt work I'm using the default configuration file from dhcdp (and tried multiple alternatives). problem is that pxe clients do not aquire dhcp addresses in the log i can see that there are 3 or 4 dhcp offers per boot atempt but no dhcp requests anyone? i'm going crazy here... .i've tryed 3 diferent machines (servers) and 4 or 5 diferent clients sometimes windows clients are able to catch the ip but only sometimes. maybe this is a route problem? the machine(s) was freshly installed with centos 4.3 please advise! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20061124/cd4ad1f0/attachment-0002.html>
> my dhcpd daemon only works sometimes!!!!!!It smells like you need an authoritative statement for your dhcpd.conf. This is done by adding the following to the top of your dhcpd.conf: authoritative; -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell
possible you have some intermitten network issues? Quoting Daniel Teixeira <dteixeira at bitecnica.com>:> Hi > im trying to configure centos to run as a dhcpd daemon but it simply doesnt > work > > I'm using the default configuration file from dhcdp (and tried multiple > alternatives). > > problem is that pxe clients do not aquire dhcp addresses > in the log i can see that there are 3 or 4 dhcp offers per boot atempt but > no dhcp requests > > anyone? > > i'm going crazy here... .i've tryed 3 diferent machines (servers) and 4 or 5 > diferent clients > sometimes windows clients are able to catch the ip but only sometimes. > > > maybe this is a route problem? > > the machine(s) was freshly installed with centos 4.3 > > > please advise! >thanks, -Nathan -http://www.netdigix.net
Daniel Teixeira spake the following on 11/24/2006 1:27 PM:> sorry but this is really strange > > my dhcpd daemon only works sometimes!!!!!! > > the problem is the same as before > dhcpoffer is beeing sent but with no further actions > > --------------my dhcpd.conf: > > > ddns-update-style ad-hoc; > > option subnet-mask 255.255.0.0; > option broadcast-address 10.0.255.255; > option routers 10.0.150.100; > option domain-name-servers 10.0.150.100; > option domain-name "domain.lan"; > option option-128 code 128 = string; > option option-129 code 129 = text; > > get-lease-hostnames true; > > next-server 10.0.150.100; > option root-path "10.0.150.100:/opt/ltsp/i386"; > > subnet 10.0.150.0 netmask 255.255.255.0 { > range 10.0.150.200 10.0.150.254; > if substring (option vendor-class-identifier, 0, 9) = "PXEClient" { > filename "/lts/2.6.16.1-ltsp-1/pxelinux.0"; > } > else{ > filename "/lts/vmlinuz-2.6.16.1-ltsp-1"; > } > > host teste { > hardware ethernet 44:4d:50:e1:25:a9; > fixed-address 10.0.150.234; > } > ----------ifcfg-eth0: > > > DEVICE=eth0 > BOOTPROTO=none > BROADCAST=10.0.255.255 > HWADDR=00:04:76:28:95:AB > IPADDR=10.0.150.100 > NETMASK=255.255.0.0 > NETWORK=10.0.0.0 > ONBOOT=yes > TYPE=Ethernet > USERCTL=no > IPV6INIT=no > PEERDNS=yes > GATEWAY=10.0.0.1 > > > > > ---------route > Destination Gateway Genmask Flags Metric Ref Use > Iface > 10.0.0.0 * 255.255.0.0 U 0 0 0 eth0 > > PLEASE Help ! :-( > > ------------------------------------------------------------------------ > *From:* centos-bounces at centos.org > [mailto:centos-bounces at centos.org] *On > Behalf Of *Daniel Teixeira > *Sent:* sexta-feira, 24 de Novembro de 2006 19:04 > *To:* 'CentOS mailing list' > *Subject:* [CentOS] dhcpd > > Hi > im trying to configure centos to run as a dhcpd daemon but it simply > doesnt work > > I'm using the default configuration file from dhcdp (and tried multiple > alternatives). > > problem is that pxe clients do not aquire dhcp addresses > in the log i can see that there are 3 or 4 dhcp offers per boot atempt > but no dhcp requests > > anyone? > > i'm going crazy here... .i've tryed 3 diferent machines (servers) and 4 > or 5 diferent clients > sometimes windows clients are able to catch the ip but only sometimes. > > > maybe this is a route problem? > > the machine(s) was freshly installed with centos 4.3 > > > please advise!I don't think the ad-hoc ddns updates will work without the proper keys for rndc included. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!
On 24/11/06, Daniel Teixeira <dteixeira at bitecnica.com> wrote:> > sorry but this is really strange > > my dhcpd daemon only works sometimes!!!!!! > > the problem is the same as before > dhcpoffer is beeing sent but with no further actionsI'd recommend avoiding RTF/HTML mails to mailing lists, they're generally frowned upon. As is top-posting. Just a friendly prod, I don't mind as-such but I know if irks a lot of people. Is your problem specific to a particular hardware platform? I've had IBM systems that have caused me all sorts of headaches when Dell kit has been fine and vice versa. Does upping the logging on the TFTPd give you any additional information? What about the other VTYs when you're netbooting a "client"? Will.