-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UE cannot connect to the internet #28
Comments
Same problem. |
What is the result of |
Issue Description: We appreciate if you can guide us through this issue. Environment Deployment Status The UERANSIM has been deployed inside another virtual machine and ran after the free5gc-compose is up and running. Current Behavior To better understand and debug the issue, we monitored several interfaces on both the UERANSIM and free5gc-compose virtual machines. Debugging Details Monitoring upfgtp interface in the UPFb function => No packets observed Verifying if upfgtp interface is assigned an IP address => no IP address is assigned to the upfgtp interface. We appreciate if someone can guide us towards verifying the reason for this. UERANSIM Applying the changes suggested by #26 does not fix the issue nor changed the above reported outputs |
Hi @hyame-alameddine, is there any updates on this issue ? |
Hello @abousselmi; We fixed the issue by doing the following: 2- We deployed the UERANSIM on the same virtual machine hosting the free5gc-compose.
3- We uncommented the line natifname: eth0 in free5gc-compose/config/ubfcfgb, free5gc-compose/config/ubfcfg1, free5gc-compose/config/ubfcfg2. 4- We run the following on free5gc-compose
5- We build the UERANSIM gnb and UE
6- We added post routing into the upfb network setting by running the following:
|
Thank you for your feedback. This is very well detailed. I will include it in the README of the project. Bests, |
Have you tried again to deploy free5gc-compose and ueransim on the different computers, I had the same problem you had before. Thank you |
Hello, Wrong configuration: Good configuration: Root cause of my problem was in the fact that I was doing changes in the wrong configuration file. All online manuals were pointing to the BUILD directory (for example: free5gc/NFs/upf/build/config/upfcfg.yaml) however when I was running free5gc core it was reading parameters from the free5gc/config/upfcfg.yaml. In my case to fix configuration I needed to change file
Hope it helps |
Hello! Good configuration: and why in configuring the /free5gc/config/upfcfg.yaml the IP address should be 10.0.6.103( my free5gcVM has 192.168.56.1/24 address) ? With respect, a student that has the same problem of uesimtun0 not pinging google.com |
Environment
The UPFs have been deployed following the comment at the following link: #26 (comment). So the UPFs start running a bash script to install the required iptables rules.
The UERANSIM has been deployed inside another Docker container attached to free5gc-compose Docker network and ran after the free5gc-compose is up and running.
Configurations
We provided each NF a static IP address, the ones reported in the following code are the ones related to the UERANSIM container (10.100.200.20) and to the AMF container (10.100.200.15).
UERANSIM/config/free5gc-gnb inside the UERANSIM Docker container
Current Behavior
The
ping -I uesimtun0 8.8.8.8
command ran inside the UERANSIM Docker container is not receiving any ICMP reply as expected.In order to try to understand the reason of this behavior we monitored some internal interfaces on the UERANSIM container and on the upfb container.
UERANSIM
For the UERANSIM container we monitored the
uesimtun0
and theeth0
interfaces.UPFB
For the upfb we monitored the
eth0
and theupfgtp
interfaces.Logs
amf.log
nrf.log
smf.log
upf1.log
upf2.log
upfb.log
nr-gnb.log
nr-ue.log
We have not seen any packet passing through the
upfgtp
interface of the upfb container, so we think that we are missing some configuration or we are misconfiguring the deployment.Hoping someone can give us an hint on how to solve this issue, best regards!
The text was updated successfully, but these errors were encountered: