Martin-Éric RACINE
Martin-Éric RACINE
That's an odd one. Running separate instances of dhcpcd works fine if it's not in test mode. I wonder what test mode does differently to end up with the same...
[This](https://dev.digicert.com/en/trustcore-sdk/nanossh/faqs.html) page shows some of the supported ciphers. There doesn't seem to be much public documentation about the other supported features.
It might be server-specific.
This only sets IPv4 and IPv6, no specific hostname: https://salsa.debian.org/debian/dhcpcd/-/blob/debian/sid/debian/tests/timesyncd-ntp-servers-from-dhcp?ref_type=heads
Look carefully. This sets up dnsmasq to be able to test that dhcpcd correctly receives IP addresses and NTP server info.
Here's an example of such a timeout: https://ci.debian.net/packages/d/dhcpcd/testing/amd64/57448052/
The server config is generated within this script. Everything else uses dnsmasq defaults. The test randomly fails with a timeout at the exact spot shown there, every now and then....
Both dhcpcd and dnsmasq versions keep on evolving since CI takes place against Testing and Unstable releases. I've asked the dnsmasq maintainers (one of which happens to be upstream) for...
DHCP service is provided by the dnsmasq configured in that CI testing script.
> @perkelix Have you heard anything back from dnsmasq maintainers? Is this something they could recommend be added in a dhcpcd.conf specific to their CI test, since they're asking for...