Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/01/2020 17.56, James Knott wrote: | On 2020-01-12 11:50 AM, Carlos E. R. wrote: |> In that sense it is bidirectional if each one set the others as |> peers, and each one defines himself as server. O perhaps server |> only for a limited set of IPs. | | That's why I said a peer has to be configured at both ends. With | normal client/server, only the client is configured to use the | server. There is no matching configuration on the server. Also, | IIRC, the client also becomes a server. It least that's the way | it used to be in openSUSE. I haven't checked recently, but I did | that when I was using it as my firewall.
I think the client needs to be told to listen to become a server; otherwise requests would be banging the firewall. I'm unsure if that is the keyword "restrict".
An ntp daemon will always listen, "restrict" is for limiting access, yes. -- Per Jessen, Zürich (2.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org