Osmocom Open Build Service

osmo-upf.spec Changed

osmo-upf_0.1.1.94.60cb.202404152026.dsc -> osmo-upf_0.1.1.95.7780.202404162026.dsc Changed

@@ -2,7 +2,7 @@
 Source: osmo-upf
 Binary: osmo-upf, osmo-upf-dbg, osmo-upf-doc
 Architecture: any all
-Version: 0.1.1.94.60cb.202404152026
+Version: 0.1.1.95.7780.202404162026
 Maintainer: Osmocom team <openbsc@lists.osmocom.org>
 Homepage: https://projects.osmocom.org/projects/osmo-upf
 Standards-Version: 3.9.8
@@ -14,8 +14,8 @@
  osmo-upf-dbg deb debug extra arch=any
  osmo-upf-doc deb doc optional arch=all
 Checksums-Sha1:
- 73957df0a1f8d80f39e491582508102d9a9258bc 72780 osmo-upf_0.1.1.94.60cb.202404152026.tar.xz
+ 30b82ed49d4a3a19a2ee95532ab99993b3b8671f 73180 osmo-upf_0.1.1.95.7780.202404162026.tar.xz
 Checksums-Sha256:
- 8aa8491b3dc604967f9e3cf98752a439c5740d33b3d2c63243b4dfe14cf4f74e 72780 osmo-upf_0.1.1.94.60cb.202404152026.tar.xz
+ 699bb4931776d90de2c5ecc3e8e5b9cd527343c78cbdc4875f6c86c4d9e5b7ea 73180 osmo-upf_0.1.1.95.7780.202404162026.tar.xz
 Files:
- 04792936df43a86c6634819dfb3fd875 72780 osmo-upf_0.1.1.94.60cb.202404152026.tar.xz
+ d4689211519daa61068bb5d1efe47795 73180 osmo-upf_0.1.1.95.7780.202404162026.tar.xz

osmo-upf_0.1.1.94.60cb.202404152026.tar.xz/.tarball-version -> osmo-upf_0.1.1.95.7780.202404162026.tar.xz/.tarball-version Changed

osmo-upf_0.1.1.94.60cb.202404152026.tar.xz/contrib/osmo-upf.spec.in -> osmo-upf_0.1.1.95.7780.202404162026.tar.xz/contrib/osmo-upf.spec.in Changed

osmo-upf_0.1.1.94.60cb.202404152026.tar.xz/debian/changelog -> osmo-upf_0.1.1.95.7780.202404162026.tar.xz/debian/changelog Changed

osmo-upf_0.1.1.94.60cb.202404152026.tar.xz/debian/control -> osmo-upf_0.1.1.95.7780.202404162026.tar.xz/debian/control Changed

osmo-upf_0.1.1.94.60cb.202404152026.tar.xz/doc/manuals/chapters/running.adoc -> osmo-upf_0.1.1.95.7780.202404162026.tar.xz/doc/manuals/chapters/running.adoc Changed

@@ -226,3 +226,44 @@
 
 When running more than one osmo-upf process on a system, pick distinct table
 names to avoid name collisions in the nftables rulesets.
+
+=== IP Forwarding
+
+In order to allow forwarding GTP payloads, the Linux operating system must
+be configured to allow IP forwarding.
+
+Note that there are many distribution-specific ways to configure this, and there
+might be higher-level firewall rule management software available like `ufw`.
+You should configure firewall rules matching your distribution and setup.
+
+To allow IP forwarding from and to all interfaces globally in a reboot-safe way,
+you may put a line like this in /etc/sysctl.conf:
+
+----
+net.ipv4.ip_forward=1
+----
+
+To do the same in an ad-hoc way that is not reboot safe but takes effect
+immediately:
+
+----
+sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"
+----
+
+It is also possible to instruct the firewall to allow IP forwarding for specific
+network devices only. For example, on a Debian based system, place an nft
+ruleset like this in `/etc/nftables.conf`:
+
+----
+define gtp_netdevs = { eth0, eth23 };
+
+table inet filter {
+      chain forward {
+              type filter hook forward priority filter; policy drop;
+              iifname $gtp_netdevs oifname $gtp_netdevs udp dport 2152 accept
+      }
+}
+----
+
+This ruleset allows IP forwarding, but limited to the GTP-U port 2152,
+and to two specific network devices eth0 and eth23.

Changes of Revision 611