forked from acouzens/open5gs
93110d011e
As mentioned in the sgwu.yaml configuration file, it is possible to configure multiple addresses with different source_interface values for the gtpu interface.
Following the this section, I defined two addresses, one with source_interface set to 0 and another with source_interface set to 1. My expectation was to see different addresses for the two PDRs in the Session Establishment Response message during session establishment. However, both addresses were the same, and it was the address I had set for source_interface = 0.
When I looked into the code, I found the reason for the issue. In the lib/pfcp/context.c file, on line 1185, the function that determines the address is called as follows:
...
} else {
ogs_gtpu_resource_t *resource = NULL;
resource = ogs_pfcp_find_gtpu_resource(
&ogs_gtp_self()->gtpu_resource_list,
pdr->dnn, OGS_PFCP_INTERFACE_ACCESS);
if (resource) {
...
In the last parameter of this function, a constant value, OGS_PFCP_INTERFACE_ACCESS, is used. This causes every PDR with any source_interface to be considered as "access," and the value 0 is used for its interface.
I replaced the value with pdr->src_if, and the bug was resolved.
|
||
|---|---|---|
| .. | ||
| app.c | ||
| context.c | ||
| context.h | ||
| event.c | ||
| event.h | ||
| gtp-path.c | ||
| gtp-path.h | ||
| init.c | ||
| meson.build | ||
| pfcp-path.c | ||
| pfcp-path.h | ||
| pfcp-sm.c | ||
| s5c-handler.c | ||
| s5c-handler.h | ||
| s11-build.c | ||
| s11-build.h | ||
| s11-handler.c | ||
| s11-handler.h | ||
| sgwc-sm.c | ||
| sgwc-sm.h | ||
| sxa-build.c | ||
| sxa-build.h | ||
| sxa-handler.c | ||
| sxa-handler.h | ||
| timer.c | ||
| timer.h | ||