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

Separate N3 and N9 interfaces do not work if listed separately #35

Open
yoursunny opened this issue Aug 9, 2023 · 0 comments
Open

Separate N3 and N9 interfaces do not work if listed separately #35

yoursunny opened this issue Aug 9, 2023 · 0 comments

Comments

@yoursunny
Copy link
Contributor

In my environment, the UPF is expected to use separate network interfaces for N3 and N9 interfaces.
The example UPF config allows two methods to write the configuration:

If there are multiple connection, set addr to 0.0.0.0 or list all the addresses

In the first method, I can write as:

gtpu:
  forwarder: 'gtp5g'
  ifList:
    - addr: '0.0.0.0'
      type: 'N3'

In the second method, I can write as:

gtpu:
  forwarder: 'gtp5g'
  ifList:
    - addr: '172.25.194.6'
      type: 'N3'
    - addr: '172.25.196.6'
      type: 'N9'

As tested, only the first method works.
This is caused by forwarder.NewDriver only listens on the first configured IP address, and ignores other addresses in ifList:

for _, ifInfo := range cfgGtpu.IfList {
mtu = ifInfo.MTU
gtpuAddr = fmt.Sprintf("%s:%d", ifInfo.Addr, factory.UpfGtpDefaultPort)
logger.MainLog.Infof("GTP Address: %q", gtpuAddr)
break
}

Suggested solution is updating the example config, asking user to take the first method only.

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

1 participant