This IE will be required by the UE creating a tunnel at the ePDG (EPDG Tunnel Req).
The ePDG will convert the IKEv2 Configuration Attributes into TS 29.060
PCO, and sends them in S2b GTPv2C CreateSessionReq+Resp as PCO.
Change-Id: Id912ead4e1205f84a40af6505a5ddf050d1e086d
The previous PDP-Type IE should have been a PDP-Address from the
start, since having only PDP-Type with no address is only a specific
case (dynamic addressing).
This becomes clear by looking at other similar protocols like:
* MAP: APN-Configuration IE has servedPartyIP-IP{v4,v6}-Address IEs
* Diameter S6b, 3GPP TS 29.272 7.3.35 APN-Configuration contains
Served-Party-IP-Address AVPs
* Diameter SWx, 3GPP TS 29.273 APN-Configuration.
* GTPv1C Ts 29.060 7.7.29 PDP Context containing PDP Address.
Since PDP-Type on its own really makes no sense, being it a special case
of PDP-Address, let's keep the IE by renaming it (keeping old name too
for API backward compat) and extend it to support lengths > 2 bytes.
Old implementation of libosmogsm gsup actually ignored lengths > 2
bytes, so we are safe acting against older implementations here, both
on the sending and receiving side on the wire.
While at it, fix the packetdiag representation, which was already wrong
before:
* Length is 1 byte, not 2 (this happened probably due to confusion
between TS 29.060 EUA and TS 24.008 PDP address, the former TLV being
2 bytes like all of GTP, and TS 24.008 being 1 byte).
* The bytes sharing several fields were swapped.
Change-Id: Ifb4e44b23d19ea049f03a3602c39f2471ff1bff4
Related: OS#6091
Related: libosmocore.git Change-Id I775ff9c3be165d9f30d6ab55d03f99b6104eadd6
Add passage explaining basic visualisation of stat and rate counter items
with Netdata so user can start utilizing them without any special
configuration.
Related: OS#5671
Change-Id: I124503c3707bbe005abbfb4245abe2829c6ff57c
The files gb-nsw-{configuration-timer,configuration,maintenance} were
not actually chapters, but sub-chapters or sub-sub-chapters. This
breaks our general idea that all of those files are top-level chapters.
It also breaks asciidoc validation on Debian 11:
asciidoc: WARNING: gb-ns2-configuration.adoc: line 1: section title out of sequence: expected level 1, got level 2
asciidoc: WARNING: gb-ns2-maintenance.adoc: line 6: section title out of sequence: expected level 2, got level 3
the only place where they were used was the osmo-gbproxy manual, and
there in the exact sequenc in which I now merged them over here.
Change-Id: I3c618e5af61b376435f400ef9c64245cec2f9b73
... this can be included from the various user manuals to insert some
general language about the systemd service units we ship, and a few key
systemd commands to get users started.
Change-Id: I8b04047cbc4097676d69fad794bb3139c05a4a5f
Copied from osmo-bsc.git/doc/manuals/chapters/mgwpool.adoc, version from
Change-Id Id0d292506e8b2a888c8d7a682a38db80e9d0933a
Related: SYS#5987
Change-Id: Ieda0d4bfe6fc90da6e19c791d8ec2da89427ba3b
Both Synch. sequence and Training sequence are basically the same thing,
only the length is different. I guess this is why 3GPP TS 45.002 names
them differently. Let's mention them both to avoid confusion.
Change-Id: I092af5ef6b66f8bdbd46cc3ae0c77fd806f2fe27
This has been the port used historically in most existing deployments,
and it's the one already documented in the osmux section of user
manuals.
Change-Id: I9593e484a0df7cbfc3fa68f071246e3fb714bd4c
How and when socket statistics are generated is not immediately obvious.
Lets add some documentation about it.
Change-Id: Icb06b3934e9ea5f3526263dc8915bc3529a64324
Related: OS#5701