You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gNB IP address is not incremented in NG Setup while testing Xn or N2 Handover Scenario. I see only SCTP port is incremented.
For example I run ./packetrusher multi-ue -n 2 --xnh 4000.
I see 2 NG SETUP request from Same IP 192.1.1.1 with only port incremented. tool is not changing IP address in Pathswitch request
also. Please find the pcap attached.
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
IT Should increment IP and send new IP address in each NG setup request
Screenshots
If applicable, add screenshots to help explain your problem.
Architecture (please complete the following information):
OS: [e.g. Linux]
Platform [e.g. x86_64, ...]
Version [e.g. 22]
Kernel [e.g. 5.0.0.23-generic]
Log:
If applicable, add log files to help understand your problem.
Pcap:
If applicable, add pcap files to help understand your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
gNB IP address is not incremented in NG Setup while testing Xn or N2 Handover Scenario. I see only SCTP port is incremented.
For example I run ./packetrusher multi-ue -n 2 --xnh 4000.
I see 2 NG SETUP request from Same IP 192.1.1.1 with only port incremented. tool is not changing IP address in Pathswitch request
also. Please find the pcap attached.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
IT Should increment IP and send new IP address in each NG setup request
Screenshots
If applicable, add screenshots to help explain your problem.
Architecture (please complete the following information):
Log:
If applicable, add log files to help understand your problem.
Pcap:
If applicable, add pcap files to help understand your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: