lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 04 Oct 2011 08:31:59 -0600
From:	Chris Friesen <chris.friesen@...band.com>
To:	Robert Hancock <hancockrwd@...il.com>
CC:	David Miller <davem@...emloft.net>, johnmusbach1@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: Handling of multiple DHCP OFFERs

On 10/03/2011 07:12 PM, Robert Hancock wrote:
> On 10/03/2011 05:36 PM, Chris Friesen wrote:
>> On 10/03/2011 05:21 PM, David Miller wrote:

>>> There are multiple userspace implementations of DHCP, and the kernel
>>> does not usually get involved at all. You'll therefore have to ask
>>> the folks who write and maintain the various DHCP implementations.
>>
>> What about netbooting? Or are you expecting people to use initramfs with
>> a userspace implementation?
>
> Normally with PXE boot it's the PXE ROM that initially gets the IP
> address. After the kernel boots up, userspace normally repeats the process.

I've worked with quite a few boards where PXE boots the kernel, but the 
kernel needs to do DHCP to get the location of the root filesystem (as 
well as various DHCP options not understood by PXE).

Chris




-- 
Chris Friesen
Software Developer
GENBAND
chris.friesen@...band.com
www.genband.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ