Bug 13986 - KRESD - Does not honor UDP/TCP settings
Summary: KRESD - Does not honor UDP/TCP settings
Status: MODIFIED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: - Unknown - - Unknown -
Assignee: Michael Tremer
QA Contact:
URL:
Keywords:
Depends on:
Blocks: KRESD
  Show dependency tree / graph
 
Reported: 2026-05-23 13:34 UTC by Stefan Schantl
Modified: 2026-05-26 19:37 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Schantl 2026-05-23 13:34:04 UTC 
As described in the summary, kresd does not honor if the forwarding should be done by UDP or TCP
Comment 1 Michael Tremer 2026-05-26 15:32:26 UTC 
UDP & TLS work, but TCP doesn't, indeed.

However there is no trivial way to turn this on, so I will solve this later.
Comment 2 Michael Tremer 2026-05-26 16:29:53 UTC 
Could you please verify whether this works?

> https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=9a45c759d6367516bfb0c9a5516a50fc7920c5e5
Comment 3 Stefan Schantl 2026-05-26 19:30:45 UTC 
Hello Michael,

I've applied your changes and can confirm that the configured protocol now is used properly.
Comment 4 Stefan Schantl 2026-05-26 19:37:49 UTC 
After some more testing, I had to admit, when selecting TLS as proto no connection to an upstream server could be created, because the resolver is forced to use TCP.

So the patch slightly needs to be adjusted to only set the TCP flag when TCP should is configured.