Bug #6384
closedosmo-epdg: SMF IP address should be obtained from AAA-Server
100%
Description
So far we are obtaining the SMF IP address in osmo-epdg from the config file:
config/sys.config
38: {gtpc_remote_ip, "127.0.0.1"},
src/osmo_epdg_sup.erl
13:-define(ENV_DEFAULT_GTPC_REMOTE_IP, "127.0.0.1").
24: GtpcRemoteIp = application:get_env(?ENV_APP_NAME, gtpc_remote_ip, ?ENV_DEFAULT_GTPC_REMOTE_IP),
%% ePDG processes:
GtpcServer = {epdg_gtpc_s2b, {epdg_gtpc_s2b,start_link, [GtpcLocalIp, GtpcLocalPort, GtpcRemoteIp, GtpcRemotePort, GtpuLocalIp, []]},
permanent,
5000,
worker,
[epdg_gtpc_s2b]},
We should instead obtain it from the AAA-Server.
It still needs to be found out whether AAA-Server in turn also obtains it from HSS.
Files
Updated by pespin about 2 months ago
Yes, AAA-Server gets the PGW address (and updates it) from the HSS.
Updated by pespin about 2 months ago
- File tunnel_setup.pcapng tunnel_setup.pcapng added
HSS can optionally provide the PDN-GW address in HSS->AAA Swx message SAA (REGISTRATION), in AVP:
SAA
Non-3GPP-User-Data (3GPP TS 29.273 8.2.3.1, mandatory in SAA type=REGISTRATION)
APN-Configuration (3GPP TS 29.272 7.3.35, optional, multiple)
PDN-GW-Allocation-Type (3GPP TS 29.272 7.3.44, optional default=static)
MIP6-Agent-Info (3GPP TS 29.272 7.3.45, optional)
So AAA should check if Non-3GPP-User-Data->APN-Configuration[Service-Selection=$APN_NAME]->MIP6-Agent-Info is available and use that, otherwise select the PGW from its config afaiu.
open5gs-hssd in epdg.osmocom.org doesn't seem to be adding MIP6-Agent-Info so far, I attach a pcap file.
Updated by pespin about 2 months ago
- Status changed from New to Feedback
- % Done changed from 0 to 90
https://gerrit.osmocom.org/c/erlang/osmo-epdg/+/36158 Forward PGW Address HSS->AAA->ePDG
Updated by pespin about 2 months ago
- Status changed from Feedback to Resolved
- % Done changed from 90 to 100
Patches merged, closing.
