This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
daniel gerrit-no-reply at lists.osmocom.orgdaniel has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-sgsn/+/14981
Change subject: configuration.adoc: Small fixes
......................................................................
configuration.adoc: Small fixes
Fix some typos, correct data compression command, add example to turn
off compression.
Change-Id: I6beff8c66eacf12f1081d51dd6b124bdd4478558
Related: OS#1720
---
M doc/manuals/chapters/configuration.adoc
1 file changed, 26 insertions(+), 14 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-sgsn refs/changes/81/14981/1
diff --git a/doc/manuals/chapters/configuration.adoc b/doc/manuals/chapters/configuration.adoc
index 2828987..6fe44b3 100644
--- a/doc/manuals/chapters/configuration.adoc
+++ b/doc/manuals/chapters/configuration.adoc
@@ -7,7 +7,7 @@
from the BSC side.
On the other hand, it is because the Gb interface does not need an
-explicit configuration of all each PCU connecting to the SGSN. The
+explicit configuration of each PCU connecting to the SGSN. The
administrator only has to ensure that the NS and BSSGP layer identities
(NSEI, NSVCI, BVCI) are unique for each PCU connecting to the SGSN.
@@ -17,7 +17,7 @@
and the GGSNs. It is implemented via UDP on well-known source and
destination ports.
-When a MS requests establishment of a PDP context, it specifies the APN
+When an MS requests establishment of a PDP context, it specifies the APN
(Access Point Name) to which the context shall be established. This APN
determines which GGSN shall be used, and that in turn determines which
external IP network the MS will be connected to.
@@ -100,7 +100,7 @@
policy that is defined for osmo-nitb!
-.Example: Assign or change authorization policy:
+.Example: Assign or change authorization policy
----
OsmoSGSN> enable
OsmoSGSN# configure terminal
@@ -116,7 +116,7 @@
<2> Saves current changes to cofiguration to make this policy
persistent
-.Example: Access control list:
+.Example: Access control list
----
sgsn
auth-policy acl-only <1>
@@ -153,7 +153,7 @@
GSM/GPRS.
GSUP performs a challenge-response authentication protocol called OAP,
-which uses the standard MILEAGE algorithm for mutual authentication
+which uses the standard MILENAGE algorithm for mutual authentication
between OsmoSGSN and the HLR/HLR-GW.
[[sgsn-ex-gsup]]
@@ -251,9 +251,9 @@
=== User traffic compression
-In order to save optimize GPRS bandwith, OsmoSGSN implements header and data
-compression schemes. The compression will reduce the packet length in order
-to save radio bandwith.
+In order to save GPRS bandwith, OsmoSGSN implements header and data
+compression schemes. The compression will reduce the packet length in
+order to save radio bandwith.
==== Header compression
@@ -278,18 +278,24 @@
compression parameters entirely. The number of slots is the maximum number
of packet headers per subscriber that can be stored in the codebook.
-.Example: Accept compression if requested:
+.Example: Accept compression if requested
----
sgsn
compression rfc1144 passive
----
-.Example: Actively promote compression:
+.Example: Actively promote compression
----
sgsn
compression rfc1144 active slots 8
----
+.Example: Turn off compression again
+----
+sgsn
+ no compression rfc1144
+----
+
NOTE: The usage of TCP/IP options may disturb the RFC1144 header compression
scheme. TCP/IP options may render RFC1144 ineffective if variable data is
encoded into the option section of the TCP/IP packet. (e.g. TCP option 8,
@@ -299,10 +305,10 @@
==== Data compression
Data compression works on the raw packet data, including the header part of the
-packet. If enabled, header compression is applied before first data compression
+packet. If enabled, header compression is applied first before data compression
is applied. OsmoSGSN implements the V.42bis data compression scheme.
-*compression rfc1144 passive*::
+*compression v42bis passive*::
V42bis data compression has to be actively requested by the modem. The network
will not promote compression by itself. This is the recommended mode of
operation.
@@ -316,14 +322,20 @@
the codebook size by the maxium number ('codewords') and size ('strlen') of
entries.
-.Example: Accept compression if requested:
+.Example: Accept compression if requested
----
sgsn
compression v42bis passive
----
-.Example: Actively promote compression:
+.Example: Actively promote compression
----
sgsn
compression v42bis active direction both codewords 512 strlen 20
----
+
+.Example: Turn off compression again
+----
+sgsn
+ no compression v42bis
+----
--
To view, visit https://gerrit.osmocom.org/c/osmo-sgsn/+/14981
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-sgsn
Gerrit-Branch: master
Gerrit-Change-Id: I6beff8c66eacf12f1081d51dd6b124bdd4478558
Gerrit-Change-Number: 14981
Gerrit-PatchSet: 1
Gerrit-Owner: daniel <dwillmann at sysmocom.de>
Gerrit-MessageType: newchange
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20190729/6c5f859e/attachment.htm>