On Thu, 6 Feb 2025, Geert Stappers wrote:
[Problems receiving replies after "0x20 encoding" was implemented]
I did wonder if this might happen.
I just upgraded, [and] saw that warning in the log after about half
an hour [...]
Which version of dnsmasq?
Same question as yes-no-question: Is it with dnsmasq 2.91rc1?
Sorry, I should've included that information, but since the patch that
actually enabled the log message that caused the confusion was less
than a couple of days old, and the traffic on this mailing list is low,
I figured it was evident from context.
The version I upgraded to was built at the tip of the master branch at
the time, commit 5226b712 ("Add --no-0x20-encode config option."),
which is the patch that introduced said log message, so between release
v2.91test10 and v2.91rc1.
Regarding the "potential ways of solving this": Why?
Please elaborate on why there should be put effort in a code change.
Express which potential benefits you see.
Why? To fix a problem with this newly implemented feature, of course,
other than everyone simply deactivating it after seeing a confusing
message in the log, and subsequently flooding the mailing list with
questions about how to deactivate that feature...
What kind of information are you looking for here? I'm just trying to
help out with a bug report that's hopefully detailed enough that the
original author (Simon, in this case) may find it useful and from his
knowledge of the change can spot a potential problem before it's
released as generally available to the world...
For those new to mailinglists:
Abandon the idea that others have read all previous emails.
On the other hand, if people reading a post find that they lack the
context of the thread being discussed, it's super easy to find the
thread in the archive and catch up before responding...
--
Peter Tirsek
_______________________________________________
Dnsmasq-discuss mailing list
[email protected]
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
