Attach a tty to the docker container while building the testsuite, as
this is what "should_colorize()" checks for.
Related: b3dca57db9
Change-Id: I6d3c9e1e82b1cf4384b4abd3f1eed072d8fe6fde
Build the ttcn3 testsuites inside docker, so there is no mismatch of
libraries between the host system and the docker container when
attempting to run the testsuite inside docker later (like jenkins does
it).
Change-Id: Ic89e32ed68848bb3b661f77775ed1520c9f44fd9
Allow calling gen_makefile.py with --jobs without any argument, and
behave the same as if --jobs was not passed. This fixes calling
gen_makefile.py initially without --jobs, and then running "make regen"
which will cause gen_makefile.py to get called with --jobs with no
argument.
This way the resulting Makefile is easier to read and understand,
no need to lookup short params in help of gen_makefile.py.
Change-Id: Iba7f148fb1880af2f05cf3ca74cfb0737befeea0
The testsuite is running in bullseye for some time, so build the Osmocom
programs in bullseye as well.
Depends: docker-playground I4cd05ef2c164dfb765ee365ab38b8dfd4f955ac6
Change-Id: Ie5be8dc976fb8ff37b6712f1cba434b2114c4bf8
When enabling BTS1_RUN_IN_OSMO_DEV, the osmo-dev setup is currently
configured to run osmo-bts-virtual without a PCU. Disable GPRS.
Change-Id: I4e55c641b86a9b44bfda263bac1cbd6fad456f8b
Renamming the make_to_src_proj variable to src_proj in commit
93bd52300e leads to the build_to_src variable
being the result of a double call to os.path.relpath(), breaking builds when using
non absolute path for make_dir
Change-Id: I2dfc26da94434558b202475af636ce336349bba9
For some reason, on Arch Linux:
$ file /bin/sh
/bin/sh: symbolic link to bash
$ sh --version
GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)
the '--trx' arguments are getting passed incorrectly:
$ ./fake_trx.py TRX1@127.0.0.1:5700/1
TRX2@127.0.0.1:5700/2
TRX3@127.0.0.1:5700/3
fake_trx: error: unrecognized arguments: TRX1@127.0.0.1:5700/1
TRX2@127.0.0.1:5700/2
TRX3@127.0.0.1:5700/3
Let's send each argument separately.
Change-Id: Ibf28ac013c426baba491af45e2ae46f37685a402
With most recent OsmoBSCNAT patches, the addresses from the connecting
BSCs get used, no need to hardcode them in the config anymore.
Depends: osmo-bsc-nat I1556aa665fbb0a97507f98794e74820731fa6935
Change-Id: I78ef36c72ff9a7b801e922eccc89dc44fbba7f23
osmo-dev's net scripts can be used to run components from RAN too, so
change the title prefix and tmux session name from CN to NET.
Change-Id: I3f46d5a4c7bd20861735c4e01f7cafbc5db08aae
Instead of hardcoding wrappers such as gdb for various commands in
run.sh, put all commands into a config file so the user can add
gdb/valgrind/strace/udtrace/... to the program they are currently
interested in debugging in their own config.
Change-Id: Ifce731ab61d263e9df7a8dc87dd572ca3d30f8dd
Make it consistent with osmo-mgw and osmo-bsc where we also have more
than one config, and the config is not part of the variable.
Change-Id: I83301d75814070c29c6362c59fade9044aa2c0cc
Make it easier for the user to follow a consistent naming scheme for the
log files if they want do do so, by displaying the last log name.
enter name to save log (last: 2022-03-07_04-test-log-name):
Change-Id: I6c5b64e15d9a8dabaf65022d6b82b69523a3ca6b
Start the OsmoBSCNAT's own instance of OsmoMGW. Launch it on a separate
IP, such as the other MGWs, so it's easy to differentiate in wireshark
which traffic relates to which MGW.
Related: https://osmocom.org/projects/osmo-bscnat/wiki/Ladder_diagrams_for_key_procedures
Change-Id: Iaeebb693c81d3aa4b1a46d2543c9872bd49b87c3
Prepare to add another MGW for the BSCNAT. Use only one variable for the
mgw, always append the -c configfile parameter further below in the
script where it gets used.
Change-Id: I6f3fe11109107b35059ebe731e0a74a91a04504c
Fix establishing a call to virtual mobile, which wouldn't work for me if
using anything but FR2 (EFR) as codec.
Change-Id: I6a8706923b651c790798a50aad93492de17dd1a5
Fix displaying unrelated message from iptables by redirecting both
stdout and stderr to /dev/null.
Change-Id: Ibe031725cbb68ec55664dd025b1ffc247db08148
osmo-gbproxy is not part of any of the convenience make targets in
gen_makefile.py (cn, cn-bsc, usrp). When using the typical workflow of
building one of these convenience targets first, then attempting to run
the network, the osmo-gbproxy window just says command not found.
With the default config_2g3g, it is not needed when only using one BTS,
so add a new config variable GBPROXY_RUN_IN_OSMO_DEV=0 and use it in
run.sh.
Change-Id: Ib1349809997ea6062ec3c43df92abab9fbfad1ea
Allow building and installing the "mobile" application from
osmocom-bb.git's src/host/layer23 dir.
Change-Id: Ic75cca703e317eaee593b4d6c78784309c056f17
Neels Hofmeyr
