osmocom-bb/src/target/trx_toolkit
Vadim Yanitskiy 2605d96720 trx_toolkit: fix: do not use 'is' / 'is not' with string and numerical literals
Since version 3.8, Python warnins us that using the "is" and "is not"
operators with string and numerical literals is a bad idea. Let's
avoid this and use the classical '==' and '!=' operators instead.

Change-Id: Iaed86d630ac1e0b9b4f72bbf3c788e325783456d
Bug description: https://bugs.python.org/issue34850
2019-11-17 17:46:48 +07:00
..
.gitignore Rename 'fake_trx' to 'trx_toolkit' 2018-03-13 02:10:02 +07:00
README trx_toolkit/README: update fake_trx.py description 2019-01-14 23:52:31 +00:00
app_common.py target/*.py: shebang: use /usr/bin/env python 2019-07-16 22:46:12 +00:00
burst_fwd.py target/*.py: shebang: use /usr/bin/env python 2019-07-16 22:46:12 +00:00
burst_gen.py trx_toolkit/burst_gen.py: basic TRXD header version 1 support 2019-07-24 05:44:19 +07:00
burst_send.py trx_toolkit: fix compatibility with Python 3: 'is' vs '==' 2019-07-24 05:44:19 +07:00
clck_gen.py trx_toolkit: fix compatibility with Python 3: 'is' vs '==' 2019-07-24 05:44:19 +07:00
ctrl_cmd.py trx_toolkit: fix compatibility with Python 3: 'is' vs '==' 2019-07-24 05:44:19 +07:00
ctrl_if.py target/*.py: shebang: use /usr/bin/env python 2019-07-16 22:46:12 +00:00
ctrl_if_trx.py target/*.py: shebang: use /usr/bin/env python 2019-07-16 22:46:12 +00:00
data_dump.py Fix common misspellings and typos 2019-10-17 08:07:39 +00:00
data_if.py trx_toolkit/data_msg.py: raise exceptions from validate() methods 2019-08-27 20:30:23 +02:00
data_msg.py trx_toolkit/data_msg.py: enrich some ValueError messages 2019-08-29 18:02:04 +02:00
fake_pm.py target/*.py: shebang: use /usr/bin/env python 2019-07-16 22:46:12 +00:00
fake_trx.py trx_toolkit: fix: do not use 'is' / 'is not' with string and numerical literals 2019-11-17 17:46:48 +07:00
gsm_shared.py target/*.py: shebang: use /usr/bin/env python 2019-07-16 22:46:12 +00:00
rand_burst_gen.py trx_toolkit/rand_burst_gen.py: fix compatibility with Python 3 2019-07-24 05:44:19 +07:00
transceiver.py target/*.py: shebang: use /usr/bin/env python 2019-07-16 22:46:12 +00:00
trx_list.py target/*.py: shebang: use /usr/bin/env python 2019-07-16 22:46:12 +00:00
trx_sniff.py trx_toolkit: fix: do not use 'is' / 'is not' with string and numerical literals 2019-11-17 17:46:48 +07:00
udp_link.py target/*.py: shebang: use /usr/bin/env python 2019-07-16 22:46:12 +00:00

README

TRX toolkit is a set of tools intended for hacking and debugging
a TRX interface between both transceiver and L1 software, and
emulating a virtual Um-interface between OsmocomBB and OsmoBTS.

Brief description of available applications:

  - fake_trx.py - main application, that allows to connect both
    OsmocomBB and OsmoBTS without actual RF hardware. It's also
    possible to emulate more than two transceivers, so multiple
    MS and/or BTS instances can be connected.

  - clck_gen.py - a peripheral tool aimed to emulate TDMA frame
    clock generator. Could be used for testing and clock
    synchronization of multiple applications. It should be noted,
    that one relays on generic system timer (via Python), so
    a random clock jitter takes place.

  - ctrl_cmd.py - another peripheral tool, which could be used
    for sending CTRL commands directly in manual mode, and also
    for application fuzzing.

  - burst_gen.py - a tool for sending GSM bursts either to L1
    (OsmoBTS or OsmocomBB) or to TRX (OsmoTRX and GR-GSM TRX).
    Currently it is only possible to generate random bursts of
    different types: NB, FB, SB, AB.

  - burst_send.py - a tool for sending existing bursts from a
    capture file either to L1 (OsmoBTS or OsmocomBB) or to
    TRX (e.g. OsmoTRX or GR-GSM TRX).

  - trx_sniff.py - Scapy-based TRX protocol sniffer. Allows one
    to observe a single connection between TRX and L1, and vice
    versa. Also provides some capabilities for filtering bursts
    by direction, frame and timeslot numbers, and for recording
    captured messages to a binary file.

Please note that TRX toolkit is not using libosmocore's CTRL
interface, so 'CTRL' in scope of this code base actually means
control interface of TRX or control protocol. In order to avoid
possible confusion, we use 'TRXC' and 'TRXD' in logging.