diff options
| author | Neels Janosch Hofmeyr <nhofmeyr@sysmocom.de> | 2022-11-26 02:58:08 +0100 |
|---|---|---|
| committer | Neels Janosch Hofmeyr <nhofmeyr@sysmocom.de> | 2022-11-26 03:05:42 +0100 |
| commit | abecf789261e53bdb99a0ab275008e4d8f65cb6d (patch) | |
| tree | 84de8f2fd125fdffe9ef558b86c90ba9aec1ca77 /contrib | |
| parent | c41bfcbbf0a364eaefe1782a60e41562edd0e3aa (diff) | |
osmo_pfcp_ip_addrs_set(): do not set port number
struct osmo_pfcp_ip_addrs uses an osmo_sockaddr for storing IP
addresses. Even though osmo_sockaddr contains a port number, no port
number gets encoded in PFCP messages. Hence always set the port to 0.
I noticed that when osmo_pfcp_ip_addrs_set() is invoked with an
osmo_sockaddr that incidentally has a port number set, subsequent
logging of e.g. a PFCP F-TEID shows a port number, which is confusing.
Change-Id: Ib29a123c06d459c99d7c1c0b9a7694fb78cd9fd8
Diffstat (limited to 'contrib')
0 files changed, 0 insertions, 0 deletions