Double DHCPDISCOVER ends with DHCPNAK
Miquel Mauri
mmauri at mgc.es
Tue Mar 8 15:00:26 UTC 2011
It is not an error, the netmask is 255.255.248.0.
I tried booting with the class and it seems ok, for PXE the server
offers an address and for ubuntu
another and the cliente starts correctly. When I restarted the client
the PXE goes ok but the ubuntu
fails again, the server offers same IP offered before but it ends with
DHCPNAK and client never starts...
The server is not modified by us, it is the Debian 6 version.
El ds 05 de 03 de 2011 a les 00:19 +1100, en/na Glenn Satchell va
escriure:
> In your logs the client is getting the address 192.1.3.191, but there is
> no definition for that range or subnet in the dhcpd.conf you posted.
> Perhaps that is just a cut and paste error?
>
> I don't know for sure but perhaps ubuntu does not like some of the dhcp
> options being sent in the second boot stage?
>
> Usually PXE options can be set in a class so they are only sent during
> the PXE boot. Here's the settings I use:
>
> # PXE boots for jumpstarting x86 boxes
> class "PXE" {
> match if substring(option vendor-class-identifier, 0, 9) = "PXEClient";
> option root-path "ltsp-mgc.mgc.es:/opt/ltsp/i386";
> next-server ltsp-mgc.mgc.es;
> filename "/ltsp/i386/pxelinux.0";
> }
>
> Thus when the boot request contains the PXEclient vendor class
> identifier the PXE options will be set, and they will not be set in the
> second boot stage.
>
> If this does not help you will need to use tcpdump to capture the
> packets to see what options are set.
>
> regards,
> -glenn
>
> On 03/04/11 23:41, Miquel Mauri wrote:
> > This are my dhcpd.conf relevant lines:
> >
> > authoritative;
> > server-identifier galaxia.mgc.es;
> > option time-servers cosmos.mgc.es;
> > ddns-updates false;
> > ddns-update-style none;
> > option root-path "ltsp-mgc.mgc.es:/opt/ltsp/i386";
> > next-server ltsp-mgc.mgc.es;
> > filename "/ltsp/i386/pxelinux.0";
> > shared-network mutua {
> > subnet 192.1.0.0 netmask 255.255.248.0 {
> > option nntp-server 192.1.1.253;
> > range 192.1.1.161 192.1.1.180;
> > range 192.1.2.1 192.1.7.254;
> > option broadcast-address 192.1.7.255;
> > option subnet-mask 255.255.248.0;
> > option routers 192.1.1.249;
> > option domain-name-servers 192.1.1.252, 192.168.48.251;
> > option domain-name "mgc.es";
> > default-lease-time 3600;
> > max-lease-time 3600;
> > }
> > }
> > host il-mfont { hardware ethernet 00:11:2f:b9:7b:b9; fixed-address
> > 192.1.1.101;}
> > host il-apinyol { hardware ethernet 00:13:d4:e8:69:19; fixed-address
> > 192.1.1.102;}
> > host il-garita { hardware ethernet 00:07:95:c7:8a:2f; fixed-address
> > 192.1.1.103;}
> > host il-pmoreno { hardware ethernet 00:0a:5e:4b:2d:8c; fixed-address
> > 192.1.1.104;}
> > host il-taulell-3 { hardware ethernet 00:0a:5e:4f:d9:0b; fixed-address
> > 192.1.1.105;}
> > host il-acarol { hardware ethernet 00:13:d4:e8:69:09; fixed-address
> > 192.1.1.106;}
> > host il-mlacruz { hardware ethernet 00:04:75:b4:de:bc; fixed-address
> > 192.1.1.107;}
> > host il-nbadenas { hardware ethernet 00:0a:5e:58:6a:57; fixed-address
> > 192.1.1.108;}
> > host il-mmasabe { hardware ethernet 00:0a:5e:1d:68:e1; fixed-address
> > 192.1.1.109;}
> > host il-emartin { hardware ethernet 00:0a:5e:58:6a:03; fixed-address
> > 192.1.1.110;}
> > host il-jcavalieri { hardware ethernet 00:13:d4:e8:69:6d; fixed-address
> > 192.1.1.111;}
> > host il-jgarcia { hardware ethernet 00:13:f7:54:f5:df; fixed-address
> > 192.1.1.112;}
> > host il-smartinpo { hardware ethernet 00:13:f7:66:b5:28; fixed-address
> > 192.1.1.113;}
> > host il-rmartos { hardware ethernet 00:0a:5e:5e:1e:a7; fixed-address
> > 192.1.1.114;}
> > host il-nbeltran { hardware ethernet 00:13:f7:d1:a1:8e; fixed-address
> > 192.1.1.115;}
> > host il-cjosa { hardware ethernet 00:0a:5e:4c:da:fc; fixed-address
> > 192.1.1.116;}
> >
> > Thanks,
> > Miquel.
> >
> > El dv 04 de 03 de 2011 a les 23:27 +1100, en/na Glenn Satchell va escriure:
> >> Please post your dhcpd.conf, or if it is a very big file then the
> >> relevant bits (global declarations, classes, the subnet and any host
> >> statements for that client). We can't tell what the problem is with only
> >> the logs.
> >>
> >> regards,
> >> -glenn
> >>
> >> On 03/04/11 21:48, Miquel Mauri wrote:
> >> > Somebody can help me?
> >> >
> >> > I don't know why this occurs.
> >> >
> >> > Thanks,
> >> > Miquel.
> >> >
> >> > El dj 03 de 03 de 2011 a les 13:04 +0100, en/na Miquel Mauri va
> >> > escriure:
> >> >> Hello,
> >> >>
> >> >> We boot machines over network with TFTP and after the image is
> >> >> downloaded it starts Ubuntu.
> >> >> The problem comes with the DHCPDISCOVER requested in Ubuntu start. The
> >> >> server offers the
> >> >> same IP offered before, but when the client requests this IP the
> >> >> server tells that is not available
> >> >> and the client machine never starts. The server runs 4.1.1-P1 on
> >> >> Debian 6.
> >> >>
> >> >> This are the syslog messages:
> >> >>
> >> >> Mar 3 12:51:01 galaxia dhcpd: DHCPDISCOVER from 00:50:56:97:6d:a8 via
> >> >> eth0
> >> >> Mar 3 12:51:02 galaxia dhcpd: DHCPOFFER on 192.1.3.191 to
> >> >> 00:50:56:97:6d:a8 via eth0
> >> >> Mar 3 12:51:03 galaxia dhcpd: DHCPREQUEST for 192.1.3.191
> >> >> (192.1.1.240) from 00:50:56:97:6d:a8 via eth0
> >> >> Mar 3 12:51:03 galaxia dhcpd: DHCPACK on 192.1.3.191 to
> >> >> 00:50:56:97:6d:a8 via eth0
> >> >> Mar 3 12:51:12 galaxia dhcpd: DHCPDISCOVER from 00:50:56:97:6d:a8 via
> >> >> eth0
> >> >> Mar 3 12:51:12 galaxia dhcpd: DHCPOFFER on 192.1.3.191 to
> >> >> 00:50:56:97:6d:a8 via eth0
> >> >> Mar 3 12:51:12 galaxia dhcpd: DHCPREQUEST for 192.1.3.191
> >> >> (192.1.1.240) from 00:50:56:97:6d:a8 via eth0: lease 192.1.3.191
> >> >> unavailable.
> >> >> Mar 3 12:51:12 galaxia dhcpd: DHCPNAK on 192.1.3.191 to
> >> >> 00:50:56:97:6d:a8 via eth0
> >> >> Mar 3 12:51:16 galaxia dhcpd: DHCPDISCOVER from 00:50:56:97:6d:a8 via
> >> >> eth0
> >> >> Mar 3 12:51:16 galaxia dhcpd: DHCPOFFER on 192.1.3.191 to
> >> >> 00:50:56:97:6d:a8 via eth0
> >> >> Mar 3 12:51:16 galaxia dhcpd: DHCPREQUEST for 192.1.3.191
> >> >> (192.1.1.240) from 00:50:56:97:6d:a8 via eth0: lease 192.1.3.191
> >> >> unavailable.
> >> >> Mar 3 12:51:16 galaxia dhcpd: DHCPNAK on 192.1.3.191 to
> >> >> 00:50:56:97:6d:a8 via eth0
> >> >> Mar 3 12:51:19 galaxia dhcpd: DHCPDISCOVER from 00:50:56:97:6d:a8 via
> >> >> eth0
> >> >> Mar 3 12:51:19 galaxia dhcpd: DHCPOFFER on 192.1.3.191 to
> >> >> 00:50:56:97:6d:a8 via eth0
> >> >> Mar 3 12:51:19 galaxia dhcpd: DHCPREQUEST for 192.1.3.191
> >> >> (192.1.1.240) from 00:50:56:97:6d:a8 via eth0: lease 192.1.3.191
> >> >> unavailable.
> >> >> Mar 3 12:51:19 galaxia dhcpd: DHCPNAK on 192.1.3.191 to
> >> >> 00:50:56:97:6d:a8 via eth0
> >> >> Mar 3 12:51:22 galaxia dhcpd: DHCPDISCOVER from 00:50:56:97:6d:a8 via
> >> >> eth0
> >> >> Mar 3 12:51:22 galaxia dhcpd: DHCPOFFER on 192.1.3.191 to
> >> >> 00:50:56:97:6d:a8 via eth0
> >> >>
> >> >> Thanks in advance,
> >> >> Miquel.
> >> >>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
*****************************************************************************************************************************************
Aquest missatge s'envia des del sistema informàtic de M.G.C., i va dirigit exclusivament al seu destinatari, pot contenir informació confidencial o privilegiada. Si el receptor no fos el destinatari, preguem ens ho comuniqui el més aviat possible. No està permès realitzar còpies parcials o totals del seu contingut, ni la seva divulgació a persona diferent al seu destinatari.
Este mensaje se envía desde el sistema informático de M.G.C., y va dirigido exclusivamente a su destinatario, pudiendo contener información confidencial o privilegiada. Si el receptor no fuera el destinatario, rogamos nos lo comunique cuanto antes. No está permitido realizar copias parciales o totales de su contenido, ni su divulgación a persona diferente de su destinatario.
*****************************************************************************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20110308/38013a32/attachment.html>
More information about the dhcp-users
mailing list