Packet Sender gives you a desktop interface and command-line client for sending TCP, UDP, SSL, and HTTP requests while you test a service you own or are authorized to assess. On Debian and Ubuntu, install the distribution package with apt. If you need the upstream desktop build, Packet Sender also publishes an AppImage and a Snap package.
Choose the installation route
Your package source determines how updates arrive, with apt integrating into Debian-based systems and the upstream AppImage and Snap releases following Packet Sender’s own release channel.
| Route | Best when | Command or action |
|---|---|---|
| apt | You use Debian, Ubuntu, or a derivative with the package available. | Install packetsender from your configured repository. |
| Snap | You already use snapd and want the publisher’s Snap package. | Install packetsender with snap. |
| AppImage | You want the upstream portable desktop build without a system-wide package install. | Download the x86_64 AppImage, make it executable, then run it. |
Install Packet Sender with apt
Refresh package metadata, then install Packet Sender when apt-cache policy packetsender shows a candidate for your distribution.
sudo apt update
sudo apt install packetsender
Start the graphical application from your desktop launcher, or use the command-line client with an address, port, and payload in a controlled test.
packetsender --version
The available version can differ from the version on the official download page because distribution repositories package and update software on their own schedule. For the wider decision between repository, Snap, and portable installs, read package management on Linux.
Install Packet Sender with Snap
The Packet Sender Snap page publishes the latest/stable channel, and Ubuntu needs snapd only when the snap command is unavailable.
sudo apt update
sudo apt install snapd
sudo snap install packetsender
Run packetsender –version after installation to identify the build on your machine, then check package permissions and the test environment before treating a Snap-related connection failure as an application defect.
Run the upstream AppImage
The official download page offers an x86_64 AppImage for Desktop Linux. Download it from that page and make the downloaded file executable before launching it.
chmod a+x Packet_Sender-*.AppImage
./Packet_Sender-*.AppImage
An AppImage is a portable application file rather than an apt-managed package. Keep it in a directory you control and return to the official download page for a newer upstream release.
Send a controlled TCP request from the CLI
Packet Sender’s command format is packetsender [options] address port data. The following command sends the ASCII text hello to a TCP service on your local machine and waits up to one second for a response. For a primer on running terminal commands, see the Linux command line.
packetsender --tcp --ascii 127.0.0.1 19091 hello --wait 1000
Use an address and port for a service you operate or have permission to test. A failed connection means no compatible service accepted the request at that destination, or a firewall or network policy blocked it. Learn how to inspect listening services with netstat and ss commands on Linux before changing Packet Sender options.
Pick TCP, UDP, or TLS deliberately
TCP establishes a connection and delivers an ordered byte stream, while UDP sends independent datagrams without a connection handshake and fits a protocol that does not provide delivery confirmation.
Packet Sender also supports SSL, which the project describes as encrypted TCP, plus HTTP and HTTPS requests. Protocol choice must match the service you are testing. If you need a refresher on addresses, name resolution, and ports, see Linux networking, IP configuration, and DNS.
Troubleshoot a connection failure
Start with the destination, protocol, and port because Packet Sender cannot make a TCP request succeed when the target only exposes UDP or no service listens on the chosen port.
- Confirm the server process is running and listening on the intended address and port.
- Match Packet Sender’s TCP, UDP, SSL, or HTTP mode to the service protocol.
- Check local and network firewall rules before retrying.
- Use a local address first when you need to separate an application issue from a routing issue.
A firewall protects the host by allowing or rejecting traffic according to its rules. Review Linux firewalls, SELinux, and AppArmor before opening a port or weakening a policy.
Remove Packet Sender
Remove the package with the same package manager that installed it. The apt command removes the Debian or Ubuntu package and its unused dependencies.
sudo apt autoremove --purge packetsender
For a Snap install, run sudo snap remove packetsender. For an AppImage, delete the AppImage file you downloaded.
Packet Sender installation checklist
Use this short check before you send traffic to a test service.
- Install from apt, Snap, or the official AppImage path that fits your system.
- Run packetsender –version to identify the installed build.
- Use only services and networks you are authorized to test.
- Verify the service address, port, and protocol before diagnosing the client.
Frequently asked questions
These answers cover the installation choices that change how Packet Sender behaves on Linux.
Can I install Packet Sender with apt?
Yes. If your Debian or Ubuntu repository provides the packetsender package, run sudo apt update followed by sudo apt install packetsender.
Which Packet Sender installation method should I use on Linux?
Use apt when your distribution provides the package, Snap when you use snapd, or the official AppImage when you want the upstream portable desktop build.
Why does Packet Sender fail to connect?
Check that the target service is running, the address and port are correct, the selected protocol matches the service, and firewall rules permit the connection.
When a request still fails, inspect the listening service with ss and compare its address, port, and protocol with the Packet Sender command before changing firewall rules.