On 14/05/16 19:55, Uwe Schindler wrote:
> Hi Simon,
>
>>> Well, that's the smoking gun. Dnsmasq is doing the right thing, and your
>>> upstream server at 212.202.215.1 is broken. I realise that doesn't solve
>>> the problem, but at least you know where to work now :)
>>>
>>>
>>> (the reason
On 10/05/16 22:03, Jake Gold wrote:
> Hello,
>
> I'm using dnsmasq as a local caching resolver and some of my queries result
> in large answers (~1300 bytes) that are truncated without EDNS.
>
> When I query my local dnsmasq daemon:
>
> dig @localhost
>
> dig sends a query to dnsmasq using
Great, thanks. I've applied your patch and made a further change:
instead of changing the filename behaviour based on CSA, it looks at the
filename provided. If it has a suffix (strictly, if it includes a '.'
character) then the filename is used as-is. Otherwise it as the layer
added as suffix.
On Sat, May 14, 2016 at 08:55:58PM +0200, Uwe Schindler wrote:
> > > Well, that's the smoking gun. Dnsmasq is doing the right thing,
> > > and your upstream server at 212.202.215.1 is broken. I realise
> > > that doesn't solve the problem, but at least you know where to
> > > work now :)
> > >
Hi Simon,
> > Well, that's the smoking gun. Dnsmasq is doing the right thing, and your
> > upstream server at 212.202.215.1 is broken. I realise that doesn't solve
> > the problem, but at least you know where to work now :)
> >
> >
> > (the reason dnsmasq is returning SERVFAIL is that there's a
>
I have included a patch below that makes essentially two modifications to get
PXE working with the UEFI firmware in VMware.
- It only appends the layer number to the file name on BIOS x86.
- It always redirects the client to port 4011. To do that, only the siaddr is
set and neither a boot file
