Citing packit(1):
NAME
Packit - Packet analysis and injection tool
SYNOPSIS
Packet capture:
packit -m capture [-cGHnvsX] [-i interface] [-r|-w file]
expression
Packet injection:
packit -m inject [-t protocol]
[-aAbcCdDeFgGhHjJkKlLmMnNoOpPqQrRsSTuUvwWxXyYzZ] [-i interface]
DESCRIPTION
Packit is a network auditing tool. Its value is derived from its
ability to customize, inject, monitor, and manipulate IP
traffic. By
allowing you to define (spoof) all TCP, UDP, ICMP, IP, ARP, RARP
and
Ethernet header options, Packit can be useful in testing
firewalls,
intrusion detection systems, port scanning, simulating network
traffic
and general TCP/IP auditing. Packit is also an excellent tool for
learning TCP/IP.
Our packaged 1.0 version seems to be the last one that can be fetched
from upstream, which is long dead; HOMEPAGE http://packit.sf.net points
to a generic corporate stub.
Looking at the web first showed lots of false positives, i.e. tools with
with the same name.
FreeBSD packages an "updated" version, see
https://github.com/resurrecting-open-source-projects/packit/blob/master/ChangeLog
That project's README says:
Packit needs your help. If you are a programmer and if you wants
to help a nice project, this is your opportunity.
My name is Eriberto and I am not a C developer. I imported Packit
from its old repository[1] to GitHub (the original homepage and
developer are inactive). After this, I applied all patches found
in Debian project and other places for this program. All my work
was registered in ChangeLog file (version 1.1 and later releases).
Since noone could be bothered with updating our port since at least
2016, I doubt there's much interest.
packit is a mixture of tcpdump(1) and scapy(1), it has the worst
synopsis I've seen so far (which is wrong, btw.) and does not support
IPv6.
I see little value in beating a dead horse here like FreeBSD does;
I think we should instead point users at tcpdump and scapy for those are
maintained and usable.
Feedback? Objections? OK?
