Closed yoursunny closed 9 months ago
Hi @yoursunny,
Very impressive to see someone from the niche green forum interested in the 5G niche ;-)
Thanks a lot for your detailed issue, the issue is indeed at the line you mentioned, I'll fix it ASAP!
Thanks and cheers, Valentin
Hi @yoursunny,
PR #49 will fix your reported issue.
Thanks a lot for your report! Valentin
Describe the bug
packetrusher ue
command does not follow the.gnodeb.plmnlist.gnbid
configuration option in its NGSetupRequest packet. Instead, it always sends gNB ID starting with "000001".To Reproduce
config.yml
as below.sudo ./packetrusher ue
command.Expected behavior The traffic capture should have an NGSetupRequest message sent from PacketRusher gNB to the AMF. In id-GlobalRANNodeID IE of this message, the gNB should indicate itself to have gNB ID 000008.
Screenshots None.
Architecture (please complete the following information):
Log:
Pcap: 1.pcapng.gz The relevant packet is frame 16. The relevant section is decoded as:
Additional context This bug is caused by this line: https://github.com/HewlettPackard/PacketRusher/blob/c10560874c0bbd8241f75c5aaa44536b528e1d74/internal/common/tools/tools.go#L36 It overwrites the configured gNB ID with numbers starting with 1.
To solve this issue, I'd recommend this logic: