Hi guys,
I configured something on my laptop and tried few requests with my
raspberry. I think I have found weird state. It checks only matching
dhcp-range context, not pxe-service, when adding PXE stuff to requests.
So I made it require also pxe-service. It seems it might do what you
have request
On 30/09/2021 22:16, Petr Menšík wrote:
> Hi,
>
> I am submitting patch enabling IDN usage for input parameters. We have
> support for IDN, but because locale is not properly initialized, no
> parameters using special characters are accepted.
>
> Patch #1 adds domain_len to more places, quite sim
If you're going to use more natural internal representations of DNS
datastructures and then convert them to line format at the end, there
are much more deserving cases than this. I think I must have been
certifiably mad to do DNSSEC validation on a line-format representation
of a DNS packet. It end
Ouch, that ancount increase seems quite weird. What if we still used
break to avoid printing all parts never added to message?
It seems to me multibyte variables in dns_header should be converted
just once after receiving and converted back to network order just once
before sending. Constant conve
> I.e. if pxe-service is not matched due to tags,
> to behave in the same way like if it wasn't there at all?
What would that involve?
Not answering in port 4011 for that client?
`ss -nap | grep 4011` shows that when "pxe-service" lines exist,
dnsmasq listens in that port, otherwise it doesn't.
Hi all,
Alkis has highlighted the main question once again. Thanks Alkis.
Now trying to provide the answers to Petr's queries -
It seems to me the answer lies only on its boot rom firmware. I just expect
> both used matching configuration and dnsmasq version.
>
This is the case with an Intel NU
