Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-bugs: [Wireshark-bugs] [Bug 3166] Support for GSM Um and LAPDm

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 5 Jan 2009 14:14:56 -0800 (PST)

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3166





--- Comment #10 from Jaap Keuter <jaap.keuter@xxxxxxxxx>  2009-01-05 14:14:55 PDT ---
Thanks for letting us know Duncan. 
When looking at the sample captures you've pointed to there are some which do
show up with malformed packets. There's packet 42 in sms-with-sendername.xml
and 38, 54 and 170 in requesting_phone_number.xml. Is that something in the
gsm_a_dtap dissector or in the data being fed to it?


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

  • References:
    • [Wireshark-bugs] [Bug 3166] New: Support for GSM Um and LAPDm
      • From: bugzilla-daemon
  • Prev by Date: [Wireshark-bugs] [Bug 3112] CDP Checksum Calculation Incorrect
  • Next by Date: [Wireshark-bugs] [Bug 3112] CDP Checksum Calculation Incorrect
  • Previous by thread: [Wireshark-bugs] [Bug 3166] Support for GSM Um and LAPDm
  • Next by thread: [Wireshark-bugs] [Bug 3166] Support for GSM Um and LAPDm
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation