Wireshark-bugs: [Wireshark-bugs] [Bug 1384] New: BSSGP.TLLI is not recognized properly in filter
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 19 Feb 2007 09:57:31 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1384

           Summary: BSSGP.TLLI is not recognized properly in filter
           Product: Wireshark
           Version: 0.99.5
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: veli-matti.truhponen@xxxxxxxxx


Build Information:
Version 0.99.5 (SVN Rev 20677)
--
When browsing one Gb over Ip -trace, the data was not recognized as NSIP. I
could decode it manually , no problem there. Then I opened the new BSSGP -layer
node and selected field TLLI and with mouse right-button "apply as filter" and
"selected". I expected to get something like this:

bssgp.tlli == 0x79df3217

but I got:

bssgp.iei.nacc_cause == 0x1f

When I wrote the expression "bssgp.tlli == 0x79df3217" in the expression and
pressed apply, it did not find any of the frames where that TLLI really exists. 

When I tried to select some other field (e.g. nsip.bvci == 3077), and attempted
the same trick, everything worked fine without any problems. I also tried
filter for gsm_a.imsi -field (gsm_a.imsi == "xxxxxxxxxxxxxxx"), and it worked
ok.


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.