Free packets per second software for linux

Packet Debugger presents a debugger-like UI for pcap packet capture files.

The Packet Debugger (pdb) allows users to work with packet streams as if they were working with a source code debugger.

Users can list, inspect, modify, and retransmit any packet from captured files, as well as work with live packet captures.

Packet Excalibur is a multi-platform graphical and scriptable network packet engine with extensible text-based protocol descriptions. It is a network tool designed to build and receive custom packets from network.

Pen testing firewalls, routers, or any network enable equipment. Validating your custom built protocols without the burden of writting lines of code. Teaching yourself how protocols works and articulates around each other.

Download the install package (PacketExcalibur_*.*_linux_tgz)

Unzip and untar the archive, run "make" in the "PacketExcalibur_*/main" directory,
- binaries are installed in /usr/sbin
- support packages are installed in /var/cache/excalibur
- preference file is created in the user home directory

NetPacket::Ethernet is a Perl module to assemble and disassemble ethernet packets.

SYNOPSIS

use NetPacket::Ethernet;

$eth_obj = NetPacket::Ethernet->decode($raw_pkt);
$eth_pkt = NetPacket::Ethernet->encode(params...); # Not implemented
$eth_data = NetPacket::Ethernet::strip($raw_pkt);

NetPacket::Ethernet provides a set of routines for assembling and disassembling packets using the Ethernet protocol.

RakNet project is a reliable UDP networking API.
RakNet is a networking API that is a wrapper for reliable UDP and higher level functionality on Windows, Linux, and Unix.
It allows any application to communicate with other applications on the same computer, over a LAN, or over the internet.
Although it could be used for any networked application, it was developed specifically for rapid development of online games and the addition of multiplayer to single player games.
Main features:
- Secure connections
- With one line of code Raknet will automatically use SHA1, AES128, SYN Cookies, and RSA to prevent connection spoofing, replay attacks, data eavesdropping, packet tampering, and MitM attacks. Overhead averages 12 bytes per datagram.
- Voice communication
- Using Speex for encoding / decoding, 16 bit audio can be transmitted using approximately 1000 bytes per second.
- Remote terminal
- Using either Telnet or secure RakNet, you can remotely administrate your applications. The system has built-in commands for most RakNet functions and is designed for users to extend for their own purposes. Example capabilities include application resets, password management, and logging.
- Application directory server
- The application directory server allows servers to list themselves for clients to find and connect to. The system uses a key / value system. Listing your server and posting new rules are both done with a single line of code.
- Autopatcher
- Update your users with database driven binary delta patches, or use a simpler version for updates such as user skins or maps.
- Object replication system
- RakNets object and memory replication system provides a framework from which you can synchronize your program state. It requires no changes to your program architecture and there is no unneeded overhead. Memory is replicated through a single function call, with support for callbacks for serialization of complex types such as pointers.
- Network traffic compression
- The BitStream class allows compressed writes of vectors, matrices, quaternions, and real numbers between -1 and 1. It also supports delta compression, by which unchanged values only use a single bit.
- Remote function calls
- While you can send and interpret your own bit streams, remote function calls make this process easier as you now deal with functions rather than raw data. Remote function calls only take 1-2 bytes of overhead and allow both static C function calls and class member function calls. Return values are also supported.
- Routing and multicasting
- RakNet supports automatically updated connection graphs, which are used for routing and multicasting via a minimum spanning tree. You could, for example, use RakNet for highly efficient distributed peer-to-peer file sharing. Simpler applications include directed messages between clients and efficient broadcasts.
- Robust communication layer
- Flow control, message ordering on different channels, message coalescence, and splitting and reassembly of packets larger than the MTU are transparently handled for you.

DNS Blacklist Packet Filter project is a Linux netfilter client that decides whether to accept or drop packets based on the results of a DNS blacklist query (such as MAPS, SORBS, or SPEWS, to name a few).

One use is to filter all incoming SMTP SYN packets for spam filtering.

Layer-7 Packet Classifier for Linux is a packet classifier for Netfilter that identifies packets based on application layer (OSI layer 7) data. This means that it is able to classify packets as HTTP, FTP, Gnucleus, Kazaa, etc., regardless of ports.
It complements existing matches that classify based on port numbers, packet length, TOS bits, and so on. Combined with Linux QoS, it allows for full layer 7 packet shaping.
Main features:
- Patches for Linux 2.4 and 2.6
- Support for TCP, UDP and ICMP over IPv4
- Uses Netfilters connection tracking of FTP, IRC, etc
- Examines data across multiple packets
- Number of packets examined tunable on the fly through /proc
- Number of bytes examined tunable at module load time
- Distinguishes between new connections (those still being tested) and old unidentified connections
- Gives access to both Netfilter and QoS (rate limiting) features
- With the Netfilter "helper" match, you can distinguish between parent and child connections (e.g. ftp command/data)

RADIUS::Packet is an object-oriented Perl interface to RADIUS packets.

SYNOPSIS

use RADIUS::Packet;
use RADIUS::Dictionary;

my $d = new RADIUS::Dictionary "/etc/radius/dictionary";

my $p = new RADIUS::Packet $d, $data;
$p->dump;

if ($p->attr(User-Name eq "lwall") {
my $resp = new RADIUS::Packet $d;
$resp->set_code(Access-Accept);
$resp->set_identifier($p->identifier);
$resp->set_authenticator($p->authenticator);
$resp->set_attr(Reply-Message) = "Welcome, Larry!rn";
my $respdat = auth_resp($resp->pack, "mysecret");
...

RADIUS (RFC2138) specifies a binary packet format which contains various values and attributes. RADIUS::Packet provides an interface to turn RADIUS packets into Perl data structures and vice-versa.

RADIUS::Packet does not provide functions for obtaining RADIUS packets from the network. A simple network RADIUS server is provided as an example at the end of this document. Also, a RADIUS::Server module is under development which will simplify the interface.

Net::DHCP::Packet is a Perl module with object methods to create a DHCP packet.

SYNOPSIS

use Net::DHCP::Packet;

my $p = new Net::DHCP::Packet->new(
Chaddr => 000BCDEF,
Xid => 0x9F0FD,
Ciaddr => 0.0.0.0,
Siaddr => 0.0.0.0,
Hops => 0);

Represents a DHCP packet as specified in RFC 1533, RFC 2132.

CONSTRUCTOR

This module only provides basic constructor. For "easy" constructors, you can use the Net::DHCP::Session module.

new( )

new( BUFFER )

new( ARG => VALUE, ARG => VALUE... )

Creates an Net::DHCP::Packet object, which can be used to send or receive DHCP network packets. BOOTP is not supported.

Without argument, a default empty packet is created.

$packet = Net::DHCP::Packet();

A BUFFER argument is interpreted as a binary buffer like one provided by the socket recv() function. if the packet is malformed, a fatal error is issued.

use IO::Socket::INET;
use Net::DHCP::Packet;

$sock = IO::Socket::INET->new(LocalPort => 67, Proto => "udp", Broadcast => 1)
or die "socket: $@";

while ($sock->recv($newmsg, 1024)) {
$packet = Net::DHCP::Packet->new($newmsg);
print $packet->toString();
}

To create a fresh new packet new() takes arguments as a key-value pairs :

ARGUMENT FIELD OCTETS DESCRIPTION
-------- ----- ------ -----------

Op op 1 Message op code / message type.
1 = BOOTREQUEST, 2 = BOOTREPLY
Htype htype 1 Hardware address type, see ARP section in "Assigned
Numbers" RFC; e.g., 1 = 10mb ethernet.
Hlen hlen 1 Hardware address length (e.g. 6 for 10mb
ethernet).
Hops hops 1 Client sets to zero, optionally used by relay agents
when booting via a relay agent.
Xid xid 4 Transaction ID, a random number chosen by the
client, used by the client and server to associate
messages and responses between a client and a
server.
Secs secs 2 Filled in by client, seconds elapsed since client
began address acquisition or renewal process.
Flags flags 2 Flags (see figure 2).
Ciaddr ciaddr 4 Client IP address; only filled in if client is in
BOUND, RENEW or REBINDING state and can respond
to ARP requests.
Yiaddr yiaddr 4 your (client) IP address.
Siaddr siaddr 4 IP address of next server to use in bootstrap;
returned in DHCPOFFER, DHCPACK by server.
Giaddr giaddr 4 Relay agent IP address, used in booting via a
relay agent.
Chaddr chaddr 16 Client hardware address.
Sname sname 64 Optional server host name, null terminated string.
File file 128 Boot file name, null terminated string; "generic"
name or null in DHCPDISCOVER, fully qualified
directory-path name in DHCPOFFER.
IsDhcp isDhcp 4 Controls whether the packet is BOOTP or DHCP.
DHCP conatains the "magic cookie" of 4 bytes.
0x63 0x82 0x53 0x63.
DHO_*code Optional parameters field. See the options
documents for a list of defined options.
See Net::DHCP::Constants.
Padding padding * Optional padding at the end of the packet

See below methods for values and syntax descrption.

Note: DHCP options are created in the same order as key-value pairs.