From 82ad64798a2f01d01e166c1d3e98081a1cd3e304 Mon Sep 17 00:00:00 2001 From: Carlos Antonio De Lima Filho <carlos.lima.106@ufrn.edu.br> Date: Tue, 3 Dec 2024 23:32:21 +0000 Subject: [PATCH] Update README.md --- .../openairinterface-install-scripts/README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/openairinterface5g/openairinterface-install-scripts/README.md b/openairinterface5g/openairinterface-install-scripts/README.md index 7d68af7b..0193ea84 100644 --- a/openairinterface5g/openairinterface-install-scripts/README.md +++ b/openairinterface5g/openairinterface-install-scripts/README.md @@ -267,6 +267,8 @@ However, if you are trying to connect to the 5G Core located on another PC, you **Step 9:** Enabling packet forwarding within the namespace: > sudo ip netns exec oai-ue1 sysctl net.ipv4.conf.all.forwarding=1 +> +> sudo ip netns exec ip route add default via 192.168.2.1 dev veth2 **Step 10:** Setting default policy for packet forwarding within the namespace to ACCEPT:: @@ -364,9 +366,10 @@ The UE parameters (figure below) must be equal to the slice 1 configuration file **Step 10:** Setting default policy for packet forwarding within the namespace to ACCEPT: -**Important:** If you are using the same PC for both UEs, and you have already done the configuration for the UE 1, you can skip the commands below. - > sudo ip netns exec oai-ue2 iptables -P FORWARD ACCEPT +> +> +> sudo ip netns exec ip route add default via 192.168.2.1 dev veth2 **Step 11:** Enable packet forwarding on the Host: -- GitLab