Actions
Bug #2711
closedwireshark claims SI 2ter is wrong
Start date:
12/05/2017
Due date:
% Done:
100%
Spec Reference:
Description
my wireshark "Wireshark 2.5.0 (v2.5.0rc0-459-gce96407447)" claims that the SI2ter produced by osmo-bsc with the following config is wrong:
Let's verify if it's really wrong, either by manual spec compare and/or by looking it with an alternative decoder e.g. of TEMS
Files
| 2ter.png | View 2ter.png | 123 KB | screensho | ||
| 2ter.pcapng | 2ter.pcapng | 956 Bytes | pcap file | ||
| osmo-bsc.cfg | osmo-bsc.cfg | 4.91 KB | BSC config file |
Related issues
Updated by msuraev over 6 years ago
- Status changed from New to In Progress
Curiously - the actual 2ter from GSMTAP is decoded properly, only when it's transmitted over RSL the decoding fails. Verified with latest master of both BSC and BTS. Not sure yet if it's some bug in BSC which is compensated by BTS or it's a bug in wireshark dissector.
Updated by msuraev over 6 years ago
- Related to Bug #1635: RSL RELASE indication and other messages include L3 information added
Updated by laforge over 6 years ago
- Project changed from OpenBSC to OsmoBSC
- Category deleted (
libbsc)
Updated by msuraev over 6 years ago
- Related to deleted (Bug #1635: RSL RELASE indication and other messages include L3 information)
Updated by msuraev over 6 years ago
- % Done changed from 0 to 70
Fix submitted for review in gerrit 5269. Careful review of the other SI with Rest Octets revealed the same issue with SI2bis - the fix is available in gerrit 5272.
Updated by msuraev over 6 years ago
- Related to Bug #2735: Malformed RF RESource INDication added
Updated by msuraev over 6 years ago
- Status changed from In Progress to Resolved
- % Done changed from 70 to 100
Actions
