* use example new counter names with ':' separator
* mention that 'counter' is obsolete
* mention group name and index
* use bold and monospace fonts to improve visibility
Change-Id: Ia962367bb93cb826002db6c950d23ae2102ac713
Related: OS#2550
osmo-mgw currently uses the VTY port constant of
osmo-bsc_mgcp. We decided to re use the same port
number for osmo-mgw, this is not mentioned in the
manuals yet.
Add the port number of osmo-mgw to the manuals
(common)
Change-Id: I41f7f2a7f850613707eddea610557b688de7a904
We agreed to re-use the port of osmo-bsc-mgcp, so there is
no need for this patch anymore.
This reverts commit ad4a01e2a4.
Change-Id: I8629db5e975cc218c80c747a39c0fdca5f5d6e10
On debian 9, apparently asciidoc-dblatex needs to be installed manually in
order to be able to generate PDFs. Add asciidoc-dblatex dep to INSTALL.txt.
Change-Id: I24b606016e7f1c03bd73a3b0cf4fa3e5b89eb192
Add examples for 'ip addr add' and mention correspondence to config file,
add examples for enabling masquerading and IP forwarding,
place the non-root config in its own section and highlight the diffs.
Add tiny hint at systemd-networkd.
Change-Id: I02bd9cfa35c7f2fb338d5d92c2e968fe80574a78
If LIBOSMO_DIR is not set explicitly than ~/source/gsm/libosmocore is
used which is base for MERGE_DOC which is used by
vty_reference_combine.sh as it is. If the shell used by
vty_reference_combine.sh does not expand ~ than the build will
fail. Let's be nice and use realpath on MERGE_DOC before giving it to
vty_reference_combine.sh to make sure complete path is used.
Change-Id: I2edf64348502cbe498d9fd27a686c712b044c926
It's difficult to understand when it referrs to jenkins job in general
and when it talks about specific jenkins jobs that builds binaries required for
osmo-gsm-tester and the ones which run osmo-gsm-tester.
As a result, it's difficult to understand which sections apply to each
host in case more than one host is used.
Change-Id: I5c882e77b469629028b8d773053783e18f3d1737
This is the one we are usig nowadays in suite.conf, which explicitly
asks to be run with modems supporting sms features.
Change-Id: If5dbc3b4689b282db6fae4668e2838be59e88da8
The osmo-bts-trx tgz doesn't exist anymore and it does not contain
osmo-trx, which comes in its own tgz.
Change-Id: Id803eca3791137b04bc24d195119d5c511fcfc49
* Add sysmocell5000
* Remove 1 modem, showing 2 of them is enough
* Split osmo-bts-trx from osmo-trx node as sysmocell500 doesn't use the
later.
* Update OsmoNITB node to show we also support split openbsc.git
components.
Change-Id: I893beb114d47edd3f67183dd9ea5acc19462496c
See osmo-ci change I2409b2928b4d7ebbd6c005097d4ad7337307dd93 for rationale.
Depends: I2409b2928b4d7ebbd6c005097d4ad7337307dd93
Change-Id: Iaf8338d0d061c70f7ab3737dc425784dc7c170a4
The patch to refactor ctrl commands to osmo-hlr, change
I98ee6a06b3aa6a67adb868e0b63b0e04eb42eb50, was tweaked. Adjust accordingly.
Change-Id: Ie4da6115bb2eb005a9f95bf4de1bfe36468fd607
The initial goal was to make sure we don't have overall FORCE rules causing
unnecessary rebuilds -- annoying while writing documentation. As I looked
through possible dependencies, I finally understood what's going on here.
Remove code dup and nicely sort which belongs where in build/Makefile.*.inc. In
each, describe in a top comment how to use it, and also unify how they are
used:
- Rename Makefile.inc to Makefile.docbook.inc and refactor
- Add Makefile.vty-reference.inc
- Add Makefile.common.inc
Make sure that we accurately pick up all dependencies.
Drop use of the macro called 'command', that silenced the actual command lines
invoked and replaced them with short strings: it obscures what is actually
going on and makes the Makefiles hard to read and understand.
Each manual's makefile is greatly reduced to few definitions and a Makefile
include, e.g. one for asciidoc, one for VTY reference.
Move common/bsc_vty_additions.xml to OsmoBSC/vty/libbsc_vty_additions.xml, link
from OsmoNITB. It applies only to OsmoBSC and OsmoNITB.
Add a script that combines a VTY reference file with *all* additions files
found in a manual's vty/ dir. Call this from Makefile.vty-reference.inc.
Change-Id: I9758e04162a480e28c7dc83475b514cf7fd25ec0
Change node IDs to use the names derived from the node prompt,
in the process fix the node references to not place the vty_additions in the
wrong places.
Related: I8fa555570268b231c5e01727c661da92fad265de (libosmocore)
Change-Id: I48edb65be94be56c4b57293d8edc1b30271acc12
- Mention that the CONFIG node is used to parse config files.
- Mention that it is not well defined whether CONFIG node items have immediate
effect.
- Add a 'telnet' here and there to clarify.
Change-Id: I882346c69f12c67d0e41d563c99d4de4efd8b8f6
* Some people want to manually create/configure their tun devices,
show them how to do this using ip with the correct parameters
* Let's not call the network device 'ggsn' but rather 'apn0', as
the device has a 1:1 correspondence to the APN, not to the GGSN.
Change-Id: I2fef818bfcb8cb521397136539f492922d5f6def
Pau Espin
Max
Philipp Maier
Harald Welte