e2term doesnt communicate with rtmgr_sim when running Setup in VM

[DerBambus]

Hi there, I am trying to make a RAN setup that is started by vagrant and then controlled by ansible, so I am running the SC_RIC in a Vagrant (Provider: Virtualbox) VM on Ubuntu 22.04. However, when I start the SC RIC Docker controller, the confirmation message for the E2Term IP Address in the RTMGR is never posted. I have tried changing the RTMGR_SIM IP address to 10.0.2.16, as 10.0.2.15 is used by Vagrant for the NAT.
Here are my docker logs:
Docker main log

I am using the default config values on the SC_RIC, which work when running the docker container on my regular desktop.
When I run the other components of the setup (on different VMs) They can all connect, however the UE doesn't get a response when pinging the 5gc, I dont know if these problems are related, but it is the only other issue I am only having on the VMs.

Any Ideas as to what I might be doing wrong?

[pgawlowicz]

If the 10.0.2.0 network is used by Vagrant, maybe you can change the network used by the RIC.

[DerBambus]

As far as I can tell, only the 10.0.2.15 address is blocked, these are the ip devices shown by ip a s :

I have tried setting the e2term to 10.0.2.16, but I had the same Issue. I also tried changing all addresses to the 10.10.2.0 network space, and it also persisted.

[pgawlowicz]

could you show the routing table: route -n

[DerBambus]

My shell didnt know the option -n I hope this is right?

[pgawlowicz]

route -n is another command, but does not matter.

It seems that the bridge interface used by the ORAN RIC is down, so it cannot work.
I would change the IP network used by the RIC and try again, you can find and replace 10.0.2. with sth else in the entire repo.

[DerBambus]

I Changed the Ip range to 10.10.2.0 now, I think last time it didn't work because I didn't realise I had to change the IPs in the .env file. The ric seems to be running correctly now, however I still cannot ping the 5gc from the Ue. The GNB and UE show that they are connected. Here is a screenshot of the recent 5gc logs, I cant really identify if the core network is having any problems:

[pgawlowicz]

what is the output of the srsUE console?

[DerBambus]

[pgawlowicz]

hmm, looks good. Could you share your gnb/srsue configs and logs?

[DerBambus]

sure,
gnb.log
ue.log
gnb_zmq.txt
ue_zmq.txt
I changed the config file types to txt, because git doesn't allow yaml and conf as upload file types

[pgawlowicz]

logs are empty.
Anyway, did you add the default route to the UE?

sudo ip netns exec ue1 ip route add default via 10.45.1.1 dev tun_srsue

Check this tutorial: https://docs.srsran.com/projects/project/en/latest/tutorials/source/srsUE/source/index.html

[DerBambus]

Sorry, didnt double check the logs when sshing them from the vms, these should work:
gnb.log
ue.log
I hadn't added the default route yet, I have tried that but it still isn't working. I also have added the ip route on the machine running the 5gc as the guide said. These logs are with the added routes now

[pgawlowicz]

DL and UL look good. The issue is probably related to a routing misconfiguration.