| Neels Hofmeyr | 65d61c3 | 2017-11-11 19:36:48 +0100 | [diff] [blame^] | 1 | == Running OsmoGGSN |
| Harald Welte | 8a1e7b8 | 2017-09-06 12:35:04 +0200 | [diff] [blame] | 2 | |
| 3 | The OsmoGGSN executable (`osmo-ggsn`) offers the following command-line |
| 4 | arguments: |
| 5 | |
| 6 | === SYNOPSIS |
| 7 | |
| 8 | *osmo-ggsn* [-h|-V] [-D] [-c 'CONFIGFILE'] |
| 9 | |
| 10 | === OPTIONS |
| 11 | |
| 12 | *-h, --help*:: |
| 13 | Print a short help message about the supported options |
| 14 | *-V, --version*:: |
| 15 | Print the compile-time version number of the OsmoBTS program |
| 16 | *-D, --daemonize*:: |
| 17 | Fork the process as a daemon into background. |
| 18 | *-c, --config-file 'CONFIGFILE'*:: |
| 19 | Specify the file and path name of the configuration file to be |
| 20 | used. If none is specified, use `osmo-ggsn.cfg` in the current |
| 21 | working directory. |
| 22 | |
| 23 | === Multiple instances |
| 24 | |
| 25 | Running multiple instances of `osmo-ggsn` is possible if all GGSN instances |
| 26 | are binding to different local IP addresse and all other interfaces (VTY, |
| 27 | OML) are separated using the appropriate configuration options. The IP based |
| 28 | interfaces are binding to local host by default. In order to separate the |
| 29 | processes, the user has to bind those services to specific but different |
| 30 | IP addresses. |
| 31 | |
| 32 | The VTY and the control interface can be bound to IP addresses from the loopback |
| 33 | address range. |
| 34 | |
| 35 | .Example: Binding VTY and control interface to a specific ip-address |
| 36 | ---- |
| 37 | line vty |
| 38 | bind 127.0.0.2 |
| 39 | ctrl |
| 40 | bind 127.0.0.2 |
| 41 | ---- |