Wireshark-bugs: [Wireshark-bugs] [Bug 5041] Tshark bug when dissect the MC interface trace
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sun, 09 Dec 2012 00:23:35 +0000

changed bug 5041

What Removed Added
CC   mmann78@netscape.net

Comment # 1 on bug 5041 from 
Has this been fixed?  Testing with SVN 46464 there is significantly more output
in TShark.  This was probably due to improved dissection since v1.3.3 (can see
the multiple upper layer messages in Wireshark as well).

Note that the display filter names have since changed, so the string is now:

tshark -r packet_MC.dump -R "gsm_a.dtap.msg_mm_type > 0 or
gsm_a.dtap.msg_cc_type > 0 or gsm_a.bssmap.msgtype > 0 or sccp.message_type >
0" -T fields -E header=y -e frame -e frame.time_epoch -e ip.src -e ip.dst -e
sccp.slr -e sccp.dlr -e sccp.message_type -e gsm_a.dtap_msg_mm_type -e
gsm_a.dtap_msg_cc_type -e gsm_a.bssmap_msgtype -e gsm_a.imsi > result_MO.txt

Output is:
frame    frame.time_epoch    ip.src    ip.dst    sccp.slr    sccp.dlr   
sccp.message_type    gsm_a.dtap_msg_mm_type    gsm_a.dtap_msg_cc_type   
gsm_a.bssmap_msgtype    gsm_a.imsi
Frame 1: 1170 bytes on wire (9360 bits), 1170 bytes captured (9360 bits)   
1271940350.759288000    10.37.11.26    10.37.19.18   
0xac0559,0xe3075e,0x7307ea,0x830033,0xa4032f,0xa80003   
0x321c37,0x6d1aa2,0x110132,0xc1003e,0x481794,0xa01a15,0x360c14,0x07098b,0x740111,0xa30a2c,0x2a0c4e,0xc804a7,0xd6015d,0xc800e7,0xa31080,0x0a16ec
  
0x05,0x05,0x06,0x06,0x06,0x06,0x06,0x05,0x06,0x06,0x06,0x06,0x01,0x06,0x06,0x01,0x06,0x05
               460001516015761

You are receiving this mail because:
  • You are the assignee for the bug.
  • You are watching all bug changes.