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
It doesn't seem necessary to do the "sleep .2" for tmux, so only do it
when starting with regular terminals.
Change-Id: I70931922aac56dad3d1e4dec67ca2b78d7cca7ff
Don't attempt to configure phy0 / osmotrx ip. This only works with
osmo-bts-trx, not with osmo-bts-virtual which we'll run in osmo-dev.
Besides that, 127.0.0.1 seems to be the default anyway.
Change-Id: I20984d00623f31ce9c58a1dc91bcf53d4aec78b2
Prepare support for a second BSC, in order to test OsmoBSCNAT.
* Rename BSC_* variables to BSC0_*
* Rename MGW4BSC_* variables to MGW4BSC0_*
* Rename osmo-bsc.cfg to osmo-bsc-0.cfg
* Rename osmo-mgw-for-bsc.cfg to osmo-mgw-for-bsc-0.cfg
Change-Id: Iaba2e3143b7bb6451a0104042e69d47ee5f48d3c
Don't ask the user to copy config_2g3g and manually keep it in sync with
config_2g3g with each change anymore. Instead, let the user config be a
diff on top of config_2g3g.
This is in preparation to adding new variables for use with OsmoBSCNAT.
Change-Id: I5870d39aee8be84c2024f8a2a71ee4a734a4fc7c
Put each line in a separate, aligned print statement and use f-strings
(Python 3.6 feature, even debian oldstable has > 3.6 by now).
This is in preparation to add a new line about the original config in
the next patch.
Change-Id: Iad39a7889c107ceb8c16325bb545cb426eb9b6e2
This was related to attempting to fix the infinite "q Enter to close"
msgs bug, which has been properly fixed in
Iebb799493f76fd57f24b15c998ded2bd8e284e6b.
Remove fg to get rid of this error:
zsh:fg:1: no job control in this shell.
Change-Id: Iba7a1adbc4f48b0477a53590ffec8af518fdf467
It's hard to distinguish multiple wireshark windows with trace.pcap
files, as only the file name and not the path is shown in the title.
Make it easier to distinguish them by adding the log name to the file
name.
Change-Id: I7007d7c1e74aef46f1942f4f6f675adebb890955
Fix the logic that is supposed to display a "q Enter to close" message
once and wait for user input, in case one of the Osmocom programs
crashed.
Explicitly read from /dev/tty, as it may not be connected as default
stdin anymore at this point. This happens when using the new code paths
with tmux as terminal, but also happened before recent refactorings for
me with all terminals.
Related: https://media.ccc.de/v/osmodevcall-20211210-osmith-osmo-dev-ttcn3#t=801
Change-Id: Iebb799493f76fd57f24b15c998ded2bd8e284e6b
Create one tmux session, with each Osmocom program in one window, if
tmux is chosen as "terminal". This allows using osmo-dev's run.sh over
ssh without X forwarding. Also the existing supported terminals
automatically scroll to the bottom as soon as there is new output,
making it hard to read logs.
Change-Id: Iaef08fb3cb3c6f58cd8490a631e177a03af9c974
Instead of passing a whole script to the terminal via command-line
argument, write it to a file. This is in preparation to use the same
script with tmux, see next patch.
Change-Id: I15760d706b20628421c10a16514120f442d5477f
Replace the previous approach of only storing the PIDs of the spawned
terminals, and then attempting to kill all other processes (the ones
running inside the spawned terminals and tcpdump) with "killall".
Instead, store PIDs of all spawned programs:
* Terminals
* Osmocom programs (new)
* Tcpdump (new)
Kill old processes at the start of run.sh as well, so even if run.sh was
killed before it could clean up, the Osmocom programs don't fail to
start anymore (as it was the case before).
Change-Id: I379ef71de2f1ab0ac4a28064e5cf9e275c4c61e9
Prepare to add "tmux" as new terminal. As discussed in code review, we
decided to drop support for auto-detection.
Change-Id: I0afb6b0242c399334a2c37f18a5d26d5beeabedc
Add MSC and BSC point-codes, as it is currently needed in the initial
message forwarding implementation.
Related: SYS#5560
Related: osmo-bsc-nat I4af398bb433341a98f818822e6c3af28b6d9dacd
Change-Id: Ia396cc677ceffa3fa86da5460f6c890b5f714059
Make STP_CN_IP and STP_RAN_IP configurable. If they are not set to the
same IP, run a second OsmoSTP and OsmoBSCNAT to connect both OsmoSTP.
Related: OS#2545
Change-Id: I8bfbd00bfeeebc6e1b87a8cd6333212db4380653
Put the terminal PIDs into a variable instead of running kill %1 %2 etc.
This makes it easier to conditionally spawn some of the programs.
Change-Id: Iaf6c175de2edf720009af13eace2b0ef83b0735b
Don't print find errors if not all dirs were cloned. Found this also
while running osmo-dev on a fresh install.
Change-Id: I7955fedc96484e5703073b63906a03477452db6e
In preparation for the OsmoDevCall#19 talk, I'm installing this on a
fresh system and made some adjustments to README so it works without
complaining about missing dependencies.
Related: https://osmocom.org/news/155
Change-Id: I7522d8c9346e9823f3977b9190210eb5d5bcfe2d
Neels Hofmeyr