Feature #2244
closed
osmo-gsm-tester: osmo-bts-trx: handle local TRX address as resource
Added by neels almost 7 years ago.
Updated over 6 years ago.
Description
osmo-bts-trx starts on 127.0.0.1 -- that should be handled as a resource like the nitb_iface.
So far that's only for osmo-bts-trx and will become an issue only for multiple osmo-bts-trx on the same tester unit.
Could be explicitly a trx_iface, or more generally, maybe a loopback_iface.
with https://gerrit.osmocom.org/2712 we have the ip_address resource. To have loopback addresses, we would add a property like 'type: loopback'; alternatively we can just run osmo-bts-trx on a public interface like the rest of the programs.
- Status changed from New to In Progress
- Assignee changed from 55360 to pespin
Assigning to me as I started looking into this issue for sysmocell5000 support.
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
I'm using a static IP for each BTS for now. This should be enough and helps us in various scenarios. For instance, Sysmocell5000 has TRX always enabled which means it's sending UDP packets to the osmo-bts-trx address. As that IP is static and it's used only when Sysmocell5000 resources it's used, it doesn't interfer with other osmo-bts-trx processes because they use a different IP.
- Status changed from Resolved to Closed
Also available in: Atom
PDF
