Replies: 2 comments 4 replies
-
Hello, I do not complete understand your question, but to usage the non-3GPP access all you need is found in usage section. If in your scenario the Y1 and Y2 interfaces are correctly established, you can use the following options for run the non-3GPP access: Options: I did not run the non-3GPP access on a different hardware than the 5G core network, but i believe that once that Y1 and Y2 interfaces are correctly established, you need only create the ipsec link required between UE and the N3IWF, and then execute the UE and trigger initial registration procedure. I hope you can solve your problem. Regards, |
Beta Was this translation helpful? Give feedback.
-
Hi @dayal007, |
Beta Was this translation helpful? Give feedback.
-
Hello,
What configuration changes, interfaces updates and firewall rules need to be done if we want to run the UE in a separate machine? Because that will be the most realistic scenario then running UE and core in the same machine.
Example
|UE - 192.168.1.50| -> |my5g-core - 192.168.1.55|
As of now, this expects everything need to be run in the same machine.
Is my understanding right?
On my5gcore machine:
sudo ip link add name ipsec0 type vti local 192.168.1.55 remote 0.0.0.0 key 5
sudo ip addr add 10.0.0.1/24 dev ipsec0
sudo ip link set ipsec0 up
On UE Machine:
sudo ip link add ipsec0 type vti local 192.168.1.50 remote 192.168.1.55 key 5
sudo ip link set ipsec0 up
And then "trigger_initial_registration.sh"
ue_addr=${ue_addr:-"192.168.1.50"}
ue_port=${ue_port:-"10000"}
scheme=${scheme:-"https"}
auth_method=${auth_method:-"5G_AKA"}
n3iwf_address=${n3iwf_address:-"192.168.1.55"}
supi_or_suci=${supi_or_suci:-"2089300007487"}
k=${k:-"5122250214c33e723a5dd523fc145fc0"}
opc_type=${opc_type:-"OP"}
opc=${opc:-"c9e8763286b5b9ffbdf56e1297d0887b"}
ike_bind_addr=${ike_bind_addr:-"192.168.1.50"}
Thanks,
Udhay
Beta Was this translation helpful? Give feedback.
All reactions