rpms/mausezahn/F-10 README.Fedora, NONE, 1.1 import.log, NONE, 1.1 mausezahn.1, NONE, 1.1 mausezahn.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2

Vivek Shah bonii at fedoraproject.org
Sat Aug 8 16:15:47 UTC 2009


Author: bonii

Update of /cvs/pkgs/rpms/mausezahn/F-10
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv26388/F-10

Modified Files:
	.cvsignore sources 
Added Files:
	README.Fedora import.log mausezahn.1 mausezahn.spec 
Log Message:

Initial package import into CVS



--- NEW FILE README.Fedora ---
Important changes in Mausezahn in Fedora:

The binary executable for Mausezahn is available in Fedora as 
/usr/bin/mausezahn as opposed to /usr/bin/mz. This is done in
keeping with the Fedora packaging guidelines with regards to 
problems that can occur in namespace with short names like 
"mz". For more reference see here:
http://fedoraproject.org/wiki/PackageMaintainers/Packaging_Tricks#Use_of_common_namespace


--- NEW FILE import.log ---
mausezahn-0_34_9-1_fc9:F-10:mausezahn-0.34.9-1.fc9.src.rpm:1249748044


--- NEW FILE mausezahn.1 ---
.\"                                      Hey, EMACS: -*- nroff -*-
.\" First parameter, NAME, should be all caps
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
.\" other parameters are allowed: see man(7), man(1)
.TH MAUSEZAHN 1 "July 18, 2009"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
.\" .nh        disable hyphenation
.\" .hy        enable hyphenation
.\" .ad l      left justify
.\" .ad b      justify to both left and right margins
.\" .nf        disable filling
.\" .fi        enable filling
.\" .br        insert line break
.\" .sp <n>    insert n+1 empty lines
.\" for manpage-specific macros, see man(7)
.SH NAME
mausezahn \- a fast versatile packet generator
.SH SYNOPSIS
.B mausezahn
.RI  [ options ] "<arg_string> | <hex_string>" 
.br
.SH DESCRIPTION
.PP
.\" TeX users may be more comfortable with the \fB<whatever>\fP and
.\" \fI<whatever>\fP escape sequences to invode bold face and italics, 
.\" respectively.
\fBMausezahn\fP is a free fast traffic generator written in C which allows 
you to send nearly every possible and impossible packet. 
.br
Mausezahn can also be used for example as didactical tool in network labs or
for security audits including penetration and DoS testing. As traffic
generator Mausezahn is for example used test IP multicast or VoIP networks.
Speeds close to the Ethernet limit are reachable (depending on the HW
platform).
.br
.SH USAGE
Mausezahn supports two modes, \fBraw-layer-2\fP mode, where every single byte
to be sent can be specified, and \fBhigher-layer\fP mode, where packet builder
interfaces are used (using the \fI-t\fP option).
.br
To use the \fBraw-layer-2\fP mode, simply specify the desired frame as
hexadecimal sequence (the \fIhex_string\fP), such as
.PP
mausezahn eth0 "00:ab:cd:ef:00 00:00:00:00:00:01 08:00 ca:fe:ba:be"
.PP
The spaces within the byte string are optional and separate the Ethernet
fields (destination and source address, type field, and a short payload). The
only additional options supported are \fI-a\fP, \fI-b\fP, \fI-c\fP, and
\fI-p\fP. The frame length MUST be greater or equal 15 bytes.
.br
The \fBhigher-layer\fP mode is enabled using the \fI-t <packet_type>\fP
option. This option activates a packet builder and besides the
\fIpacket_type\fP an optional \fIarg_string\fP can be specified. The
\fIarg_string\fP contains packet-specific parameters, such as TCP flags, port
numbers, etc.
.PP
Note that Mausezahn requires root privileges. Please see the Mausezahn User's
Guide for more details or use Mausezahn's command line help.
.SH OPTIONS
Mausezahn has a built-in context specific help. Simply append the keyword
\fBhelp\fP to the configuration options. 
.br
The most important options are:
.TP
.B \-v
Verbose mode.
.TP
.B \-q
Quiet mode (only warnings and errors are displayed).
.TP
.B \-c <count>
Send the packet count times (default: 1, infinite: 0).
.TP
.B \-d <delay>
Apply delay between transmissions. The delay value can be specified in usec
(default, no additional unit needed), or in msec (e. g. 100m or 100msec), or
in seconds (e. g. 100s or 100sec).
.TP
.B \-p <lenght>
Pad the raw frame to specified length (using zero bytes). Note that for raw
layer 2 frames the specified length defines the whole frame length, while for
higher layer packets the number of additional padding bytes are specified.
.TP
.B \-a <Src_MAC|keyword>
Use specified source mac address (use hex notation such as 00:00:aa:bb:cc:dd).
By default the interface MAC address will be used. The keywords \fIrand\fP and
\fIown\fP refer to a random MAC address (only unicast addresses are created)
and the own address, respectively. You can also use the keywords mentioned
below (although broadcast-type source addresses are officially invalid).
.TP
.B \-b <Dst_MAC|keyword>
Use specified destination mac address.  By default a broadcast is sent in raw
layer 2 mode or the destination hosts/gateways interface MAC address in normal
(IP) mode. You can use the same keywords as mentioned above as well as
\fIbc\fP (or \fIbcast\fP), \fIcisco\fP, and \fIstp\fP. 
Please note that for the destination MAC address the \fIrand\fP keyword is
supported but creates a random address only once, even when you send multiple
packets. 
.TP
.B \-A <Src_IP|range|rand>
Use specified source IP address (default is own interface IP). Optionally the
keyword \fIrand\fP can again be used for a random source IP address or a range
can be specified, such as 192.168.1.1-192.168.1.100 or 10.1.0.0/16. Also a DNS
name can be specified for which Mausezahn tries to determine the corresponding
IP address automatically.
.TP
.B \-B <Dst_IP|range>
Use specified destination IP address (default is broadcast i. e.
255.255.255.255). As with the source address (see above) you can also specify
a range or a DNS name.
.TP
.B \-t <packet_type>
Create the specified packet type using the built-in packet builder. Currently
supported packet types are: \fIarp\fP, \fIbpdu\fP, \fIip\fP, \fIudp\fP,
\fItcp\fP, \fIrtp\fP, and \fIdns\fP. There is currently also a limited support
for ICMP. Enter \fI-t help\fP to verify which packet builders your actual
Mausezahn version supports. Also, for any particular packet type, for example
\fItcp\fP enter \fImausezahn \-t tcp help\fP to receive a context specific help.
.TP
.B \-T <packet_type>
Make this Mausezahn instance the receiving station. Currently (version 0.30)
only \fIrtp\fP is an option here and provides precise jitter measurements. For
this purpose start another Mausezahn instance on the sending station and the
local receiving station will output jitter statistics. See \fImausezahn \-T rtp
help\fP for a detailed help.
.TP
.B \-Q <[CoS:]vlan> [, <[CoS:]vlan>, ...]
Specify 802.1Q VLAN tag and optional Class of Service. An arbitrary number of
VLAN tags can be specified (that is you can simulate QinQ or even
QinQinQinQ...). Multiple tags must be separated via a comma or a period (e. g.
"5:10,20,2:30"). VLAN tags are not supported for ARP and BPDU packets (in
which case you could specify the whole frame in hex using the raw layer 2
interface of Mausezahn).
.TP
.B \-M <label[:cos[:ttl]][bos]> [, <label...>] 
Specify a MPLS label or even a MPLS label stack. Optionally for each label the
experimental bits (usually the Class of Service, CoS) and the Time To Live
(TTL) can be specified. And if you are really crazy you can set/unset the
Bottom of Stack (BoS) bit at each label using the \fIS\fP (set) and \fIs\fP
(unset) option. By default the BoS is set automatically and correctly. Any
other setting will lead to invalid frames. Enter \fI-M help\fP for detailed
instructions and examples.
.TP
.B \-P <ASCII_payload>
Specify a cleartext payload. Alternatively each packet type supports a
hexadecimal specification of the payload (see for example \fI-t udp help\fP).
.br
.SH COMBINATION OF RANGES
When multiple ranges are specified, e. g. destination port ranges AND
destination address ranges, then \fBall\fP possible combinations of ports and
addresses are used for packet generation. This can lead to a very huge number
of frames.
.br
.SH DISCLAIMER AND WARNING
Mausezahn has been designed as fast traffic generator so you quickly can
overwhelm a LAN segment with myriads of packets. And because Mausezahn should
also support security audits it is easily possible to create malicious
packets, SYN floods, specify port and address ranges, DNS and ARP poisoning,
etc.
.br
Therefore, don't use this tool when you are not aware of possible consequences
or have only little knowledge about networks and data communication.  If you
abuse Mausezahn for unallowed attacks and get caught, or damage something of
your own, then this is completely your fault.
.br
.SH EXAMPLES
Send BPDU frames for VLAN 5 as used with Cisco's PVST+ type of STP. Per
default Mausezahn assumes that you want to become the root bridge:
.PP
# mausezahn eth0 \-c 0 \-d 2s \-t bpdu vlan=5
.PP
Perform a CAM table overflow attack:
.PP
# mausezahn eth0 \-c 128000 \-a rand \-p 64
.PP
Perform a SYN flood attack to another VLAN using a VLAN hopping attack. This
only works if you are connected to the same VLAN which is configured as native
VLAN on the trunk.  We assume that the victim VLAN is VLAN 100 and the native
VLAN is VLAN 5. Also lets attack every host in VLAN 100 which use a IP prefix
of 10.100.100.0/24:
.PP
# mausezahn eth0 \-c 0 \-Q 5,100 \-t tcp flags=syn \-p 20
.PP
Send IP multicast packets to the multicast group 230.1.1.1 using a UDP header
with destination port 32000. Send one frame every 10 msec:
.PP
# mausezahn eth0 \-c 0 \-d 10msec \-B 230.1.1.1 \-t udp dp=32000 \-P "Multicast test packet"
.PP
Send UDP packets to the destination host target.anynetwork.foo using all
possible destionation ports and send every packet with all possible source
addresses of the range 172.30.0.0/16; pad with 1000 bytes and repeat this 10
times:
.PP
# mausezahn eth0 \-c 10 \-A 172.30.0.0/16 \-B target.anynetwork.foo \-t udp dp=1-65535 \-p 1000
.br
.SH AUTHOR
Herbert Haas 
.br
Visit www.perihel.at/sec/mz/ for Mausezahn news and additional information.
.PP
This manual page has been written by Vivek Shah <boni.vivek at gmail.com>
for the Fedora project.


--- NEW FILE mausezahn.spec ---
Name:		mausezahn
Version:	0.34.9
Release:	1%{?dist}
Summary:	A fast versatile packet generator

Group:		Applications/Internet
License:	GPLv2
URL:		http://www.perihel.at/sec/mz/
Source0:	http://www.perihel.at/sec/mz/mz-%{version}.tar.gz
Source1:	%{name}.1
Source2:	README.Fedora
BuildRoot:	%{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)

BuildRequires:	libpcap-devel >= 0.8, libnet-devel >= 1.1, cmake >= 2.4.0
Requires:	python-matplotlib

%description
Mausezahn is a free fast traffic generator written in C which allows you to 
send nearly every possible and impossible packet. Mausezahn can also be used 
for example as didactical tool in network labs or for security audits including
penetration and DoS testing. As traffic generator Mausezahn is for example used
to test IP multicast or VoIP networks. Speeds close to the Ethernet limit are 
reachable (depending on the HW platform).

%prep
%setup -q -n mz-%{version}
sed -i.optflags -e '/^SET(CMAKE_C_FLAGS/d' CMakeLists.txt

%build
%cmake .
make %{?_smp_mflags} VERBOSE=1

%install
rm -rf $RPM_BUILD_ROOT
make install INSTALL="%{__install} -p" DESTDIR=$RPM_BUILD_ROOT
find $RPM_BUILD_ROOT -type f -name "*.html" -delete
find $RPM_BUILD_ROOT -type f -name "*.pdf" -delete
mv $RPM_BUILD_ROOT%{_sbindir}/mz $RPM_BUILD_ROOT%{_sbindir}/%{name}
cp -p %SOURCE1 $RPM_BUILD_ROOT%{_mandir}/man1/
mv $RPM_BUILD_ROOT%{_defaultdocdir}/mz \
$RPM_BUILD_ROOT%{_defaultdocdir}/%{name}-%{version}
cp -p %SOURCE2 $RPM_BUILD_ROOT%{_defaultdocdir}/%{name}-%{version}/
cp -pr AUTHORS ChangeLog COPYING README \
$RPM_BUILD_ROOT%{_defaultdocdir}/%{name}-%{version}
rm $RPM_BUILD_ROOT%{_mandir}/man1/mz.1

%clean
rm -rf $RPM_BUILD_ROOT

%files
%defattr(-,root,root,-)
%{_sbindir}/%{name}
%{_defaultdocdir}/%{name}-%{version}/
%{_mandir}/man1/%{name}*

%changelog
* Sat Aug 8 2009 Vivek Shah <boni.vivek at gmail.com> 0.34.9-1
- Updated to new upstream version

* Tue Aug 4 2009 Vivek Shah <boni.vivek at gmail.com> 0.34.8-2
- Removed the cmake flags to be overriden by optflags

* Sat Aug 1 2009 Vivek Shah <boni.vivek at gmail.com> 0.34.8-1
- Updated to new upstream version
- Removed extra empty doc line from files section
- Removed INSTALL files from doc section
- Added Fedora specific flags

* Sat Jul 18 2009 Vivek Shah <boni.vivek at gmail.com> 0.34.6-2
- Cleaned up spaces in description and added a missing infinitive
- Unified all doc files to be copied in a single docdir

* Sat Jul 18 2009 Vivek Shah <boni.vivek at gmail.com> 0.34.6-1
- Changed package name to mausezahn
- Added new README.Fedora
- Modified existing manpage

* Tue Nov 4 2008 Vivek Shah <boni.vivek at gmail.com> 0.34.5-2
- Changed binary and manpage file name to mausezahn to avoid conflicts
- Added Requires field for sample python script

* Sat Nov 1 2008 Vivek Shah <boni.vivek at gmail.com> 0.34.5-1
- Initial package


Index: .cvsignore
===================================================================
RCS file: /cvs/pkgs/rpms/mausezahn/F-10/.cvsignore,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- .cvsignore	5 Aug 2009 22:43:26 -0000	1.1
+++ .cvsignore	8 Aug 2009 16:15:47 -0000	1.2
@@ -0,0 +1 @@
+mz-0.34.9.tar.gz


Index: sources
===================================================================
RCS file: /cvs/pkgs/rpms/mausezahn/F-10/sources,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- sources	5 Aug 2009 22:43:26 -0000	1.1
+++ sources	8 Aug 2009 16:15:47 -0000	1.2
@@ -0,0 +1 @@
+17dcc41248744a14690a62bce3b637b2  mz-0.34.9.tar.gz




More information about the fedora-extras-commits mailing list