Lennart, I suppose that what you wrote concerns UDP port on the server providing system that systemd-timesyncd uses to synchronize time? This is not a problem, from the point of view of the system where systemd-timesyncd is running privileged remote port is not a problem, I have problems if source UDP port (so one created by systemd-timesyncd) is problematic, but I understand that systemd-timesyncd always uses unprivileged source port?
Thanks for an answer, JD On Tue, Mar 31, 2020 at 4:57 PM Lennart Poettering <lenn...@poettering.net> wrote: > > On Mi, 11.03.20 17:34, Jędrzej Dudkiewicz (jedrzej.dudkiew...@gmail.com) > wrote: > > > Hi, > > > > I have quite a few devices running Linux in client's network - so I > > have no control over it. It seems that all privileged UDP ports are > > blocked I have to use unprivileged port. I'd like to use > > systemd-timesyncd to synchronize time, thought I can't find a way to > > force it to use unprivileged port. Is there any way to do it? > > There's not, currently, the port nr is hardcoded. It might be OK to > make the port nr configurable though, via an env var. You could then > set the env var via a drop-in for systemd-timesyncd.service that uses > Environment=. Patch should be simple, look for resolve_getaddrinfo() > in timesyncd-manager.c. Consider prepping a patch and posting as > github PR, we'll the review/merge it. > > Lennart > > -- > Lennart Poettering, Berlin -- Jędrzej Dudkiewicz I really hate this damn machine, I wish that they would sell it. It never does just what I want, but only what I tell it. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
