Project

General

Profile

Actions

Feature #5682

open

cfg: separate PFCP Node ID from PFCP local address

Added by neels about 1 year ago.

Status:
New
Priority:
Low
Assignee:
-
Target version:
-
Start date:
09/17/2022
Due date:
% Done:

0%

Spec Reference:

Description

The PFCP protocol features a Node ID, which can be used to uniquely identify
PFCP endpoints across different interfaces. The Node ID can be a fully-qualified
domain name (FQDN), or IP address. Currently, osmo-upf has no support for
using an FQDN as Node ID, and requires the 'local-addr' to be configured, which
it uses as Node ID.

Instead, we should separate the concepts of which local interface to use from the Node ID sent in-band.
pfcp_endpoint.h already has separate fields in osmo_pfcp_endpoint_cfg for local_addr and local_node_id, but osmo-upf only features a pfcp / local-addr config option.


Related issues

Related to OsmoHNBGW - Feature #5647: cfg: separate PFCP Node ID from PFCP local addressNew08/17/2022

Actions
Actions #1

Updated by neels about 1 year ago

  • Related to Feature #5647: cfg: separate PFCP Node ID from PFCP local address added
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)