OK - I provided a patch for this change ([PATCH] Remove ttl==255
restriction for queries).
Additionally I sent two other patches:
1. [PATCH] umdns: Remove incorrect comma in hhtp service json config
2. [PATCH] umdns: Add debug output for service_timeout
Philipp
On 09/25/2017 06:45 PM, John
in that case its a bug and the code should be changed to only have that
restriction on queries
John
On 25/09/17 17:21, Philipp Meier wrote:
My question is about query (not response). LEDE is ignoring query when
TTL != 255.
Philipp
On 09/25/2017 05:16 PM, John Crispin wrote:
Hi,
My question is about query (not response). LEDE is ignoring query when
TTL != 255.
Philipp
On 09/25/2017 05:16 PM, John Crispin wrote:
Hi,
rfc6762 has the following ...
11. Source Address Check
All Multicast DNS responses (including responses sent via unicast)
SHOULD be sent with
Hi,
rfc6762 has the following ...
11. Source Address Check
All Multicast DNS responses (including responses sent via unicast)
SHOULD be sent with IP TTL set to 255. This is recommended to
provide backwards-compatibility with older Multicast DNS queriers
(implementing a draft
Hi,
When using umdns I was wondering why my mDNS query did not get any answer.
I found the following reason:
My mDNS query has TTL field set to 1. But LEDE umdns package expects a
TTL value of 255 (see interface.c function read_socket4).
According
