WiresharkIntegration » History » Version 3
laforge, 02/19/2016 10:49 PM
add link to wireshark bugzilla requesting gsmtap merge
| 1 | 1 | laforge | = Wireshark integration = |
|---|---|---|---|
| 2 | 1 | laforge | |
| 3 | 1 | laforge | [http://www.wireshark.org/ wireshark] is a popular Open Source protocol analyzer. Among many |
| 4 | 1 | laforge | other protocols, it includes dissectors for the GSM Layer 2 (LAPDm) and 3 (04.08). |
| 5 | 1 | laforge | |
| 6 | 3 | laforge | There also is a GSMTAP protocol dissector (not in wireshark mainline yet submitted as [https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4508 wireshark bug 4508], available in our |
| 7 | 1 | laforge | git repository in {{{src/wireshark/gsmtap.patch}}}), which allows real-time capture and |
| 8 | 1 | laforge | decode of GSM protocol messages encapsulated in GSMTAP (which is in turn encapsulated |
| 9 | 1 | laforge | in UDP and IP). |
| 10 | 1 | laforge | |
| 11 | 1 | laforge | So if you have a wireshark version with GSMTAP support, you can have realtime decode and |
| 12 | 1 | laforge | trace of GSM protocol messages. |
| 13 | 1 | laforge | |
| 14 | 3 | laforge | The OsmocomBB [wiki:layer23] program sends GSMTAP packets to the localhost (127.0.0.1) address |
| 15 | 1 | laforge | of the loopback interface (lo). |
| 16 | 2 | laforge | |
| 17 | 2 | laforge | == Screenshot == |
| 18 | 2 | laforge | |
| 19 | 2 | laforge | [[Image(gsmtap-wireshark.png, 66%)]] |
