|Release Type||Release Number||Release Date|
|Original||CloudShark 2.2 build 2127||June 5th, 2014|
|Maintenance Release 1||CloudShark 2.2 build 2151||June 25th, 2014|
|Maintenance Release 2||CloudShark 2.2 build 2168||July 7th, 2014|
|Maintenance Release 3||CloudShark 2.2 build 2176||July 11th, 2014|
|Maintenance Release 4||CloudShark 2.2 build 2201||August 15th, 2014|
CloudShark 2.2 brings big increases in performance, file-size support, concurrent users, and more. We’ve upgraded key components behind the scenes letting you run longer analysis, work with larger files, and deliver results to multiple users with fewer bottlenecks.
The big news: There is no more 200 MB limit to the size file you can analyze!
This comes with some caveats. Analysis tools are still capped at what can be completed in a reasonable amount of time. To run some tools and filters against larger files, your hardware will need to be powerful enough.
We have created a few hardware profiles and expected file-size support based on them. Please get in touch with support to learn more about specific tuning you can perform.
CloudShark Enterprise customers should contact us after upgrading to discuss how to tune their server for their specific number of users.
If you are running CloudShark 2.1 or older you must run the following command to upgrade:
su - bash <(curl get.cloudshark.org/upgrade2.2)
Upgrading our server-side components has sped up pretty much every part of CloudShark. On identical hardware, you can see typically 2x faster response times for some pages.
A few specific instances where improvements will be noticeable include:
CloudShark by default will now accept files up to 2 GB in size. Captures can be opened, filtered, analyzed and there are no more restrictions on viewing files based on file size. The local CloudShark Administrator can configure the maximum allowed size from the Settings page anywhere from 1 MB to 4 GB.
CloudShark for multi-tenant environments has been improved. When capture files are made public by one user, the Admin can decide if all the rest of the users on that same system should see public files shared by other users. In some cases this is helpful, however if your users should not know about each other, this option should be enabled on the Admin’s Settings page.
This also applies to tags. A user will only see tags auto-completed that have been applied to captures they have access to. Individual users who do not share captures will not see each other’s tags in the filter box on the main capture index.
CloudShark 2.2 has updated the graphing tool with a new default style, faster performance, and a new rendering engine on the server that can deliver PDF, SVG, PNG, and now JPG.
CloudShark 2.2 delivers tshark 1.10.7 behind the scenes, bringing bug fixes and updated protocol support for ANSI A, DVB-CI, GSM DTAP, GSM MAP, IEEE 802.11, LCSAP, LTE RRC, MAC LTE, Prism, RTP, SDP, SIP, and TCP
The Protocol Conversations window will now respond when clicking on
conversations by applying a display filter for that traffic to the capture file.
conversations will continue to bring up the Follow-Stream dialog box. If you would like to filter
those conversations, that option has always been available from within Follow Stream.
The online and offline installation processes have been improved behind the scenes. We have also improved our logging and diagnostics information collecting to assist our support team.
This release delievers tshark 1.10.9 which includes bug and vulnerability fixes.