2017-11-11 18:36:48 +00:00
|
|
|
== Running OsmoGGSN
|
2017-09-06 10:35:04 +00:00
|
|
|
|
|
|
|
|
The OsmoGGSN executable (`osmo-ggsn`) offers the following command-line
|
|
|
|
|
arguments:
|
|
|
|
|
|
|
|
|
|
=== SYNOPSIS
|
|
|
|
|
|
|
|
|
|
*osmo-ggsn* [-h|-V] [-D] [-c 'CONFIGFILE']
|
|
|
|
|
|
|
|
|
|
=== OPTIONS
|
|
|
|
|
|
|
|
|
|
*-h, --help*::
|
|
|
|
|
Print a short help message about the supported options
|
|
|
|
|
*-V, --version*::
|
|
|
|
|
Print the compile-time version number of the OsmoBTS program
|
|
|
|
|
*-D, --daemonize*::
|
|
|
|
|
Fork the process as a daemon into background.
|
|
|
|
|
*-c, --config-file 'CONFIGFILE'*::
|
|
|
|
|
Specify the file and path name of the configuration file to be
|
|
|
|
|
used. If none is specified, use `osmo-ggsn.cfg` in the current
|
|
|
|
|
working directory.
|
|
|
|
|
|
|
|
|
|
=== Multiple instances
|
|
|
|
|
|
|
|
|
|
Running multiple instances of `osmo-ggsn` is possible if all GGSN instances
|
|
|
|
|
are binding to different local IP addresse and all other interfaces (VTY,
|
|
|
|
|
OML) are separated using the appropriate configuration options. The IP based
|
|
|
|
|
interfaces are binding to local host by default. In order to separate the
|
|
|
|
|
processes, the user has to bind those services to specific but different
|
|
|
|
|
IP addresses.
|
|
|
|
|
|
|
|
|
|
The VTY and the control interface can be bound to IP addresses from the loopback
|
|
|
|
|
address range.
|
|
|
|
|
|
|
|
|
|
.Example: Binding VTY and control interface to a specific ip-address
|
|
|
|
|
----
|
|
|
|
|
line vty
|
|
|
|
|
bind 127.0.0.2
|
|
|
|
|
ctrl
|
|
|
|
|
bind 127.0.0.2
|
|
|
|
|
----
|
2017-11-12 21:50:00 +00:00
|
|
|
|
|
|
|
|
Also make sure to place each instance's GTP bind on a separate IP address (GTP
|
|
|
|
|
uses a port number that is fixed in the GTP specifications, so it will not be
|
|
|
|
|
possible to pick differing ports on the same IP address), like:
|
|
|
|
|
|
|
|
|
|
----
|
|
|
|
|
ggsn ggsn0
|
|
|
|
|
gtp bind-ip 127.0.0.2
|
|
|
|
|
----
|
