Hi!
I've improved the layer23 gsmtap support to add support for * uplink frames, sent by layer23 to L1 * properly support dedicated channels with LAPDm * allow the user to specify the GSMTAP destination IP address
In order to use the new features, you need to 1) use the new gsmtap.patch for wireshark 2) use the '-i dstip' option of layer23, as the default is now to NOT generate GSMTAP UDP Packets
I'm attaching a screen-shot showing the wireshark decode of the LOC UPD REQ generated by layer23. As you can see from the packet list, the BTS responds with the UA packet containing the same LOC UPD REQ as part of the contention resolution in LAPDm, just as expected.
Cheers, Harald
Hi Jason,
On Thu, Mar 04, 2010 at 11:42:38AM -0500, Jason wrote:
Harald Welte wrote:
In order to use the new features, you need to 1) use the new gsmtap.patch for wireshark
Looks like we crossed paths. Do you want me to rebase my patch against your new version, or toss it?
As indicated, I'll be working on further gsmtap bugfixes, so I'd rather like to ask you to not work on the same part at the same time.
Hi all,
in the latest git commit, there has been another update of the wireshark gsmtap dissector patch. It now * dissects the SACCH L1 header in front of SACCH frames * properly hands off SACCH payload so SI5/6 are decoded correctly * displays a summary of the GSMTAP header in the protocol tree like the following example "GSM TAP Header, ARFCN: 871 (Downlink), TS: 0, Channel: SDCCH/4 (0)"
I've submitted this to the wireshark team for review. With some luck it will pass this time
There is an example pcap file showing bidirectional traffic from current osmocom-bb.git layer23. I've attached it to https://calypso.gnumonks.org/trac/wiki/WiresharkIntegration
Regards, Harald
baseband-devel@lists.osmocom.org
-
Harald Welte -
Jason