-
Notifications
You must be signed in to change notification settings - Fork 56
Feature: Add IPv6 support #34
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
base: main
Are you sure you want to change the base?
Conversation
andy89923
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
Sorry, I am not digging into the implementation yet.
Here are some quick suggestions for this PR!
Welcome to discuss, thanks!
|
Some refactors will be added before I unset the Draft state of this pull request |
|
Hi @adjivas , Thanks for the contribution. I suggest to change the base branch to 'next' to see the compatible. |
|
Hi @andy89923 , Thank's for this new suggestion, so I will work with the 'next' branch I open this PR for the IPv6 support free5gc/udm#48 |
|
Please rebase to the latest release, thanks! |
|
Hello @andy89923 |
andy89923
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again for the PRs!
We will test all the PRs related together when they are ready.
|
Hello @andy89923 |
|
Hi @adjivas , Thanks for the PR! Your 'main' is 24 commits behind main branch in free5gc. |
|
@andy89923 sure it's done! |
andy89923
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM!
@Alonza0314 Please help test these PRs with IPv6 support.
| RegisterIPv4 string `yaml:"registerIPv4,omitempty" valid:"host,optional"` // IP that is registered at NRF. | ||
| RegisterIP string `yaml:"registerIP,omitempty" valid:"host,optional"` // IP that is registered at NRF. | ||
| BindingIPv4 string `yaml:"bindingIPv4,omitempty" valid:"host,optional"` // IP used to run the server in the node. | ||
| BindingIP string `yaml:"bindingIP,omitempty" valid:"host,optional"` // IP used to run the server in the node. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ianchen0119 ,
Do you think we need RegisterIPv4 and RegisterIP simultaneously?
Keep RegisterIPv4 to maintain various places for old configuration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can remove RegisterIPv4 and keep RegisterIP only
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tim-ywliu Hello,
Some config files like free5gc/ausfcfg.yaml use the field RegisterIPv4
I kept it in the SBI for compatibility, but I removed it from the
context
Hello,
This PR adds the RegisterIP/BindingIP fields, we can set them with IPv4 or IPv6 values
For not introduce any breaking changes, the RegisterIPv4/BindingIPv4 are the fall back of the RegisterIP/BindingIP fields.
It's adds a validation rule to avoid missing or duplicate field.
I test this PR with this fix of the Free5gs's Nrf to have this valid results:

