Re: [Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

2017-03-30 Thread Floris Bos
On 03/29/2017 07:43 PM, Chris Novakovic wrote: +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. Note that if you are using

Re: [Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

2017-03-30 Thread Pali Rohár
On Wednesday 29 March 2017 23:22:39 Eric Luehrsen wrote: > 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 imple

Re: [Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

2017-03-29 Thread Eric Luehrsen
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 i

Re: [Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

2017-03-29 Thread Dan Sneddon
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 >>> instantly. >>> >>> As a

Re: [Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

2017-03-29 Thread Kurt H Maier
On Wed, Mar 29, 2017 at 08:48:30PM +0200, Floris Bos wrote: > > > > I'm not sure hardcoding an entire OUI is the right reaction to such > > opposition. > > So what do you propose that the reaction should be instead? In your specific case, I would use netem [1] to introduce a delay to inc

Re: [Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

2017-03-29 Thread Floris Bos
On 03/29/2017 07:49 PM, Kurt H Maier wrote: On Wed, Mar 29, 2017 at 07:17:41PM +0200, Floris Bos wrote: That was my first proposal. But there was opposition against introducing extra options. I'm not sure hardcoding an entire OUI is the right reaction to such opposition. So what do y

Re: [Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

2017-03-29 Thread Kurt H Maier
On Wed, Mar 29, 2017 at 07:17:41PM +0200, Floris Bos wrote: > > That was my first proposal. > But there was opposition against introducing extra options. I'm not sure hardcoding an entire OUI is the right reaction to such opposition. I'm also wary about hardcoding the duration.

Re: [Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

2017-03-29 Thread Chris Novakovic
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 >> instantly. >> >> As a workaround ensure there is a minimum delay of one >> s

Re: [Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

2017-03-29 Thread Floris Bos
On 03/29/2017 07:13 PM, 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 instantly. As a workaround ensure there is a minimum delay of one second if the

Re: [Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

2017-03-29 Thread Kurt H Maier
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 > instantly. > > As a workaround ensure there is a minimum delay of one > second if the client is a Pi. > > On Linux it look

Re: [Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

2017-03-29 Thread Albert ARIBAUD
Hi again, Le Wed, 29 Mar 2017 17:24:45 +0200 Floris Bos a écrit: > Hi, > > On 03/29/2017 05:02 PM, Albert ARIBAUD wrote: > > Le Wed, 29 Mar 2017 14:48:48 +0200 > > Floris Bos a écrit: > > > >> The PXE boot firmware implementation of the Raspberry Pi 3 > >> has a bug causing it to fail if it

Re: [Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

2017-03-29 Thread Floris Bos
Hi, On 03/29/2017 05:02 PM, Albert ARIBAUD wrote: Le Wed, 29 Mar 2017 14:48:48 +0200 Floris Bos a écrit: The PXE boot firmware implementation of the Raspberry Pi 3 has a bug causing it to fail if it receives replies instantly. As a workaround ensure there is a minimum delay of one second if

Re: [Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

2017-03-29 Thread Albert ARIBAUD
Hi, Le Wed, 29 Mar 2017 14:48:48 +0200 Floris Bos a écrit: > The PXE boot firmware implementation of the Raspberry Pi 3 > has a bug causing it to fail if it receives replies > instantly. > > As a workaround ensure there is a minimum delay of one > second if the client is a Pi. > > On Linux it

[Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

2017-03-29 Thread Floris Bos
The PXE boot firmware implementation of the Raspberry Pi 3 has a bug causing it to fail if it receives replies instantly. As a workaround ensure there is a minimum delay of one second if the client is a Pi. On Linux it looks up the exact receive time of the UDP packet with the SIOCGSTAMP ioctl to