Hi Doug,
Thanks for your explanation. Simon also emailed me after my post and let
me know where the problem is. The conclusion is this issue seems not be
easily fixed.
So the patch for grub will be applied after grub 2.02. Before that,
could you please show me the configuration file you confir
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
I'm running ubuntu 14, which uses dnsmasq as a local resolver on
127.0.1.1. When I issue a dig query, dig informs me it's using
127.0.1.1 as its resolver:
;; Query time: 3 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Wed Mar 29 09:36:06 CDT 2017
;; MSG SIZE rcvd: 63
However, I would lik
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
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
On Wed, Mar 29, 2017 at 09:43:33AM -0500, Joel Whitehouse wrote:
> I'm running ubuntu 14, which uses dnsmasq as a local resolver on 127.0.1.1.
> When I issue a dig query, dig informs me it's using 127.0.1.1 as its
> resolver:
>
> ;; Query time: 3 msec
> ;; SERVER: 127.0.1.1#53(127.0.1.1)
> ;; WHEN
2017-03-27 17:38 GMT+01:00 Simon Kelley :
> This is a real problem, and I plan to look at it (and all the other
> stuff I've been ignoring.) ASAP. I'm moving house just now, so very
> short of time. If I don't produce something by the end of next week,
> please prod me again.
>
Ok, I will rem
Hi Joel,
Le Wed, 29 Mar 2017 09:43:33 -0500
Joel Whitehouse a écrit:
> I'm running ubuntu 14, which uses dnsmasq as a local resolver on
> 127.0.1.1. When I issue a dig query, dig informs me it's using
> 127.0.1.1 as its resolver:
>
> ;; Query time: 3 msec
> ;; SERVER: 127.0.1.1#53(127.0.1.1)
On Wednesday 29 March 2017 09:43:33 Joel Whitehouse wrote:
> Both the file /var/run/NetworkManager/dnsmasq.conf and the directory
> /etc/NetworkManager/dnsmasq.d/ are empty, so it's likely that dnsmasq is
> receiving its resovlers from Network Manager over the dbus interface.
Right.
> Is there an
On Wed, Mar 29, 2017 at 09:43:33AM -0500, Joel Whitehouse wrote:
> I'm running ubuntu 14, which uses dnsmasq as a local resolver on 127.0.1.1.
> When I issue a dig query, dig informs me it's using 127.0.1.1 as its
> resolver:
>
> ;; Query time: 3 msec
> ;; SERVER: 127.0.1.1#53(127.0.1.1)
> ;; WHEN
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
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
Hi Joel,
2017-03-29 17:43 UTC+03.00, Joel Whitehouse :
>
> Is there any way to get dnsmasq to log when it issues a new query to a
> resolver?
>
You can run tcpdump on upstream interface and port 53.
Risto
___
Dnsmasq-discuss mailing list
Dnsmasq-discu
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
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
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.
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
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
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
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
Hi Steven,
If I find some free time, I might try tracing through the code to figure
out why dnsmasq is throwing out the DHCP packets on port 4011 in the EFI
+ PXE configuration without a proxy. In the meantime, here is the
configuration that works for me with dhcp-boot (assuming my dnsmasq
server'
21 matches
Mail list logo