XPost: alt.comp.networking.connectivity, alt.comp.microsoft.windows

I need to set up an outgoing port for a client app.
But I don't know if it uses tcp or udp or even ipv4 or ipv6.

Googling, I found these four commands which gave these results shown below. https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/default-dynamic-port-range-tcpip-chang

From those results, how would you advise I set the arbitrary outgoing port?

netsh int ipv4 show dynamicport tcp

Protocol tcp Dynamic Port Range
---------------------------------
Start Port : 1024
Number of Ports : 64511


netsh int ipv4 show dynamicport udp

Protocol udp Dynamic Port Range
---------------------------------
Start Port : 49152
Number of Ports : 16384

netsh int ipv6 show dynamicport tcp

Protocol tcp Dynamic Port Range
---------------------------------
Start Port : 1024
Number of Ports : 64511


netsh int ipv6 show dynamicport udp

Protocol udp Dynamic Port Range
---------------------------------
Start Port : 49152
Number of Ports : 16384

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.networking.connectivity, alt.comp.microsoft.windows

On 2024-01-08 08:26, Charlie wrote:

I need to set up an outgoing port for a client app.
But I don't know if it uses tcp or udp or even ipv4 or ipv6.

It will be tcp on ipv4. Give any random number between 1024 and 64511.

--
Cheers, Carlos.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.networking.connectivity, alt.comp.microsoft.windows

Charlie wrote:

how would you advise I set the arbitrary outgoing port?

Do you have any reason to force known number(s)?

It would be normal for most protocols to default to an ephemeral source
port, i.e. let the operating system decide.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)