[et-mgmt-tools] DHCP Troubleshooting

[Pablo Iranzo Gómez]

	Ole, try with

	authoritative;





-- 
Pablo Iranzo Gómez
(http://Alufis35.uv.es/~iranzo/)
(PGPKey Available on http://www.uv.es/~iranzop/PGPKey.pgp)
                  --
Postulado de Boling sobre la Ley de Murphy:

Si se encuentra bien, no se preocupe. Se le pasará

On Mon, 2 Jun 2008, Ole Ersoy wrote:

> Hi,
>
> I've been attempting an install for a while now and playing around with a lot of settings.  At this point my client just says "No DHCP Lease Offer Received".  However /var/log/messages looks like this:
>
> Jun  2 12:55:05 localhost dhcpd: DHCPDISCOVER from 00:16:ec:cc:d1:f6 via eth0
> Jun  2 12:55:05 localhost dhcpd: DHCPOFFER on 192.168.1.2 to 00:16:ec:cc:d1:f6 via eth0
> Jun  2 12:55:28 localhost dhcpd: DHCPDISCOVER from 00:16:ec:cc:d1:f6 via eth0
> Jun  2 12:55:28 localhost dhcpd: DHCPOFFER on 192.168.1.2 to 00:16:ec:cc:d1:f6 via eth0
> Jun  2 12:55:30 localhost dhcpd: DHCPDISCOVER from 00:16:ec:cc:d1:f6 via eth0
> Jun  2 12:55:30 localhost dhcpd: DHCPOFFER on 192.168.1.2 to 00:16:ec:cc:d1:f6 via eth0
> Jun  2 12:55:34 localhost dhcpd: DHCPDISCOVER from 00:16:ec:cc:d1:f6 via eth0
> Jun  2 12:55:34 localhost dhcpd: DHCPOFFER on 192.168.1.2 to 00:16:ec:cc:d1:f6 via eth0
> Jun  2 12:55:42 localhost dhcpd: DHCPDISCOVER from 00:16:ec:cc:d1:f6 via eth0
> Jun  2 12:55:42 localhost dhcpd: DHCPOFFER on 192.168.1.2 to 00:16:ec:cc:d1:f6 via eth0
>
> So it looks like the client is asking for a lease, and the server is responding with one, but the client does not see it...Could it be that the dhcp configuration is sending something the client does not understand?  My configuration file looks like this?
>
> ddns-update-style interim;
>
> allow booting;
> allow bootp;
> #if $omapi_enabled
> omapi-port $omapi_port;
> #end if
>
> ignore client-updates;
> set vendorclass = option vendor-class-identifier;
>
> subnet 192.168.1.0 netmask 255.255.255.0 {
>     option routers          192.168.1.1;
>     option subnet-mask      255.255.255.0;
>     range dynamic-bootp     192.168.1.100 192.168.1.254;
>     filename                "pxelinux.0";
>     default-lease-time      21600;
>     max-lease-time          43200;
>     next-server             $next_server;
> }
>
> $insert_cobbler_system_definitions
>
> It's weird because the client was getting a lease earlier today, right up to the point where I actually managed to almost install a distro using cobbler (Almost because there was a hiccup in the kickstart template), and since then I've tried various permutations of all the settings including:
>
> - removing the system added
> - removing the profile (Just testing pure dhcp)
> - Toggling omapi_enabled
> - Running with non managed dhcp (Similar configuration)
> - Reinstalling cobbler and setting everything up from scratch
> - Double check that DHCP is disabled on the router
> - Completely disabled the firewall
> - ...
>
> I used yum to reinstall and it looks like cobbler-1.0.0-2.fc has made it into the repository now, so that's what I'm running with.
>
> Any ideas?
>
> TIA,
> - Ole
>
>
> _______________________________________________
> et-mgmt-tools mailing list
> et-mgmt-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/et-mgmt-tools
>