| 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
| ||
|
Date: Mon, 03 Oct 2011 19:12:20 -0600 From: Robert Hancock <hancockrwd@...il.com> To: Chris Friesen <chris.friesen@...band.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 05:36 PM, Chris Friesen wrote: > On 10/03/2011 05:21 PM, David Miller wrote: >> From: John Musbach<johnmusbach1@...il.com> >> Date: Mon, 3 Oct 2011 23:18:06 +0000 (UTC) >> >>> Hello, I am configuring a network that'll have multiple DHCP servers >>> and I was wondering how Linux handles receiving multiple DHCP OFFERs? >>> More specifically, how does it choose which one to prefer and how long >>> will it wait for a answer from a preferred server if the other server >>> answers first? Thanks. >> >> 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? > > Chris > 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. -- 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