Thank you Michael, this is true in both configuration modes (Top Down Command Endpoint and Top Down config sync), right?
Connection direction (I’m speaking about tcp) shall not be confused with the configuration mode.
I tested this scenario to make that clear to my self.
My configuration is Top Down Command Endpoint and it works even if the client is blocking any incoming connection.
The main thing that change between the two different configuration modes is “who” triggers the checks: master scheduler in the first case, satellite/client in the second case.
Please, correct me if I’m wrong.
PS: I don’t whish to go further about Top Down config sync in this post, I’ll open another one later on).