libosmo-pfcp - Osmocom PFCP library

Age	Commit message (Collapse)	Author	Files	Lines
2023-04-15	pfcp_msg: refactor LOG_PFCP_MSG	Neels Janosch Hofmeyr	1	-20/+5
	It was requested during code review to make this a function and not a macro. One effective change: no longer log "NULL{fi=NULL}" when no m->ctx.session_fi or .peer_fi are set. Change-Id: Ic84090c9b1a34185577cfb2ea1efa9c07542df34
2022-07-23	clarify osmo_pfcp_msg alloc API	Neels Hofmeyr	1	-4/+4
	Looking at the osmo_pfcp_msg_alloc API with a bit of distance now, I found that: - it is confusing to have a single function for req and resp. A resp may pass remote_addr as NULL, and a req may pass in_reply_to as NULL. Make this much more obvious with separate req/resp functions. - the osmo_pfcp_endpoint_tx() implicitly puts the local Node ID into sent PFCP messages, so the local_node_id arg for msg alloc is redundant. Drop that. Refactor without backwards compat, because we have not yet officially released this API. This requires a fixup patch to osmo-upf.git (and affects unmerged patches to osmo-hnbgw.git). Related: SYS#5599 Related: I73e6da3b80f05e9408c81f41ac05d6578b8e31cf (osmo-upf) Change-Id: I0d71134e42932cc72992eba73a15e82bc7cd11bd
2022-06-16	add pfcp_endpoint	Neels Hofmeyr	1	-0/+3
	Related: SYS#5599 Change-Id: Ic8d42e201b63064a71b40ca45a5a40e29941e8ac
2022-06-16	libosmo-pfcp: implement PFCP header and msg handling	Neels Hofmeyr	1	-0/+197
	Related: SYS#5599 Change-Id: I3f85ea052a6b7c064244a8093777e53a47c8c61e