Packet Sender is an open source utility to allow sending and receiving TCP, UDP, and SSL (encrypted TCP) packets. The mainline branch officially supports Windows, Mac, and Desktop Linux (with Qt). Other places may recompile and redistribute Packet Sender. Packet Sender is free and licensed GPL v2 or later. It can be used for both commercial and personal use.
Official releases of Packet Sender can be downloaded at PacketSender.com. Some places redistribute Packet Sender.
The mobile apps are open source and available at : https://github.com/dannagle/Packet_Sender_Mobile
Packet Sender Mobile binaries for iOS and Android may be purchased for a small fee on the Apple App Store and the Google Play Store. Packet Sender Mobile contains bare minimum permissions, no ads, no analytics, no "Review me!" nags, no email list sign-ups, no notifications, and no IAPs. It is absolutely nothing but the app. This is old-fashioned software development that respects the user. Please show your support.
Packets sets can be quickly saved/retrieved/shared using the free Packet Sender Cloud service. The cloud may also be used to publicly display and distribute your packets (via an URL) for collaboration, tutorials, end users, etc. Packet Sender may import public packet sets with public URL.
There are various reasons to do this:
If you are publishing a network API, maintaining a public cloud page is significantly easier than painfully detailing (IP, port, type, etc) the packets to your users. Plus, updating that page is easy.
More information about it can be found at https://cloud.packetsender.com/help
Packet Sender has a "portable" mode. At launch, it will look for
its run-time directory. For the SSL server, it will look for
Windows users, this directory is the same place as the .exe.
For Mac users, this run-time directory is at
If INI files are found, it will use them instead of
Packet Sender's built-in servers are configured to support either IPv4 or IPv6 but not both at the same time. For clients, Packet Sender GUI and CLI will seemlessly switch between the two modes upon sending (you may need to include the scope ID). Older versions of Packet Sender tried use both simultaneously, but testing found this unreliable. Click the IPv4 / IPv6 toggle on the bottom right to switch between the two.
Inside the settings, you may also force Packet Sender's servers to bind to a custom IP address. This can be very useful for systems with multiple NICs or complicated IP setups. Packet Sender will trigger an error if told to bind to an address that does not exist.
Packet Sender's multicast support is triggered by attempting to send to a IPv4 multicast address or via the mulitcast submenu). The feature is currently experimental and has these known problems.
There is no IPv6 multicast support, though it is on the roadmap. Sponsors wanting IPv6 multicast support are welcome to contact me.
For when the normal send system is not enough, you can now hammer a target IP with packets to see if your device can handle it. Please note that this feature is experimental and the metrics displayed have not been fully tested.
Packet Sender is identical for all the desktop versions. The only difference is its theme to match the operating system.
The fields at the top can be navigated using CTRL+1, CTRL+2, etc, up to CTRL+8 (send button). On Mac, the shortcut key is Command.
Packet Sender supports establishing encrypted connections over SSL. This is supported in the GUI and on the command line. Some notes on this:
Packet Sender bundles an internal "Snake Oil" certificate for use as a server for Windows. The certificate and key is in the same place as packet and settings.
Packet Sender bundles OpenSSL for use in Windows. On Mac and Linux, Packet Sender will use the native SSL libraries.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)
Packet Sender supports up to 5 smart responses. To use it, disable normal responses.
Packet Sender supports these macros when sending responses:
Packet Sender supports persistent TCP and SSL connections via a separate UI dialog. It is enabled by checkbox on the main window or in the settings dialog.
Persistent connections are not supported via the command line.
Packet Sender has a built-in subnet calculator. It is under the Tools menu.
The command line extension used in Windows installations is .com. Using .exe will launch the GUI. Leave off the extension and Windows will choose the correct program. The same executable controls the command line and GUI for Mac and Linux operating systems.
The command line system in Packet Sender follows the same pattern as other Linux utilities. It has a long name (such as --version) and a short name (such as -v). These options can be arranged in any order and Packet Sender will parse them correctly. The last 3 options are positional and must appear last. They are IP, port, and data. These last options are optional if using a stored packet.
packetsender --help Usage: packetsender [options] address port data Packet Sender is a Network UDP/TCP/SSL Test Utility by NagleCode See https://PacketSender.com/ for more information. Options: -?, -h, --help Displays this help. -v, --version Displays version information. -q, --quiet Quiet mode. Only output received data. -x, --hex Parse data-to-send as hex (default). -a, --ascii Parse data-to-send as mixed-ascii (like the GUI). -A, --ASCII Parse data-to-send as pure ascii (no \xx translation). -w, --wait <ms> Wait up to <milliseconds> for a response after sending. Zero means do not wait (Default). -f, --file <path> Send contents of specified path. Max 1024 for UDP, 100 MiB for TCP. -b, --bind <port> Bind port. Default is dynamic. -t, --tcp Send TCP (default). -s, --ssl Send SSL and ignore errors. -S, --SSL Send SSL and stop for errors. -u, --udp Send UDP. -n, --name <name> Send previously saved packet named <name>. Other options overrides saved packet parameters. -Arguments: -address Destination address. Optional for saved packet. -port Destination port. Optional for saved packet. -data Data to send. Optional for saved packet.
packetsender -taw 500 packetsender.com 22 "Hello\nWorld" TCP (56620)://18.104.22.168 48 65 6c 6c 6f 0a 57 6f 72 6c 64 Response Time:5:51:37.042 pm Response HEX:53 53 48 2D 32 2E 30 2D 4F 70 65 6E 53 53 48 5F 35 2E 33 70 31 20 44 65 62 69 61 6E 2D 33 75 62 75 6E 74 75 33 2E 31 2E 49 53 2E 31 30 2E 30 34 0D 0A Response ASCII:SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu3.1.IS.10.04\r\n
The command line has the option to ignore or abandon on SSL errors. The default is to ignore.
packetsender -saw 500 expired.packetsender.com 443 "GET / HTTP/1.0\r\n\r\n" SSL Error: The certificate has expired SSL (54202)://expired.packetsender.com:443 47 45 54 20 2f 20 48 54 54 50 2f 31 2e 30 0d 0a 0d 0a Cipher: Encrypted with AES(128) Response Time:3:24:55.695 pm Response HEX:48 54 54 50 2f 31 2e 31 20 34 32 31 20 0d 0a 53 65 72 76 65 72 3a 20 6e 67 69 6e 78 2f 31 2e 31 30 2e 30 20 28 55 62 75 6e 74 75 29 0d Response ASCII:HTTP/1.1 421 \r\nServer: nginx/1.10.0 (Ubuntu)\r
The only dependency is Qt SDK. Here is how to build the app.
The Windows and Mac versions were built using Qt 5.12
Here is the sequence of commands for Ubuntu 16.04. Please adapt to your Linux platform. Packet Sender requires no additional libraries beyond the stock Qt SDK. I have been told there are build issues with stock Fedora. If a Fedora wizard can get it to properly compile, please let me know, and I'll add your instructions.
If you are feeling adventurous, feel free to build from the master branch. It contains the latest stable build. The development branch should probably be avoided.
sudo apt-get update sudo apt-get install qt5-default build-essential wget https://github.com/dannagle/PacketSender/archive/(Version).tar.gz tar -xzvf (Version).tar.gz cd PacketSender-(Version)/src qmake PacketSender.pro make
To run use:
If it doesn't run, you may need to set it executable
chmod a+x PacketSender
Missing a feature? You can hire me to add it to Packet Sender.
GPL v2 or Later. Contact me if you require a different license.