Re: TL source port

> On 22 Sep 2025, at 22:28, Volker Kuhlmann <[email protected]> wrote:
> 
> TCP port 8369 does not show up as being for anything specific (ports
> 1024 and above are unregulated so to speak). E.g.
> https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers
> 
> This makes me think your workplace blocks every outgoing port, then
> unblocks those that are needed. It might slow down a cyber attack by a
> smidgeon.
> 
> Your only chance is to approach the sysadmins with a reason (i.e. use
> case) and beg. Your chances depend on exactly what policy they have.

Thanks for the clarification. This seems a likely explanation. I didn't get any from the sysadmins, other than outgoing port 8369 must be blocked.

As for begging, this is exactly what I did. We'll see how it goes. I'm not holding my breath though. These are the same people that block rsync outside the local domain, forcing me to wait until I'm home to retrieve the TL sources when needed.

Bruno