On Sun, Dec 18, 2016 at 10:28:03PM +0100, Pali Rohár wrote:
> On Sunday 18 December 2016 21:32:32 Geert Stappers wrote:
> >
> > if substring (option vendor-class-identifier, 0, 3) = "d-i" {
> > filename "http://host/preseed.cfg";;
> > }
> >
> > Note that the above example limits this filename to DHCP clients that
> > identify themselves as "d-i", so it will not affect regular DHCP
> > clients, but only the installer. You can also put the text in a
> > stanza for only one particular host to avoid preseeding all installs
> > on your network. </quote>
<snip/>
> > I think that bugreporter is missing that there are *2* DHCP requests.
>
> I know that they are two DHCP requests. Problem is that Debian installer
> try to interpret bootfile (returned by second request) as preseed file
> even it is not preseed file (but looks like URL).
The DHCP bootfilename in the second request, the d-i request,
should point to a preseedfile ...
> And I consider this as a bug.
[1]
> As more things can look like URL, e.g.
> iPXE script which can also be in bootfile option.
>
> > One from a bootROM as iPXE and the other DHCP request by
> > Debian-Installer. (Hence the "if statement" in the manual ( quoted
> > above ) that should go into DHCP server configuration)
> >
> > On "CDROM boot" or "USBstick boot" there is the same Debian-Installer
> > code that does network configuration, which uses DHCP.
> >
> >
> > Advice: Networksniff (tcpdump, wireshark, tshark) the whole
> > installation. Pay special attention to the DHCP request by
> > Debian-Installer which can be recognisted on "d-i". Check that the
> } DHCP reply has the URL of the wanted preseed file.
>
> I know what is happening there...
Then show your networksniff to the world.
I here by volenteer to analyze .pcap files.
Groeten
Geert Stappers
[1] Space left blank, because it is way too easy to fuel a flame war.
--
Leven en laten leven
Attachment:
signature.asc
Description: Digital signature