Project

General

Profile

Actions

Bug #5842

open

ipa: investigate NSVC local and remote port configuration difference with wireshark dissector

Added by lynxis about 1 month ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
12/22/2022
Due date:
% Done:

0%

Spec Reference:

Description

While looking into OML traces between osmo-bsc and osmo-bts the wireshark displays NSVC link configuration different than the osmo-bsc is configured. osmo-bts works as osmo-bsc is configured.

The question:
Is only wireshark wrong, but ipa nanobts, osmo-bts, osmo-bsc works as expected?
or
Does wireshark and ipa nanobts have a different understanding than osmo-bts and osmo-bsc?

Please test with osmo-bsc with a ip.access nanobts and configure different local and remote udp ports and see if it works.

e.g. bsc config:

network
 bts 0
[..]
  gprs nsei 102
  gprs nsvc 0 nsvci 102
  gprs nsvc 0 local udp port 23100
  gprs nsvc 0 remote ip 192.168.1.44
  gprs nsvc 0 remote udp port 23000
  gprs nsvc 1 nsvci 202
  gprs nsvc 1 local udp port 23102
  gprs nsvc 1 remote ip 192.168.1.44
  gprs nsvc 1 remote udp port 23001

Wireshark will display local udp port and remote udp port switched in the OML obj (0xf2, 0x0, 0x0), PDU IPA Set Attributes.

Actions #1

Updated by lynxis about 1 month ago

  • Subject changed from ipa: investigate NSVC local and remote port configuration to ipa: investigate NSVC local and remote port configuration difference with wireshark dissector
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)