Fix UE not receiving packets #71
Merged
Conversation
This file contains 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
Signed-off-by: Raguideau <[email protected]>
linouxis9
approved these changes
Feb 7, 2024
| @@ -154,6 +155,8 @@ func SetupGtpInterface(ue *context.UEContext, msg gnbContext.UEMessage) { | |||
| log.Fatal("[GNB][GTP] Unable to create Kernel Route ", err) | |||
| } | |||
|
|
|||
| time.Sleep(time.Duration(100) * time.Millisecond) // Wait for MAC address to be attributed to ueVrfDevice | |||
There was a problem hiding this comment.
It would be great to understand why we need that but LGTM!
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.
Types of changes
Bug fix (non-breaking change which fixes an issue)
Using EBPF the packets would not always reach vrf due to missing entry in arp table. -> Add VRF as neighbour when creating VRF.
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Signed-off-by: Author Name <[email protected]>to accept the DCO.