Wireshark 2.1.0 (32-bit) Beta

# New and Updated Features
- You can now switch between between Capture and File Format dissection of the current capture file via the View menu in the Qt GUI.
- You can now show selected packet bytes as ASCII, HTML, Image, ISO 8859-1, Raw, UTF-8, a C array, or YAML.
- You can now use regular expressions in Find Packet and in the advanced preferences.
- Name resolution for packet capture now supports asynchronous DNS lookups only. Therefore the "concurrent DNS resolution" preference has been deprecated and is a no-op. To enable DNS name resolution some build dependencies must be present (currently c-ares). If that is not the case DNS name resolution will be disabled (but other name resolution mechanisms, such as host files, are still available).
- The byte under the mouse in the Packet Bytes pane is now highlighted.
- TShark supports exporting PDUs via the -U flag.
- The Windows and OS X installers now come with the "sshdump" and "ciscodump" extcap interfaces.
- Most dialogs in the Qt UI now save their size and positions.
- The Follow Stream dialog now supports UTF-16.
- The Firewall ACL Rules dialog has returned.
* New File Format Decoding Support
* New Protocol Support
* Updated Protocol Support: Bluetooth OBEX dissector (btobex) was renamed to Obex Dissector (obex), allow to DecodeAs it over USB, TCP and UDP. A preference was added to TCP dissector for handling IPFIX process information. It has been disabled by default.
* New and Updated Capture File Support and Micropross mplog
* New and Updated Capture Interfaces support: Non-empty section placeholder.
* Major API Changes
- The libwireshark API has undergone some major changes: The address macros (e.g., SET_ADDRESS) have been removed. Use the (lower case) functions of the same names instead. "old style" dissector functions (that don’t return number of bytes used) have been replaced in name with the "new style" dissector functions. tvb_get_string and tvb_get_stringz have been replaced with tvb_get_string_enc and tvb_get_stringz_enc respectively.
* Getting Wireshark: Wireshark source code and installation packages are available from https://www.wireshark.org/download.html.
* Vendor-supplied Packages: Most Linux and Unix vendors supply their own Wireshark packages. You can usually install or upgrade Wireshark using the package management system specific to that platform. A list of third-party packages can be found on the download page on the Wireshark web site.
* File Locations: Wireshark and TShark look in several different locations for preference files, plugins, SNMP MIBS, and RADIUS dictionaries. These locations vary from platform to platform. You can use About→Folders to find the default locations on your system.
* Getting Help: Community support is available on Wireshark’s Q&A site and on the wireshark-users mailing list. Subscription information and archives for all of Wireshark’s mailing lists can be found on the web site. Official Wireshark training and certification are available from Wireshark University.
* Frequently Asked Questions: A complete FAQ is available on the Wireshark web site.