neels has submitted this change. ( https://gerrit.osmocom.org/c/osmo-upf/+/30834 ) Change subject: manual: tweak 'running' for new netinst feature ...................................................................... manual: tweak 'running' for new netinst feature Related: SYS#6192 Change-Id: Iaa7af53aae72099283bb29ef0fc0eba03ae2f27d --- M doc/manuals/chapters/running.adoc 1 file changed, 15 insertions(+), 8 deletions(-) Approvals: Jenkins Builder: Verified pespin: Looks good to me, but someone else must approve laforge: Looks good to me, approved diff --git a/doc/manuals/chapters/running.adoc b/doc/manuals/chapters/running.adoc index ab7ab18..0f56521 100644 --- a/doc/manuals/chapters/running.adoc +++ b/doc/manuals/chapters/running.adoc @@ -117,11 +117,12 @@ range that matches the UE IP addresses that are configured in GTP-C / PFCP. The following configuration placed in `osmo-upf.cfg` creates a GTP device called -`apn23` on startup, which is also destroyed on program exit: +`apn23` on startup of osmo-upf, which is destroyed on program exit. It listens +for GTP on local IP address `1.2.3.4`: ---- tunend - dev create apn23 + dev create apn23 1.2.3.4 ---- TODO:: `osmo-upf` is not yet able to configure this network device's IP address @@ -132,7 +133,7 @@ ---- tunend - dev use apn42 + dev use apn42 2.3.4.5 ---- GTP kernel devices can be managed manually using the `gtp-link` program @@ -146,11 +147,17 @@ $ osmo-upf -c osmo-upf.cfg ---- -NOTE:: It is possible to configure multiple GTP devices in `osmo-upf.cfg`, but -`osmo-upf` currently _only uses the first GTP device_ found in the -configuration. In the future, different devices may be used based on the Network -Instance IE passed in the PFCP Session messages (PDR/FAR). Until then, it makes -little sense to configure more than one GTP device. +It is possible to configure multiple GTP devices in `osmo-upf.cfg`. Depending on +the Network Instance name, osmo-upf creates tunnel endpoints on the GTP device +with a matching IP address: + +- The Network Instance IE in the PDR on the Access side determines the local IP + address to use, see <<netinst>>. +- This local IP address in turn determines the GTP device to use. + +It is possible for a GTP device to listen on ANY -- just omit the IP address in +the `dev` config. In this case, all Network Instance names will be served by +this GTP device. When using ANY, there should be exactly one GTP dev configured. [[nftables]] ===== Configure Linux netfilter for `tunmap` 2 is the latest approved patch-set. No files were changed between the latest approved patch-set and the submitted one. -- To view, visit https://gerrit.osmocom.org/c/osmo-upf/+/30834 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-upf Gerrit-Branch: master Gerrit-Change-Id: Iaa7af53aae72099283bb29ef0fc0eba03ae2f27d Gerrit-Change-Number: 30834 Gerrit-PatchSet: 3 Gerrit-Owner: neels &lt;nhofmeyr(a)sysmocom.de&gt; Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge &lt;laforge(a)osmocom.org&gt; Gerrit-Reviewer: neels &lt;nhofmeyr(a)sysmocom.de&gt; Gerrit-Reviewer: pespin &lt;pespin(a)sysmocom.de&gt; Gerrit-MessageType: merged