Skip to content
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

loopback interface names seem reversed #3

Open
cyberxml opened this issue Mar 27, 2021 · 1 comment
Open

loopback interface names seem reversed #3

cyberxml opened this issue Mar 27, 2021 · 1 comment

Comments

@cyberxml
Copy link

These instructions assign the address "127.0.0.2" to interface "lo:" per the following command

ifconfig lo: 127.0.0.2 netmask 255.0.0.0 up

In the file ue.nfapi.conf you set the local address to 127.0.0.2 and the local interface to lo"

While in the file rcc.band7.tm1.nfapi.conf you set the local address to 127.0.0.1 and the local interface to lo:

This configuration did not work for me. I switched the interface definitions as below and the oipX interfaces were assigned tunnel address as expected.

In the file ue.nfapi.conf I set the local address to 127.0.0.2 and the local interface to lo:

While in the file rcc.band7.tm1.nfapi.conf I set the local address to 127.0.0.1 and the local interface to lo

@s5uishida
Copy link
Owner

Hi @cyberxml

I changed the configuration files for matching the assignment of the addresses of UE / RAN lo interfaces as shown in the figure of 1. Environment.

These original configuration files and the description in this figure are reversed. So I checked the operation with my changed settings.

In addition, I think that it is good if the lo addresses of the other party of local / remote is consistent in each file of UE and RAN.

  • ue.nfapi.conf (for UE)
  • rcc.band7.tm1.nfapi.conf (for RAN)

Regards,

--Shigeru

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants