How to trigger 5G Procedures (handover, paging, idle mode etc) #132
-
Hello everyone, I need some help using PacketRusher with free5GC. I've been struggling to figure out how to trigger various 5G procedures in the core network, particularly the handover process. I've looked through the documentation, but it seems that a usage guide for PacketRusher isn't available yet. Could anyone guide me on how to trigger a handover in the 5G core using PacketRusher? Any insights or resources would be greatly appreciated! Thank you in advance for your assistance. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Hi @MShayanNazeer, I'm happy to help! To see all the possible commands, I would advise you to run the following the command: For these procedures to work, you must be able to create two gNodeB with PacketRusher: PacketRusher automatically creates a second gNodeB with the same configuration as the first gNodeB, but with the IP used by the second gNodeB next to the first gNodeB: if the first gNodeB has IP 10.0.0.1 in config.yml, the second gNodeB created automatically by PacketRusher will have IP 10.0.0.2 and this cannot be configured differently for now. I hope it helped, feel free to reach out if you need more help! Thanks and best regards, |
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
Hi @MShayanNazeer,
I'm happy to help!
To see all the possible commands, I would advise you to run the following the command:
sudo ./packetrusher multi-ue --help
.One example is for eg.
sudo ./packetrusher multi-ue -n 1 -xnh 3000 -idl 13000 -ngh 23000
.This command will create and register an UE, make it do a Xn Handover to another UE after 3000 ms, then a switch to CM-IDLE and then CM-CONNECTED procedure after 13000 ms, and then finally a NGAP Handover after 23000 ms.
For these procedures to work, you must be able to create two gNodeB with PacketRusher:
PacketRusher automatically creates a second gNodeB with the same configuration as the first gNodeB, but with the IP used by the second gN…