Termshark VS PsPing

Hello fellow command-line devotees - termshark v2.4 is now available via github. Termshark is a terminal user-interface for tshark that tries to imitate the look and feel of Wireshark. The motivation is for when you're ssh-ed somewhere and want to study some network packets without the hassle of copying them back to your desktop. This release adds Wireshark-like packet search (ctrl-f to open) and profiles, like... Source: almost 2 years ago

Hello everyone - I made a new release of termshark: version 2.4. Termshark is my attempt at a terminal UI for tshark that shamelessly copies the look and feel of Wireshark. The motivation for termshark is for when you're ssh-ed somewhere, want to look at some packets quickly, but it's a pain to copy pcaps back to your desktop. This version adds a Wireshark-like packet-search (ctrl-f to open) and user profiles -... Source: almost 2 years ago

Hi everyone - I published termshark v2.4 yesterday on github. Termshark is a terminal UI for tshark that I've tried to make look similar to Wireshark. It's written completely in Go and so compiles down to a single executable for each platform. Github has pre-compiled binaries for Linux, macOS, Windows and the BSDs. The motivation for termshark is for when you have a pcap or a source of packets you want to check... Source: almost 2 years ago

Hello command-line colleagues - termshark v2.3 is now up on github. Termshark is a terminal user-interface for tshark that copies the look of Wireshark in 80x32. For this release, I've added configurable columns and a way to transfer the open capture file using magic-wormhole. Termshark can be convenient but for any non-trivial analysis, you need to get the pcap open in Wireshark. If you tend to ssh from within... Source: over 2 years ago

Hello everyone - termshark v2.3 is out now on github. Termshark is a terminal UI for tshark that copies the look of Wireshark, and is written 100% in Go. With this release, at last, you can configure the columns that are displayed, and I've also added a simple way to transfer the current pcap to another machine with magic wormhole. Termshark is convenient but sometimes you just need to get the pcap open in... Source: over 2 years ago

[1] https://learn.microsoft.com/en-us/sysinternals/downloads/psping. Source: over 1 year ago

I wonder what would happen if you tried using something like psping to do a TCP ping to the router. You can get that here if you don't already have it https://docs.microsoft.com/en-us/sysinternals/downloads/psping. Source: almost 2 years ago

A great tool is test FW rules is PSPing, it allows you to ping TCP ports to test your rules. Https://docs.microsoft.com/en-us/sysinternals/downloads/psping I use it all the time. Source: almost 2 years ago

PSPing could also be used as it does a TCP latency check rather than ICMP (see here: https://docs.microsoft.com/en-us/sysinternals/downloads/psping). Source: over 2 years ago

Try to improve your loopback performance. The game uses two seperate processes because reasons, and they comminicate with each other over the loopback device. You'd probably assume this is really efficient and limited only by your memory bandwidth + a small overhead. The overhead is actually very large. You can measure what your loopback transfer speed is by using a program called psping... Source: almost 3 years ago