Change in ...osmo-sgsn[master]: osmo-sgsn: Fix outdated information in usermanual
gerrit-no-reply at lists.osmocom.org
Fri Jul 26 12:11:05 UTC 2019
laforge has submitted this change and it was merged. ( https://gerrit.osmocom.org/c/osmo-sgsn/+/14963 )
Change subject: osmo-sgsn: Fix outdated information in usermanual
osmo-sgsn: Fix outdated information in usermanual
Quite a few features that are listed as not-implemented in the overview
section are actually implemented now.
2 files changed, 9 insertions(+), 18 deletions(-)
Jenkins Builder: Verified
laforge: Looks good to me, approved
diff --git a/doc/manuals/chapters/overview.adoc b/doc/manuals/chapters/overview.adoc
index abc7496..e2c0107 100644
@@ -74,14 +74,13 @@
non-acknowledged mode, as this is the most common use case in real-world
-Furthermore, it does not support IP header nor payload compression at
-this point. Addition of those features is subject to customer demand or
+It does support both TCP/IP header compression according to RFC1144 and
+payload compression according to V.42bis
-The LLC implementation does support LLC encryption. However, as no HLR
-access is implemented yet, there is no way to enable/configure
-per-subscriber specific keys.
+The LLC implementation does support LLC encryption with ciphers GEA3 and GEA4.
+For encryption to work the auth policy needs to be set to remote and the SGSN
+connected to an HLR containing the subscriber data including key material.
+Other auth policys will not work with encryption.
==== Session Management Implementation
@@ -93,11 +92,8 @@
Multiple PDP contexts can be attached by a single MS.
-Currently, all PDP contexts are routed to the same GGSN, irrespective of
-the APN used/configured in the MS. This is sufficient (and actually
-desirable) for small autonomous networks, but of course not suitable for
-real networks in roaming scenarios. Please contact sysmocom in case you
-require additional features such as DNS-based APN resolving.
+Multiple GGSNs can be configured and routing to a GGSN can be configured based
+on APN. Dynamic lookup of GGSNs though DNS-based APN resolving is also possible.
@@ -109,10 +105,5 @@
Known Limitations include:
-* No LLC encryption support
-* No interface to the OsmoNITB HLR
* No paging coordination between SGSN and MSC
* No SMS over Ps support
-* No IuPS interface for 3G (in progress)
-* No IP header compression
-* No payload compression
diff --git a/doc/manuals/chapters/running.adoc b/doc/manuals/chapters/running.adoc
index d758b28..63c2b27 100644
@@ -14,7 +14,7 @@
Print a short help message about the supported options
- Print the compile-time version number of the OsmoBTS program
+ Print the compile-time version number of the OsmoSGSN program
*-d, --debug 'DBGMASK','DBGLEVELS'*::
Set the log subsystems and levels for logging to stderr. This
has mostly been superseded by VTY-based logging configuration,
To view, visit https://gerrit.osmocom.org/c/osmo-sgsn/+/14963
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Owner: daniel <dwillmann at sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: daniel <dwillmann at sysmocom.de>
Gerrit-Reviewer: laforge <laforge at gnumonks.org>
Gerrit-Reviewer: pespin <pespin at sysmocom.de>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gerrit-log