You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f46bd9c
Browse filesBrowse the repository at this point in the historyBrowse files
feat: Support configuring local IP address for N9 interface
Until now, eupf only allowed configuring the local IP address for the N3
interface, which actually ended up being used for both N3 and N9 (GTP-U
forwarding towards other uplink UPFs).
However, that limitation poses so problems under some production
scenarios. Some users require running an UPF to forward GTPv1U traffic from
network A to network B and viceversa, where those 2 networks are not reachable
to each other, only through the UPF host.
This happens for instance when cellular operators don't control/own the
entirety of their networks, e.g. a network which runs their NAT under a
satellite link with private addresses (eg VPN) which end up at a single host.
As a result, the UPF requires managing at least 2 separate local IP addresses
for GTP-U traffic: One (usually private) IP address towards the RAN, and one
(usually public, or another private network) IP address towards the Corei.
As a result, when a PFCP client (an SMF, or osmo-hnbgw, or osmo-s1gw to mention
some other examples) tries to setup a session to forward GTPU traffic from
network A (RAN) to network B (Core), will result in eUPF forwarding the GTP-U
packet to the Core but using the RAN configured IP as the GTPU packet local IP
address.
Hence, either local routing will be wrong, or the Core will drop the received
packet, or won't know how to route traffic back to it.
This patch allows eupf to be used co-located with 3G osmo-hnbgw [1] and
4G osmo-s1gw [2] under the mentioned network setups, both supporting PFCP to
manage a UPF to forward data plane also in GTP1U protocol.
[1] https://osmocom.org/projects/osmohnbgw
[2] https://gitea.osmocom.org/erlang/osmo-s1gw
Related: edgecomllc#577
| Interface name<br>`Mandatory`| List of network interfaces handling N3 (GTP) & N6 (SGi) traffic. eUPF attaches XDP hook to every interface in this list. Format: `[ifnameA, ifnameB, ...]`. |`interface_name`|`UPF_INTERFACE_NAME`|`--iface`|`lo`|
10
10
| N3 address <br>`Mandatory`| IPv4 address for N3 interface |`n3_address`|`UPF_N3_ADDRESS`|`--n3addr`|`127.0.0.1`|
11
+
| N9 address <br>`Mandatory`| IPv4 address for N9 interface |`n9_address`|`UPF_N9_ADDRESS`|`--n9addr`|`127.0.0.1`|
11
12
| XDP mode <br>`Optional`| XDP attach mode: <br> ∘ **generic** – Kernel-level implementation. For evaluation purpose. <br> ∘ **native** – Driver-level implenemntaion <br> ∘ **offload** – NIC-level implementation. XDP can be loaded and executed directly on the NIC. <br> Refer to [How XDP Works](https://www.tigera.io/learn/guides/ebpf/ebpf-xdp/#How-XDP-Works)|`xdp_attach_mode`|`UPF_XDP_ATTACH_MODE`|`--attach`|`generic`|
12
13
| API address <br>`Optional`| Local address for serving [REST API](api.md) server |`api_address`|`UPF_API_ADDRESS`|`--aaddr`|`:8080`|
13
14
| PFCP address <br>`Optional`| Local address that PFCP server will listen to |`pfcp_address`|`UPF_PFCP_ADDRESS`|`--paddr`|`:8805`|
@@ -46,6 +47,7 @@ pfcp_address: :8805
46
47
pfcp_node_id: 127.0.0.1
47
48
metrics_address: :9090
48
49
n3_address: 127.0.0.1
50
+
n9_address: 127.0.0.1
49
51
qer_map_size: 1024
50
52
far_map_size: 1024
51
53
pdr_map_size: 1024
@@ -65,6 +67,7 @@ UPF_PFCP_ADDRESS=:8806
65
67
UPF_METRICS_ADDRESS=:9091
66
68
UPF_PFCP_NODE_ID: 10.100.50.241 # address on n4 interface
0 commit comments