HewlettPackard / HewlettPackard/PacketRusher

[BUG] PacketRusher does not always handle received messages in order

Open
#102 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
193
Forks
47
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
PacketRusher does not always handle received messages in order.
Eg: UEContextRelease will be handled before the DownlinkNASTransport, so context / communication with UE will be freed and we'll unable to pass down the NAS message to UE.

Expected order:
![image](https://github.com/HewlettPackard/PacketRusher/assets/8758184/2fc862d9-bb62-4040-83ce-94ffa04f9495)
Handled order:
![image](https://github.com/HewlettPackard/PacketRusher/assets/8758184/4ea168d5-ef37-4e46-8d45-a26195f1fed1)

Contributor guide

Open the contributing guide

Research direction

Start by tracing how PacketRusher handles received UEContextRelease and DownlinkNASTransport messages, then reproduce the ordering shown in the issue. Done means received messages are handled in the expected order so the NAS message can still reach the UE.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.