October 2024 - gerrit-log - lists.osmocom.org

[L] Change in osmo-hlr[master]: gsupclient: Introduce gsup_client_mux

by laforge

Attention is currently required from: lynxis lazus. laforge has posted comments on this change by lynxis lazus. ( https://gerrit.osmocom.org/c/osmo-hlr/+/38112?usp=email ) Change subject: gsupclient: Introduce gsup_client_mux ...................................................................... Patch Set 5: (1 comment) File src/gsupclient/gsup_client_mux.c: https://gerrit.osmocom.org/c/osmo-hlr/+/38112/comment/ae62d4c2_c12418cb?usp… : PS1, Line 8: * SPDX-License-Identifier: AGPL-3.0+ > yeah, GPLv2 is fine with me! GPLv2-or-later is what I meant. -- To view, visit https://gerrit.osmocom.org/c/osmo-hlr/+/38112?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: osmo-hlr Gerrit-Branch: master Gerrit-Change-Id: I916c1bb6cfc48f92fc5db2b5c914eb1b4e25fa7f Gerrit-Change-Number: 38112 Gerrit-PatchSet: 5 Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Comment-Date: Tue, 22 Oct 2024 16:15:34 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: laforge <laforge(a)osmocom.org> Comment-In-Reply-To: lynxis lazus <lynxis(a)fe80.eu>

8 months, 1 week

1
0
0 0

[M] Change in osmo-ggsn[master]: doc: Document MTU features in User Manual and example config files

by pespin

Attention is currently required from: pespin. Hello Jenkins Builder, I'd like you to reexamine a change. Please visit https://gerrit.osmocom.org/c/osmo-ggsn/+/38500?usp=email to look at the new patch set (#4). The following approvals got outdated and were removed: Verified-1 by Jenkins Builder Change subject: doc: Document MTU features in User Manual and example config files ...................................................................... doc: Document MTU features in User Manual and example config files Related: OS#6298 Related: SYS#7122 Change-Id: Ib6e974b38107fe48072380f768e1881f0fc95e80 --- M doc/examples/osmo-ggsn-kernel-gtp.cfg M doc/examples/osmo-ggsn.cfg M doc/manuals/chapters/configuration.adoc M doc/manuals/chapters/running.adoc 4 files changed, 147 insertions(+), 12 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-ggsn refs/changes/00/38500/4 -- To view, visit https://gerrit.osmocom.org/c/osmo-ggsn/+/38500?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newpatchset Gerrit-Project: osmo-ggsn Gerrit-Branch: master Gerrit-Change-Id: Ib6e974b38107fe48072380f768e1881f0fc95e80 Gerrit-Change-Number: 38500 Gerrit-PatchSet: 4 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Attention: pespin <pespin(a)sysmocom.de>

8 months, 1 week

1
0
0 0

[M] Change in osmo-ggsn[master]: doc: Document MTU features in User Manual and example config files

by pespin

Hello Jenkins Builder, I'd like you to reexamine a change. Please visit https://gerrit.osmocom.org/c/osmo-ggsn/+/38500?usp=email to look at the new patch set (#3). Change subject: doc: Document MTU features in User Manual and example config files ...................................................................... doc: Document MTU features in User Manual and example config files Related: OS#6298 Related: SYS#7122 Change-Id: Ib6e974b38107fe48072380f768e1881f0fc95e80 --- M doc/examples/osmo-ggsn-kernel-gtp.cfg M doc/examples/osmo-ggsn.cfg M doc/manuals/chapters/configuration.adoc M doc/manuals/chapters/running.adoc 4 files changed, 147 insertions(+), 12 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-ggsn refs/changes/00/38500/3 -- To view, visit https://gerrit.osmocom.org/c/osmo-ggsn/+/38500?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newpatchset Gerrit-Project: osmo-ggsn Gerrit-Branch: master Gerrit-Change-Id: Ib6e974b38107fe48072380f768e1881f0fc95e80 Gerrit-Change-Number: 38500 Gerrit-PatchSet: 3 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder

8 months, 1 week

1
0
0 0

[M] Change in osmo-ggsn[master]: WIP: doc: Document MTU features in User Manual and example config files

by pespin

pespin has posted comments on this change by pespin. ( https://gerrit.osmocom.org/c/osmo-ggsn/+/38500?usp=email ) Change subject: WIP: doc: Document MTU features in User Manual and example config files ...................................................................... Patch Set 2: This change is ready for review. -- To view, visit https://gerrit.osmocom.org/c/osmo-ggsn/+/38500?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: osmo-ggsn Gerrit-Branch: master Gerrit-Change-Id: Ib6e974b38107fe48072380f768e1881f0fc95e80 Gerrit-Change-Number: 38500 Gerrit-PatchSet: 2 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Comment-Date: Tue, 22 Oct 2024 16:07:37 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: No

8 months, 1 week

1
0
0 0

[M] Change in osmo-ggsn[master]: WIP: doc: Document MTU considerations

by pespin

pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ggsn/+/38500?usp=email ) Change subject: WIP: doc: Document MTU considerations ...................................................................... WIP: doc: Document MTU considerations Related: OS#6298 Related: SYS#7122 Change-Id: Ib6e974b38107fe48072380f768e1881f0fc95e80 --- M doc/examples/osmo-ggsn-kernel-gtp.cfg M doc/examples/osmo-ggsn.cfg M doc/manuals/chapters/configuration.adoc M doc/manuals/chapters/running.adoc 4 files changed, 89 insertions(+), 12 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-ggsn refs/changes/00/38500/1 diff --git a/doc/examples/osmo-ggsn-kernel-gtp.cfg b/doc/examples/osmo-ggsn-kernel-gtp.cfg index bed52b9..69ab51b 100644 --- a/doc/examples/osmo-ggsn-kernel-gtp.cfg +++ b/doc/examples/osmo-ggsn-kernel-gtp.cfg @@ -44,6 +44,7 @@ gtpu-mode kernel-gtp tun-device tun4 type-support v4 + mtu default apply ip prefix dynamic 172.16.222.0/24 ip dns 0 8.8.8.8 ip dns 1 8.8.4.4 diff --git a/doc/examples/osmo-ggsn.cfg b/doc/examples/osmo-ggsn.cfg index 53cebc1..52b1034 100644 --- a/doc/examples/osmo-ggsn.cfg +++ b/doc/examples/osmo-ggsn.cfg @@ -44,6 +44,7 @@ gtpu-mode tun tun-device tun4 type-support v4 + mtu default apply ip prefix dynamic 172.16.222.0/24 ip dns 0 8.8.8.8 ip dns 1 8.8.4.4 @@ -53,6 +54,7 @@ gtpu-mode tun tun-device tun6 type-support v6 + mtu default apply ipv6 prefix dynamic 2001:780:44:2000:0:0:0:0/56 ipv6 dns 0 2001:4860:4860::8888 ipv6 dns 1 2001:4860:4860::8844 @@ -62,6 +64,7 @@ gtpu-mode tun tun-device tun46 type-support v4v6 + mtu default apply ip prefix dynamic 172.16.46.0/24 ip dns 0 8.8.8.8 ip dns 1 8.8.4.4 diff --git a/doc/manuals/chapters/configuration.adoc b/doc/manuals/chapters/configuration.adoc index f0889d3..2dfe0d3 100644 --- a/doc/manuals/chapters/configuration.adoc +++ b/doc/manuals/chapters/configuration.adoc @@ -1,3 +1,4 @@ +[[osmoggsn_configuring]] == Configuring OsmoGGSN All configuration of OsmoGGSN is performed using the VTY. For more @@ -22,6 +23,7 @@ gtpu-mode tun tun-device tun4 type-support v4 + mtu default apply ip prefix dynamic 176.16.222.0/24 ip dns 0 192.168.100.1 ip dns 1 8.8.8.8 @@ -162,18 +164,20 @@ ---- OsmoGGSN(config-ggsn-apn)# gtpu-mode tun <1> OsmoGGSN(config-ggsn-apn)# type-support v4 <2> -OsmoGGSN(config-ggsn-apn)# ip prefix dynamic 176.16.222.0/24 <3> -OsmoGGSN(config-ggsn-apn)# ip dns 0 192.168.100.1 <4> -OsmoGGSN(config-ggsn-apn)# ip dns 1 8.8.8.8 <5> -OsmoGGSN(config-ggsn-apn)# ip ifconfig 176.16.222.0/24 <6> +OsmoGGSN(config-ggsn-apn)# mtu 1420 apply <3> +OsmoGGSN(config-ggsn-apn)# ip prefix dynamic 176.16.222.0/24 <4> +OsmoGGSN(config-ggsn-apn)# ip dns 0 192.168.100.1 <5> +OsmoGGSN(config-ggsn-apn)# ip dns 1 8.8.8.8 <6> +OsmoGGSN(config-ggsn-apn)# ip ifconfig 176.16.222.0/24 <7> ---- <1> Use the userspace GTP-U handling using a TUN device <2> Support (only) IPv4 Addresses -<3> Specify the pool of dynamic IPv4 addresses to be allocated to PDP +<2> Specify MTU to announce to MS. Apply the MTU on the tunnel interface. +<4> Specify the pool of dynamic IPv4 addresses to be allocated to PDP contexts -<4> Specify the primary DNS server to be provided using IPCP/PCO -<5> Specify the secondary DNS server to be provided using IPCP/PCO -<6> Request OsmoGGSN to configure the `tun4` device network/netmask +<5> Specify the primary DNS server to be provided using IPCP/PCO +<6> Specify the secondary DNS server to be provided using IPCP/PCO +<7> Request OsmoGGSN to configure the `tun4` device network/netmask NOTE:: If you use the optional `ip ifconfig` command to set the network device address/mask, OsmoGGSN must run with root or `CAP_NET_ADMIN` @@ -271,6 +275,7 @@ ---- # ip addr add 192.168.7.1/24 dev apn0 +# ip link set mtu 1420 dev apn0 # ip link set apn0 up ---- @@ -298,13 +303,18 @@ [Match] Name=apn0 <1> +[Link] +MTUBytes=1420 <2> + [Network] -Address=192.168.7.1/24 <2> -IPMasquerade=yes <3> +Address=192.168.7.1/24 <3> +IPMasquerade=yes <4> ---- <1> The network device name, which must match the one in the apn0.netdev unit file above -<2> The local IP address configured on the device -<3> Requesting systemd to configure IP masquerading for this interface. Depending on your needs, +<2> Requesting systemd to set the MTU for this interface. The MTU of the tun + interface should be lower than regular, since it must accommodate the extra IP/UDP/GTPv1U headers. +<3> The local IP address configured on the device +<4> Requesting systemd to configure IP masquerading for this interface. Depending on your needs, You may not want this if you have proper end-to-end routing set up, and want to have transparent inbound IP access to your GPRS-attached devices. @@ -326,6 +336,7 @@ gtpu-mode tun tun-device apn0 type-support v4 + mtu 1420 ip prefix dynamic 192.168.7.0/24 ip dns 0 192.168.100.1 ip dns 1 8.8.8.8 diff --git a/doc/manuals/chapters/running.adoc b/doc/manuals/chapters/running.adoc index 04c5b06..2371ec3 100644 --- a/doc/manuals/chapters/running.adoc +++ b/doc/manuals/chapters/running.adoc @@ -52,6 +52,68 @@ your distribution's documentation -- e.g. look for @net.ipv4.ip_forward=1@ in @/etc/sysctl.d/@, and https://wiki.debian.org/iptables for masquerading. +=== MTU considerations + +When running osmo-ggsn, the user must take network Maximum Transmission Unit +(MTU) into consideration, and configure it based on network specific setup. + +In osmo-ggsn, the MTU can be configured per APN through the VTY, see <<osmoggsn_configuring>>. +If told so by the config, osmo-ggsn will apply the MTU on the APN network interface. + +==== MTU announced to MS + +The configured MTU is also announced to the MS through: + +* IPv4 APN: GTPv1C Create PDP Context Response, PCO IE "IPv4 Link MTU", 3GPP TS 24.008 Table 10.5.154. +* IPv6 APN: ICMPv6 Routing Advertisement during IPv6 SLAAC procedure, RFC 4861. + +==== Figuring out maximum MTU value + +There is no golden MTU value, since it really depends on the local (and remote) networks where traffic is routed. +The idea is finding out a value which: +* Is as big as possible, to avoid need to split big chunks of data into lots of small packets, hence affecting performance due to processing overhead: extra headers being trnasmitted, plus processing of extra packets. +* Is small enough so that it can be transported over the lower layers of the links involving the communication, avoiding IP fragmentation, which again hurts performance. + +OsmoGGSN, by default, announces an MTU of `1420` bytes. This is calculated on the assumption that traffic is transported over Ethernet, which has a usual MTU of 1500 bytes. On top of that, it must account for the IP/UDP/GTPv1U headers used to encapsulate the traffic sent towards the RAN. Hence the following bytes are subtracted from the Ethernet base MTU of 1500 bytes: +* IP: IPv4 headers can take up to 60 bytes (due to IPv4 options). IPv6 headers can take up to 40 bytes (assuming no extension headers for IPv6 in general, since they are uncommon). Hence, the 60 bytes of IPv4 are picked since that's greater than the IPv4. +* UDP: The UDP header takes 8 bytes. +* GTPv1U: The GTPv1U header takes 12 bytes, assuming here no extensions headers are used (OsmoGGSN doesn't use them). +Hence, `TUNNEL_MTU = ETH_MTU - IP_HDR - UDP_HDR - GTPv1U_HDR = 1500 - 60 - 8 - 12 = 1420`. + +Under certain networks, the base MTU may already be smaller than Ethernet's MTU (1500 bytes), due to, for instance, existence of some sort of extra tunneling protocol in the path, such as a VPN, ipsec, extra VLAN levels, etc. Under this scenario, the user must take care of figuring out the new base MTU value to use for the calculations presented above. This can be accomplished by packet inspection (eg. `wireshark`) or with tools such as `ping`, running it with a certain packet size and the IPv4 DF bit set, and see up to which packet size the networks is able to forward the message. For instance: + +.Example: Test if packets of 1420 bytes can reach peer host 176.16.222.4 +---- +ping -M probe 176.16.222.4 -s 1420 +---- + +==== TCP MSS Clamping + +Usually endpoints use Path MTU Discovery (PMTUD) to determine the maximum MTU to reach the peer. +However, this technique may sometimes not be successful for all users of OsmOGGSN: +* MS may not support requesting and/or configuring the MTU OsmoGGSN announced. +* MS may not support PMTUD on its network stack, or may not have it enabled or may be buggy. +* Network may be misconfigured or some middlebox may be buggy (eg. not forwarding ICMP `Packet Too Big` packets). + +Furthermore, PMTUD takes time to figure out the maximum MTU to use, since it relies on sending data and checking if it got lost, and adapting to the fact, reducing efficiency (throughput) of connections or even stalling them completely when big packets are generated. + +TODO: +- Explain what's TCP MSS +- Explain what's TCP MSS clamping and why is it useful in this case (we are reducing MTU from usual routes due to encapsulating traffic) +- Show an example with iptables on how to configure TCP MSS. + +==== Further Reading + +For more related specs, check the following specs: + +* 3GPP TS 29.061 section 11.2.1.5 +* 3GPP TS 290.060 section 13.2 IP Fragmentation +* 3GPP TS 25.414 section 6.1.3.3 +* 3GPP TS 23.060 section 9.3, Annex C +* 3GPP TS 24.008 (PCO IPv4 MTU) +* RFC 4861 (IPv6 Router Advertisement) + + === Multiple instances Running multiple instances of `osmo-ggsn` is possible if all GGSN instances -- To view, visit https://gerrit.osmocom.org/c/osmo-ggsn/+/38500?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: osmo-ggsn Gerrit-Branch: master Gerrit-Change-Id: Ib6e974b38107fe48072380f768e1881f0fc95e80 Gerrit-Change-Number: 38500 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de>

8 months, 1 week

1
0
0 0

[M] Change in osmo-sgsn[master]: GMM: split parsing of a RA Update Request in a separate file

by lynxis lazus

Attention is currently required from: daniel, laforge, pespin. lynxis lazus has posted comments on this change by lynxis lazus. ( https://gerrit.osmocom.org/c/osmo-sgsn/+/37869?usp=email ) Change subject: GMM: split parsing of a RA Update Request in a separate file ...................................................................... Patch Set 23: (2 comments) Commit Message: https://gerrit.osmocom.org/c/osmo-sgsn/+/37869/comment/9e7dba91_0b5ac8ca?us… : PS21, Line 9: gprs_gmm.c is huge. Further split the general validation : and parsing of the message into an own function. : > does it make sense to do this split for a single message? If we think the code should be split, sho […] Yes, it would be great to do it for multiple messages. But it is also moving parts out of it, validating it, add a new message struct. File src/sgsn/gprs_gmm_util.c: https://gerrit.osmocom.org/c/osmo-sgsn/+/37869/comment/8b435c60_0b9ff769?us… : PS15, Line 54: * \param[in] msg l3 pointers must point to gmm. Return 0 on success or GMM cause > this documentation looks broken. […] Done -- To view, visit https://gerrit.osmocom.org/c/osmo-sgsn/+/37869?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: osmo-sgsn Gerrit-Branch: master Gerrit-Change-Id: I413da1b6b4b7c0c4781393acd8564661bc74ce2d Gerrit-Change-Number: 37869 Gerrit-PatchSet: 23 Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: daniel <dwillmann(a)sysmocom.de> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-CC: laforge <laforge(a)osmocom.org> Gerrit-Attention: laforge <laforge(a)osmocom.org> Gerrit-Attention: pespin <pespin(a)sysmocom.de> Gerrit-Attention: daniel <dwillmann(a)sysmocom.de> Gerrit-Comment-Date: Tue, 22 Oct 2024 12:07:24 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: laforge <laforge(a)osmocom.org> Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>

8 months, 1 week

1
0
0 0

[XS] Change in osmo-ggsn[master]: doc: Reorder some chapters

by pespin

pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ggsn/+/38499?usp=email ) Change subject: doc: Reorder some chapters ...................................................................... doc: Reorder some chapters Move general/generic osmocom chapters (logging, vty) further to the end, so that the osmo-ggsn specific chapters stay together and don't get lost in tons of generic content. Change-Id: I6441944cc365bae40ab0f3cc4f1ecd1ac790c5c5 --- M doc/manuals/osmoggsn-usermanual.adoc 1 file changed, 2 insertions(+), 3 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-ggsn refs/changes/99/38499/1 diff --git a/doc/manuals/osmoggsn-usermanual.adoc b/doc/manuals/osmoggsn-usermanual.adoc index 30cd542..cc4a9c7 100644 --- a/doc/manuals/osmoggsn-usermanual.adoc +++ b/doc/manuals/osmoggsn-usermanual.adoc @@ -11,13 +11,12 @@ //include::{srcdir}/chapters/control.adoc[] +include::{srcdir}/chapters/configuration.adoc[] + include::./common/chapters/vty.adoc[] include::./common/chapters/logging.adoc[] - -include::{srcdir}/chapters/configuration.adoc[] - include::./common/chapters/control_if.adoc[] include::./common/chapters/vty_cpu_sched.adoc[] -- To view, visit https://gerrit.osmocom.org/c/osmo-ggsn/+/38499?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: osmo-ggsn Gerrit-Branch: master Gerrit-Change-Id: I6441944cc365bae40ab0f3cc4f1ecd1ac790c5c5 Gerrit-Change-Number: 38499 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de>

8 months, 1 week

1
0
0 0

[XS] Change in osmo-ggsn[master]: doc: Fix typo: wrong interface named

by pespin

pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ggsn/+/38498?usp=email ) Change subject: doc: Fix typo: wrong interface named ...................................................................... doc: Fix typo: wrong interface named Change-Id: Ib7ef619c74bf0e6453f0d5ba509e7727bf90f838 --- M doc/manuals/chapters/running.adoc 1 file changed, 1 insertion(+), 1 deletion(-) git pull ssh://gerrit.osmocom.org:29418/osmo-ggsn refs/changes/98/38498/1 diff --git a/doc/manuals/chapters/running.adoc b/doc/manuals/chapters/running.adoc index 41de78f..04c5b06 100644 --- a/doc/manuals/chapters/running.adoc +++ b/doc/manuals/chapters/running.adoc @@ -56,7 +56,7 @@ Running multiple instances of `osmo-ggsn` is possible if all GGSN instances are binding to different local IP addresses and all other interfaces (VTY, -OML) are separated using the appropriate configuration options. The IP based +CTRL) 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. -- To view, visit https://gerrit.osmocom.org/c/osmo-ggsn/+/38498?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: osmo-ggsn Gerrit-Branch: master Gerrit-Change-Id: Ib7ef619c74bf0e6453f0d5ba509e7727bf90f838 Gerrit-Change-Number: 38498 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de>

8 months, 1 week

1
0
0 0

[XS] Change in osmo-ggsn[master]: doc: Fix typo in user manual

by pespin

pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ggsn/+/38496?usp=email ) Change subject: doc: Fix typo in user manual ...................................................................... doc: Fix typo in user manual Change-Id: I9b0024cfdb748febcecf01a097125103bc0f39c1 --- M doc/manuals/chapters/running.adoc 1 file changed, 1 insertion(+), 1 deletion(-) git pull ssh://gerrit.osmocom.org:29418/osmo-ggsn refs/changes/96/38496/1 diff --git a/doc/manuals/chapters/running.adoc b/doc/manuals/chapters/running.adoc index c07e309..41de78f 100644 --- a/doc/manuals/chapters/running.adoc +++ b/doc/manuals/chapters/running.adoc @@ -55,7 +55,7 @@ === 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, +are binding to different local IP addresses 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 -- To view, visit https://gerrit.osmocom.org/c/osmo-ggsn/+/38496?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: osmo-ggsn Gerrit-Branch: master Gerrit-Change-Id: I9b0024cfdb748febcecf01a097125103bc0f39c1 Gerrit-Change-Number: 38496 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de>

8 months, 1 week

1
0
0 0

[XS] Change in osmo-ggsn[master]: doc: Remove reference to non londer existing osmo-ggsn.init

by pespin

pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ggsn/+/38497?usp=email ) Change subject: doc: Remove reference to non londer existing osmo-ggsn.init ...................................................................... doc: Remove reference to non londer existing osmo-ggsn.init The init file was removed at some point in the past. Nowadays only a systemd service is provided. Change-Id: I47f889a223bfaf7bd4848898211a3cc62df5e08c --- M doc/manuals/chapters/overview.adoc 1 file changed, 1 insertion(+), 6 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-ggsn refs/changes/97/38497/1 diff --git a/doc/manuals/chapters/overview.adoc b/doc/manuals/chapters/overview.adoc index 632db5e..c0eed79 100644 --- a/doc/manuals/chapters/overview.adoc +++ b/doc/manuals/chapters/overview.adoc @@ -9,7 +9,7 @@ core network of 2G and 3G cellular networks. The GGSN function is the tunnel endpoint on the core network side, -from where the external (IP) packet data network +from where the external (IP) packet data network === Software Components @@ -43,11 +43,6 @@ In *contrib/osmo-ggsn.service* you can find a sample service file for OsmoGGSN which can be used with systemd. -==== init script - -In *contrib/osmo-ggsn.init* you can find a sample init script to be used -on systems with classic init process. - === Limitations OsmoGGSN supports both GTP0 (GSM 09.60) and GTP1 (3GPP 29.060). In the -- To view, visit https://gerrit.osmocom.org/c/osmo-ggsn/+/38497?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: osmo-ggsn Gerrit-Branch: master Gerrit-Change-Id: I47f889a223bfaf7bd4848898211a3cc62df5e08c Gerrit-Change-Number: 38497 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de>

8 months, 1 week

1
0
0 0

2025

2024

2023

2022

gerrit-log October 2024