Attention is currently required from: laforge, fixeria, daniel, lynxis lazus.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/32169 )
Change subject: tests: rename and extend gprs_{bvci_default->params}.vty ......................................................................
Patch Set 1:
(1 comment)
Commit Message:
https://gerrit.osmocom.org/c/osmo-bsc/+/32169/comment/a25ae91a_fa0913ad PS1, Line 18: The PCU obviously cannot bind to port 0, and will keep re-starting.
I have had such a configuration and it definitely failed to bind (or at least failed to establish th […]
The question here is more: does it make sense from network architecture point of view that PCU binds to a randomly available port for Gb?
AFAIU it makes no sense, since it needs to bind to a specific port also known by the SGSN so that it knows where to send packets to. Or is the SGSN available to learn dynamically of the PCU by listening() on its port? Maybe something @lynxis or @daniel will be able to answer better.
If it makes no sense that the PCU can bidn to a random port, then sure, let's disallow passing bind port 0. But let's then explain correctly the rationale behind it, which is wrong in current version of this patch.