On 03/29/2017 04:35 PM, Dan Sneddon wrote:
> On 03/29/2017 10:43 AM, Chris Novakovic wrote:
>> On 29/03/2017 18:13, Kurt H Maier wrote:
>>> On Wed, Mar 29, 2017 at 02:48:48PM +0200, Floris Bos wrote:
>>>> The PXE boot firmware implementation of the Raspberry Pi 3
>>>> has a bug causing it to fail if it receives replies
>>> Why not have a configurable dhcp-delay setting instead of putting
>>> device-specific quirks into the source code of dnsmasq forever?
>> +1 for a dhcp-delay setting, ideally per-MAC: the Ethernet adapters on
>> older RPi models (as well as the built-in wifi adapter on the RPi 3)
>> also use the b8:27:eb OUI, and this artificial delay oughtn't be applied
>> to them.
> Another +1 for adding a dhcp-delay setting on a per-MAC basis.
PXE devices are limited. I guess in a way of thinking that is
intentionally so. A server side robustness action is a valid use case
consideration. I would suggest the "tag" option method. You can tag a
network if say a whole subnet was only to serve PXE security cameras.
You can tag a partial MAC (wildcard) to ID a manufacturer. Assign the
delay option to the tag. This is just like DHCP "need broadcast" and
other client-server quirks.
Dnsmasq-discuss mailing list