Repository navigation
feat: recognize UEIPAddress in UpdatePDR - #591
Merged
Merged
Conversation
pirog-spb
reviewed
Feb 8, 2025
pirog-spb
approved these changes
Feb 11, 2025
pirog-spb
added a commit
that referenced
this pull request
Oct 31, 2026
Adapted from upstream a1b6f6a to the refactored extractPDR structure. Lookup UEIPAddress within PDI (findIEindex) instead of on PDR directly, so that UpdatePDR correctly recognizes UE IP address changes. Also fix a latent bug where the final 'missing' branch returned a nil error. Co-authored-by: Junxiao Shi <[email protected]> Co-authored-by: Alex Rozhkevich <[email protected]> Signed-off-by: pirog-spb <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This patch allows eUPF to recognize UEIPAddress field within UpdatePDR IE.
The test case comes from 1.pcapng.gz frame 34, which was generated by free5GC v3.4.4.
Existing code would log the following error upon encountering this message: