Change in osmo-gsm-tester[master]: srsenb.conf.tmpl: use gtp_bind_addr also s1c bind

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.

srs_andre gerrit-no-reply at lists.osmocom.org
Wed Jun 10 19:25:43 UTC 2020


srs_andre has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-gsm-tester/+/18583 )

Change subject: srsenb.conf.tmpl: use gtp_bind_addr also s1c bind
......................................................................


Patch Set 3:

> Patch Set 3: Code-Review-2
> 
> > Patch Set 3:
> > 
> > Otherwise if you think there's a bug I can have a look at it.
> 
> I just tested it and it's working fine here:
> 
> """
> enb:
> - label: srsENB-zmq
>   type: srsenb
>   rf_dev_type: zmq
>   rf_dev_args: auto
>   run_node:
>     run_type: ssh
>     run_addr: 10.42.42.117
>     ssh_user: jenkins
>     ssh_addr: 10.42.42.116
> """
> 
> """"
> $ ss -l -n -p | grep enb -B1
> u_dgr  UNCONN     0      0         * 1289                  * 0
> udp    UNCONN     0      0      10.42.42.117:2152                  *:*                   users:(("srsenb",pid=60591,fd=15))
> --
> tcp    LISTEN     0      5      172.16.0.1:5003                  *:*                   users:(("iperf3",pid=60753,fd=3))
> tcp    LISTEN     0      100    10.42.42.117:2000                  *:*                   users:(("srsenb",pid=60591,fd=10))
> """"
> 
> So this patch is indeed not needed and can be abandoned.

To give some context, I've recently changed the resources.conf to run eNB and EPC on the same machine. And to run srsUE on it's own machine. But for the eNB to connect to the EPC I need gtp_bind_addr and s1c_bind_addr to be the same.

See here:

[enb]
# need hex value here for enb_id due to bug: https://github.com/srsLTE/srsLTE/issues/485
enb_id = 0x19b
mcc = 901
mnc = 70
mme_addr = 127.0.1.100
gtp_bind_addr = 127.0.1.1
s1c_bind_addr = 127.0.1.1
n_prb = 100
tm = 1
nof_ports = 1

You are right that if I put just "addr" as s1c_bind_addr and set the run_addr to 127.0.1.1, I can get the above mentioned config and the eNB attached to the EPC. But the same run_addr is also used for the ZMQ radio and this is then not working. Perhaps UHD works.

This is the stdout of srsUE:
Reading configuration file /osmo-gsm-tester-srsue/srsue/srsue.conf...

Built in Release mode using commit 34bc192f7 on branch build_branch.

Opening 1 channels in RF device=zmq with args=tx_port0=tcp://10.12.1.206:2001,tx_port1=tcp://10.12.1.206:2003,tx_port2=tcp://10.12.1.206:2005,tx_port3=tcp://10.12.1.206:2007,rx_port0=tcp://127.0.1.1:2000,rx_port1=tcp://127.0.1.1:2002,rx_port2=tcp://127.0.1.1:2004,rx_port3=tcp://127.0.1.1:2006,rx_freq0=2630e6,tx_freq0=2510e6,id=ue,base_srate=23040000
CHx base_srate=23040000
CHx id=ue
Current sample rate is 1.92 MHz with a base rate of 23.04 MHz (x12 decimation)
CH0 rx_port=tcp://127.0.1.1:2000
CH0 rx_freq=2630e6
CH0 tx_port=tcp://10.12.1.206:2001
CH0 tx_freq=2510e6

You see that ZMQ radio tries to receive from this localhost address, but it should receive from the external IP.

So in summary, this patch is needed and cant be deleted.


-- 
To view, visit https://gerrit.osmocom.org/c/osmo-gsm-tester/+/18583
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings

Gerrit-Project: osmo-gsm-tester
Gerrit-Branch: master
Gerrit-Change-Id: Ibf5b0017c781d17c7f20b859c1cda297e2a9cca2
Gerrit-Change-Number: 18583
Gerrit-PatchSet: 3
Gerrit-Owner: srs_andre <andre at softwareradiosystems.com>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin at sysmocom.de>
Gerrit-Reviewer: srs_andre <andre at softwareradiosystems.com>
Gerrit-Comment-Date: Wed, 10 Jun 2020 19:25:43 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20200610/d8ef87b4/attachment.htm>


More information about the gerrit-log mailing list