Hi Neels,
If you'd like to run alongside Osmocom (without cfg), then you probably want to stay clear of 4000 to 4500.
OK, this part is a given...
So you can just pick 5000 or whatever.
The table in the wiki page already lists 5000 as A/IP for osmo-bsc_nat. I am now thinking about 5100 to 5199 range.
If we have agreement on it, we can also designate a port number or range on above wiki page as "used by project XYZ" and then hopefully future Osmocom programs will see that and choose a different port.
Would it be acceptable to add a note to the Port_Numbers wiki page along the lines of:
"Port numbers 5100 through 5199 are reserved for deployment-specific programs that may be developed locally by administrators of individual Osmocom-based cellular networks, as may be needed for unique custom requirements of individual deployments."
?
It does not make sense to officially designate a given port range as non-Osmocom, because each program or program-family should make their own port choices. They should not *all* use the same port range.
Please note the "deployment-specific" language I propose above. If I develop custom add-ons to Osmocom CNI that are highly specific to USA telecom environment and to the problem of interconnecting an Osmocom network with this national telephone+SMS environment, and someone else develops their own custom add-ons that are specific to local needs in a very different world region with different needs, those two different program-families will never run together. Hence my idea of reserving a range of port numbers for "deployment-specific" applications, whatever they may be in a given deployment.
M~