Part of this I traced back by looking at the tcpdump command being called: (A little globe to start, an "x" to stop which makes sense, and what appears to be a fish to clear the buffer.) Once I did start the monitor, performance was EXTREMELY slow. My first impression on opening this program is confusion with the UI you have to hover over the buttons at the top to see the help text and figure out what they do. (Other commercial Mac networking tools, which include wrappers for tcpdump as well as other network tools, cost more than twice what PacketStream does.) I hope you'll give it a try.
On the other hand, PacketStream has come a long way since its earliest design (when all it did was "spit out the output of tcpdump into a window"), and it offers a lot of power in an inexpensive package. If you want every tcpdump option in the GUI, try WireShark (a powerful but ugly Gtk application that isn't the least bit Mac-like). If you are a command-line power user who wants to be able to toggle every flag/switch in tcpdump's output, PacketStream isn't for you. Regarding what PacketStream is and isn't: it's designed to be an easy-to-use wrapper of tcpdump's functionality, exposing a good deal of tcpdump's functionality, in a way that is simple, elegant, and Mac-like. Finally, with support for AppleScript (you can call PacketStream with an AppleScript) and the Services menu, PacketStream now offers a greater degree of Mac system integration/inter-application communication than before. It also exposes more of tcpdump's options to the user, specifically the ability to display actual packet data in the main interface.
#PACKETSTREAM REVIEWS PASSWORD#
This new release of PacketStream addresses many of the issues raised in previous reviews, including Keychain integration to avoid prompting the user repeatedly for a password when running a network scan.
0 kommentar(er)
