1 .\" netsniff-ng - the packet sniffing beast
2 .\" Copyright 2013 Herbert Haas, modified by Daniel Borkmann.
3 .\" Subject to the GPL, version 2.
4 .TH MAUSEZAHN 8 "03 March 2013" "Linux" "netsniff-ng toolkit"
6 mausezahn \- a fast versatile packet generator with Cisco-cli
10 \fBmausezahn\fR { [\fIoptions\fR] "<arg-string> | <hex-string>" }
14 mausezahn is a fast traffic generator which allows you to send nearly every
15 possible and impossible packet. In contrast to trafgen(8), mausezahn's packet
16 configuration is on a protocol-level instead of byte-level and mausezahn also
17 comes with a built-in Cisco-like command-line interface, making it suitable
18 as a network traffic generator box in your network lab.
20 Next to network labs, it can also be used as a didactical tool and for security
21 audits including penetration and DoS testing. As a traffic generator, mausezahn
22 is also able to test IP multicast or VoIP networks. Packet rates close to the
23 physical limit are reachable, depending on the hardware platform.
25 mausezahn supports two modes, ''direct mode'' and a multi-threaded ''interactive
28 The ''direct mode'' allows you to create a packet directly on the command line
29 and every packet parameter is specified in the argument list when calling
32 The ''interactive mode'' is an advanced multi-threaded configuration mode with
33 its own command line interface (CLI). This mode allows you to create an arbitrary
34 number of packet types and streams in parallel, each with different parameters.
36 The interactive mode utilizes a completely redesigned and more flexible protocol
37 framework called ''mops'' (mausezahn's own packet system). The look and feel of
38 the CLI is very close to the Cisco IOS^tm command line interface.
40 You can start the interactive mode by executing mausezahn with the ''\-x''
41 argument (an optional port number may follow, otherwise it is 25542). Then use
42 telnet(1) to connect to this mausezahn instance. If not otherwise specified,
43 the default login and password combination is mz:mz and the enable password is: mops.
44 This can be changed in /etc/netsniff-ng/mausezahn.conf.
46 The direct mode supports two specification schemes: The ''raw-layer-2'' scheme,
47 where every single byte to be sent can be specified, and ''higher-layer'' scheme,
48 where packet builder interfaces are used (using the ''\-t'' option).
50 To use the ''raw-layer-2'' scheme, simply specify the desired frame as a
51 hexadecimal sequence (the ''hex-string''), such as:
53 mausezahn eth0 "00:ab:cd:ef:00 00:00:00:00:00:01 08:00 ca:fe:ba:be"
55 In this example, whitespaces within the byte string are optional and separate
56 the Ethernet fields (destination and source address, type field, and a short
57 payload). The only additional options supported are ''\-a'', ''\-b'', ''\-c'',
58 and ''\-p''. The frame length must be greater than or equal to 15 bytes.
60 The ''higher-layer'' scheme is enabled using the ''\-t <packet-type>'' option.
61 This option activates a packet builder, and besides the ''packet-type'', an
62 optional ''arg-string'' can be specified. The ''arg-string'' contains packet-
63 specific parameters, such as TCP flags, port numbers, etc. (see example section).
67 mausezahn provides a built-in context-specific help. Append the keyword
68 ''help'' after the configuration options. The most important options
72 Start mausezahn in interactive mode with a Cisco-like CLI. Use telnet to log
73 into the local mausezahn instance. If no port has been specified, port 25542
77 Specify IPv6 mode (IPv4 is the default).
80 Specify the IP address mausezahn should bind to when in interactive mode, default: 0.0.0.0.
83 Verbose mode. Capital \-V is even more verbose.
86 Simulation mode, i.e. don't put anything on the wire. This is typically combined
87 with the verbose mode.
90 Quiet mode where only warnings and errors are displayed.
93 Send the packet count times (default: 1, infinite: 0).
96 Apply delay between transmissions. The delay value can be specified in usec
97 (default, no additional unit needed), or in msec (e.g. 100m or 100msec), or
98 in seconds (e.g. 100s or 100sec). Note: mops also supports nanosecond delay
99 resolution if you need it (see interactive mode).
102 Pad the raw frame to specified length using zero bytes. Note that for raw
103 layer 2 frames the specified length defines the whole frame length, while for
104 higher layer packets the number of additional padding bytes are specified.
106 .SS -a <src-mac|keyword>
107 Use specified source MAC address with hexadecimal notation such as 00:00:aa:bb:cc:dd.
108 By default the interface MAC address will be used. The keywords ''rand'' and ''own''
109 refer to a random MAC address (only unicast addresses are created)
110 and the own address, respectively. You can also use the keywords mentioned
111 below although broadcast-type source addresses are officially invalid.
113 .SS -b <dst-mac|keyword>
114 Use specified destination MAC address. By default, a broadcast is sent in raw
115 layer 2 mode or to the destination hosts or gateway interface MAC address in normal
116 (IP) mode. You can use the same keywords as mentioned above, as well as ''bc''
117 or ''bcast'', ''cisco'', and ''stp''.
119 .SS -A <src-ip|range|rand>
120 Use specified source IP address, default is own interface address. Optionally, the
121 keyword ''rand'' can again be used for a random source IP address or a range
122 can be specified, such as ''192.168.1.1-192.168.1.100'' or ''10.1.0.0/16''.
123 Also, a DNS name can be specified for which mausezahn tries to determine the
124 corresponding IP address automatically.
126 .SS -B <dst-ip|range>
127 Use specified destination IP address (default is broadcast i.e. 255.255.255.255).
128 As with the source address (see above) you can also specify a range or a DNS name.
130 .SS -t <packet-type [help] | help>
131 Create the specified packet type using the built-in packet builder. Currently,
132 supported packet types are: ''arp'', ''bpdu'', ''ip'', ''udp'', ''tcp'', ''rtp'',
133 and ''dns''. Currently, there is also limited support for ''icmp''. Type
134 ''\-t help'' to verify which packet builders your actual mausezahn version
135 supports. Also, for any particular packet type, for example ''tcp'' type
136 ''mausezahn \-t tcp help'' to receive a more in-depth context specific help.
139 Make this mausezahn instance the receiving station. Currently, only ''rtp'' is
140 an option here and provides precise jitter measurements. For this purpose, start
141 another mausezahn instance on the sending station and the local receiving station
142 will output jitter statistics. See ''mausezahn \-T rtp help'' for a detailed help.
144 .SS -Q <[CoS:]vlan> [, <[CoS:]vlan>, ...]
145 Specify 802.1Q VLAN tag and optional Class of Service. An arbitrary number of
146 VLAN tags can be specified (that is, you can simulate QinQ or even QinQinQinQ..).
147 Multiple tags must be separated via a comma or a period (e.g. "5:10,20,2:30").
148 VLAN tags are not supported for ARP and BPDU packets (in which case you could
149 specify the whole frame in hexadecimal using the raw layer 2 interface of mausezahn).
151 .SS -M <label[:cos[:ttl]][bos]> [, <label...>]
152 Specify a MPLS label or even a MPLS label stack. Optionally, for each label the
153 experimental bits (usually the Class of Service, CoS) and the Time To Live
154 (TTL) can be specified. If you are really crazy you can set and unset the
155 Bottom of Stack (BoS) bit for each label using the ''S'' (set) and ''s''
156 (unset) option. By default, the BoS is set automatically and correctly. Any other
157 setting will lead to invalid frames. Enter ''\-M help'' for detailed instructions
160 .SS -P <ascii-payload>
161 Specify a cleartext payload. Alternatively, each packet type supports a
162 hexadecimal specification of the payload (see for example ''\-t udp help'').
165 Read the ASCII payload from the specified file.
168 Read the hexadecimal payload from the specified file. Actually, this file must be also
169 an ASCII text file, but must contain hexadecimal digits, e.g. "aa:bb:cc:0f:e6...".
170 You can use also spaces as separation characters.
174 For more comprehensive examples, have a look at the two following HOWTO sections.
176 .SS mausezahn eth0 \-c 0 \-d 2s \-t bpdu vlan=5
177 Send BPDU frames for VLAN 5 as used with Cisco's PVST+ type of STP. By default
178 mausezahn assumes that you want to become the root bridge.
180 .SS mausezahn eth0 \-c 128000 \-a rand \-p 64
181 Perform a CAM table overflow attack.
183 .SS mausezahn eth0 \-c 0 \-Q 5,100 \-t tcp "flags=syn,dp=1-1023" \-p 20 \-A rand \-B 10.100.100.0/24
184 Perform a SYN flood attack to another VLAN using VLAN hopping. This only works
185 if you are connected to the same VLAN which is configured as native VLAN on the
186 trunk. We assume that the victim VLAN is VLAN 100 and the native VLAN is VLAN 5.
187 Lets attack every host in VLAN 100 which use an IP prefix of 10.100.100.0/24, also
188 try out all ports between 1 and 1023 and use a random source IP address.
190 .SS mausezahn eth0 \-c 0 \-d 10msec \-B 230.1.1.1 \-t udp "dp=32000,dscp=46" \-P "Multicast test packet"
191 Send IP multicast packets to the multicast group 230.1.1.1 using a UDP header
192 with destination port 32000 and set the IP DSCP field to EF (46). Send one
195 .SS mausezahn eth0 \-Q 6:420 \-M 100,200,300:5 \-A 172.30.0.0/16 \-B target.anynetwork.foo \-t udp "sp=666,dp=1-65535" \-p 1000 \-c 10
196 Send UDP packets to the destination host target.anynetwork.foo using all
197 possible destination ports and send every packet with all possible source
198 addresses of the range 172.30.0.0/16; additionally use a source port of 666
199 and three MPLS labels, 100, 200, and 300, the outer (300) with QoS field 5.
200 Send the frame with a VLAN tag 420 and CoS 6; eventually pad with 1000 bytes
201 and repeat the whole thing 10 times.
203 .SS mausezahn \-t syslog sev=3 \-P "Main reactor reached critical temperature." \-A 192.168.33.42 \-B 10.1.1.9 \-c 6 \-d 10s
204 Send six forged syslog messages with severity 3 to a Syslog server 10.1.1.9; use
205 a forged source IP address 192.168.33.42 and let mausezahn decide which local
206 interface to use. Use an inter-packet delay of 10 seconds.
208 .SS mausezahn \-t tcp "flags=syn|urg|rst, sp=145, dp=145, win=0, s=0-4294967295, ds=1500, urg=666" \-a bcast \-b bcast \-A bcast \-B 10.1.1.6 \-p 5
209 Send an invalid TCP packet with only a 5 byte payload as layer-2 broadcast and
210 also use the broadcast MAC address as source address. The target should be
211 10.1.1.6 but use a broadcast source address. The source and destination port
212 shall be 145 and the window size 0. Set the TCP flags SYN, URG, and RST
213 simultaneously and sweep through the whole TCP sequence number space with an
214 increment of 1500. Finally set the urgent pointer to 666, i.e. pointing to
217 .SH CONFIGURATION FILE
219 When mausezahn is run in interactive mode it automatically looks for and reads
220 a configuration file located at /etc/netsniff-ng/mausezahn.conf for custom options
221 if the file is available, otherwise it uses defaults set at compile time.
222 .SS Config file: /etc/netsniff-ng/mausezahn.conf
224 The configuration file contains lines of the form:
228 Options supported in the configuration file are:
231 user Username for authentication (default: mz)
232 password Password for authentication (default: mz)
233 enable Password to enter privilege mode (default: mops)
234 port The listening port for the CLI (default: 25542)
235 listen-addr IP address to bind CLI to (default: 0.0.0.0)
236 management-only Set management interface (no data traffic is allowed to pass through)
237 cli-device Interface to bind CLI to (default: all) *not fully implemented*
238 automops Path to automops file (contains XML data describing protocols) *in development*
242 $ cat /etc/netsniff-ng/mausezahn.conf
245 enable = privilege-mode-passwd
247 listen-addr = 127.0.0.1
249 .SH INTERACTIVE MODE HOWTO
253 Using the interactive mode requires starting mausezahn as a server:
257 Now you can telnet(1) to that server using the default port number 25542, but also
258 an arbitrary port number can be specified:
261 mausezahn accepts incoming telnet connections on port 99.
262 mz: Problems opening config file. Will use defaults
265 Either from another terminal or from another host try to telnet to the
268 caprica$ telnet galactica 99
269 Trying 192.168.0.4...
270 Connected to galactica.
271 Escape character is '^]'.
281 It is recommended to configure your own login credentials in
282 /etc/netsniff-ng/mausezahn.conf, (see configuration file section)
285 Since you reached the mausezahn prompt, lets try some common commands. You can
286 use the '?' character at any time for context-specific help. Note that Cisco-like
287 short form of commands are accepted in interactive mode. For example, one
288 can use "sh pac" instead of "show packet"; another common example is to use
289 "config t" in place of "configure terminal". For readability, this manual will
290 continue with the full commands.
292 First try out the show command:
296 mausezahn maintains its own ARP table and observes anomalies. There is an entry
297 for every physical interface (however this host has only one):
300 Intf Index IP address MAC address last Ch UCast BCast Info
301 ----------------------------------------------------------------------------------
302 eth0 [1] D 192.168.0.1 00:09:5b:9a:15:84 23:44:41 1 1 0 0000
304 The column Ch tells us that the announced MAC address has only changed one time
305 (= when it was learned). The columns Ucast and BCast tell us how often this
306 entry was announced via unicast or broadcast respectively.
308 Let's check our interfaces:
311 Available network interfaces:
312 real real used (fake) used (fake)
313 device IPv4 address MAC address IPv4 address MAC address
314 ---------------------------------------------------------------------------------------
315 > eth0 192.168.0.4 00:30:05:76:2e:8d 192.168.0.4 00:30:05:76:2e:8d
316 lo 127.0.0.1 00:00:00:00:00:00 127.0.0.1 00:00:00:00:00:00
318 Default interface is eth0.
320 .SS Defining packets:
322 Let's check the current packet list:
325 Packet layer flags: E=Ethernet, S=SNAP, Q=802.1Q, M=MPLS, I/i=IP/delivery_off, U=UDP, T=TCP
326 PktID PktName Layers Proto Size State Device Delay Count/CntX
327 1 sysARP_servic... E----- ARP 60 config lo 100 msec 1/0 (100%)
328 1 packets defined, 0 active.
330 We notice that there is already one system-defined packet process; it has been
331 created and used only once (during startup) by mausezahn's ARP service.
332 Currently, its state is config which means that the process is sleeping.
334 .SS General packet options:
336 Now let's create our own packet process and switch into the global
339 mz# configure terminal
341 Allocated new packet PKT0002 at slot 2
344 name Assign a unique name
345 description Assign a packet description text
346 bind Select the network interface
347 count Configure the packet count value
348 delay Configure the inter-packet delay
349 interval Configure a greater interval
350 type Specify packet type
351 mac Configure packet's MAC addresses
353 payload Configure a payload
354 port Configure packet's port numbers
355 end End packet configuration mode
356 ethernet Configure frame's Ethernet, 802.2, 802.3, or SNAP settings
357 ip Configure packet's IP settings
358 udp Configure packet's UDP header parameters
359 tcp Configure packet's TCP header parameters
361 Here are a lot of options but normally you only need a few of them. When you
362 configure lots of different packets you might assign a reasonable name and
363 description for them:
365 mz(config-pkt-2)# name Test
366 mz(config-pkt-2)# description This is just a test
368 You can, for example, change the default settings for the source and destination MAC or IP
369 addresses using the mac and ip commands:
371 mz(config-pkt-2)# ip address destination 10.1.1.0 /24
372 mz(config-pkt-2)# ip address source random
374 In the example above, we configured a range of addresses (all hosts in the
375 network 10.1.1.0 should be addressed). Additionally we spoof our source IP
376 address. Of course, we can also add one or more VLAN and, or, MPLS tag(s):
378 mz(config-pkt-2)# tag ?
379 dot1q Configure 802.1Q (and 802.1P) parameters
380 mpls Configure MPLS label stack
381 mz(config-pkt-2)# tag dot ?
382 Configure 802.1Q tags:
383 VLAN[:CoS] [VLAN[:CoS]] ... The leftmost tag is the outer tag in the frame
384 remove <tag-nr> | all Remove one or more tags (<tag-nr> starts with 1),
385 by default the first (=leftmost,outer) tag is removed,
386 keyword 'all' can be used instead of tag numbers.
387 cfi | nocfi [<tag-nr>] Set or unset the CFI-bit in any tag (by default
388 assuming the first tag).
389 mz(config-pkt-2)# tag dot 1:7 200:5
391 .SS Configure count and delay:
393 mz(config-pkt-2)# count 1000
394 mz(config-pkt-2)# delay ?
395 delay <value> [hour | min | sec | msec | usec | nsec]
397 Specify the inter-packet delay in hours, minutes, seconds, milliseconds,
398 microseconds or nanoseconds. The default unit is milliseconds (i.e. when no
401 mz(config-pkt-2)# delay 1 msec
402 Inter-packet delay set to 0 sec and 1000000 nsec
405 .SS Configuring protocol types:
407 mausezahn's interactive mode supports a growing list of protocols and only
408 relies on the MOPS architecture (and not on libnet as is the case with
409 the legacy direct mode):
411 mz(config-pkt-2)# type
412 Specify a packet type from the following list:
420 mz(config-pkt-2)# type tcp
421 mz(config-pkt-2-tcp)#
423 seqnr Configure the TCP sequence number
424 acknr Configure the TCP acknowledgement number
425 hlen Configure the TCP header length
426 reserved Configure the TCP reserved field
427 flags Configure a combination of TCP flags at once
428 cwr Set or unset the TCP CWR flag
429 ece Set or unset the TCP ECE flag
430 urg Set or unset the TCP URG flag
431 ack set or unset the TCP ACK flag
432 psh set or unset the TCP PSH flag
433 rst set or unset the TCP RST flag
434 syn set or unset the TCP SYN flag
435 fin set or unset the TCP FIN flag
436 window Configure the TCP window size
437 checksum Configure the TCP checksum
438 urgent-pointer Configure the TCP urgent pointer
439 options Configure TCP options
440 end End TCP configuration mode
441 mz(config-pkt-2-tcp)# flags syn fin rst
442 Current setting is: --------------------RST-SYN-FIN
443 mz(config-pkt-2-tcp)# end
444 mz(config-pkt-2)# payload ascii This is a dummy payload for my first packet
445 mz(config-pkt-2)# end
447 Now configure another packet, for example let's assume we want an LLDP process:
450 Allocated new packet PKT0003 at slot 3
451 mz(config-pkt-3)# type lldp
452 mz(config-pkt-3-lldp)# exit
455 In the above example we only use the default LLDP settings and don't configure
456 further LLDP options or TLVs. Back in the top level of the CLI let's verify
460 Packet layer flags: E=Ethernet, S=SNAP, Q=802.1Q, M=MPLS, I/i=IP/delivery_off, U=UDP, T=TCP
461 PktID PktName Layers Proto Size State Device Delay Count/CntX
462 1 sysARP_servic... E----- ARP 60 config lo 100 msec 1/0 (100%)
463 2 Test E-Q-IT 125 config eth0 1000 usec 1000/1000 (0%)
464 3 PKT0003 E----- LLDP 36 config eth0 30 sec 0/0 (0%)
465 3 packets defined, 0 active.
467 The column Layers indicates which major protocols have been combined. For
468 example the packet with packet-id 2 ("Test") utilizes Ethernet (E),
469 IP (I), and TCP (T). Additionally an 802.1Q tag (Q) has been inserted. Now
470 start one of these packet processes:
475 Packet layer flags: E=Ethernet, S=SNAP, Q=802.1Q, M=MPLS, I/i=IP/delivery_off, U=UDP, T=TCP
476 PktID PktName Layers Proto Size State Device Delay Count/CntX
477 1 sysARP_servic... E----- ARP 60 config lo 100 msec 1/0 (100%)
478 2 Test E-Q-IT 125 config eth0 1000 usec 1000/1000 (0%)
479 3 PKT0003 E----- LLDP 36 config eth0 30 sec 0/1 (0%)
480 3 packets defined, 1 active.
482 Let's have a more detailed look at a specific packet process:
486 Description: This is just a test
487 State: config, Count=1000, delay=1000 usec (0 s 1000000 nsec), interval= (undefined)
489 Ethernet: 00-30-05-76-2e-8d => ff-ff-ff-ff-ff-ff [0800 after 802.1Q tag]
490 Auto-delivery is ON (that is, the actual MAC is adapted upon transmission)
491 802.1Q: 0 tag(s); (VLAN:CoS)
492 IP: SA=192.168.0.4 (not random) (no range)
493 DA=255.255.255.255 (no range)
494 ToS=0x00 proto=17 TTL=255 ID=0 offset=0 flags: -|-|-
495 len=49664(correct) checksum=0x2e8d(correct)
496 TCP: 83 bytes segment size (including TCP header)
497 SP=0 (norange) (not random), DP=0 (norange) (not random)
498 SQNR=3405691582 (start 0, stop 4294967295, delta 0) -- ACKNR=0 (invalid)
499 Flags: ------------------------SYN----, reserved field is 00, urgent pointer= 0
500 Announced window size= 100
501 Offset= 0 (times 32 bit; value is valid), checksum= ffff (valid)
502 (No TCP options attached) - 0 bytes defined
503 Payload size: 43 bytes
504 Frame size: 125 bytes
505 1 ff:ff:ff:ff:ff:ff:00:30 05:76:2e:8d:81:00:e0:01 81:00:a0:c8:08:00:45:00 00:67:00:00:00:00:ff:06
506 33 fa:e4:c0:a8:00:04:ff:ff ff:ff:00:00:00:00:ca:fe ba:be:00:00:00:00:a0:07 00:64:f7:ab:00:00:02:04
507 65 05:ac:04:02:08:0a:19:35 90:c3:00:00:00:00:01:03 03:05:54:68:69:73:20:69 73:20:61:20:64:75:6d:6d
508 97 79:20:70:61:79:6c:6f:61 64:20:66:6f:72:20:6d:79 20:66:69:72:73:74:20:70 61:63:6b:65:74
511 If you want to stop one or more packet processes, use the stop command. The
512 "emergency stop" is when you use stop all:
517 Stopped 1 transmission processe(s)
519 The launch command provides a shortcut for commonly used packet processes. For
520 example to behave like a STP-capable bridge we want to start an BPDU process
521 with typical parameters:
524 Allocated new packet sysBPDU at slot 5
526 Packet layer flags: E=Ethernet, S=SNAP, Q=802.1Q, M=MPLS, I/i=IP/delivery_off, U=UDP, T=TCP
527 PktID PktName Layers Proto Size State Device Delay Count/CntX
528 1 sysARP_servic... E----- ARP 60 config lo 100 msec 1/0 (100%)
529 2 Test E-Q-IT 125 config eth0 1000 usec 1000/1000 (0%)
530 3 PKT0003 E----- LLDP 36 config eth0 30 sec 0/12 (0%)
531 4 PKT0004 E---I- IGMP 46 config eth0 100 msec 0/0 (0%)
532 5 sysBPDU ES---- BPDU 29 active eth0 2 sec 0/1 (0%)
533 5 packets defined, 1 active.
535 Now a Configuration BPDU is sent every 2 seconds, claiming to be the root
536 bridge (and usually confusing the LAN. Note that only packet 5 (i.e. the
537 last row) is active and therefore sending packets while all other packets
538 are in state config (i.e. they have been configured but they are not doing
539 anything at the moment).
541 .SS Configuring a greater interval:
543 Sometimes you may want to send a burst of packets at a greater interval:
546 Modify packet parameters for packet Test [2]
547 mz(config-pkt-2)# interval
548 Configure a greater packet interval in days, hours, minutes, or seconds
549 Arguments: <value> <days | hours | minutes | seconds>
550 Use a zero value to disable an interval.
551 mz(config-pkt-2)# interval 1 hour
552 mz(config-pkt-2)# count 10
553 mz(config-pkt-2)# delay 15 usec
554 Inter-packet delay set to 0 sec and 15000 nsec
556 Now this packet is sent ten times with an inter-packet delay of 15 microseconds
557 and this is repeated every hour. When you look at the packet list, an interval
558 is indicated with the additional flag 'i' when inactive or 'I' when active:
561 Packet layer flags: E=Ethernet, S=SNAP, Q=802.1Q, M=MPLS, I/i=IP/delivery_off, U=UDP, T=TCP
562 PktID PktName Layers Proto Size State Device Delay Count/CntX
563 1 sysARP_servic... E----- ARP 60 config lo 100 msec 1/0 (100%)
564 2 Test E-Q-IT 125 config-i eth0 15 usec 10/10 (0%)
565 3 PKT0003 E----- LLDP 36 config eth0 30 sec 0/12 (0%)
566 4 PKT0004 E---I- IGMP 46 config eth0 100 msec 0/0 (0%)
567 5 sysBPDU ES---- BPDU 29 active eth0 2 sec 0/251 (0%)
568 5 packets defined, 1 active.
572 Packet layer flags: E=Ethernet, S=SNAP, Q=802.1Q, M=MPLS, I/i=IP/delivery_off, U=UDP, T=TCP
573 PktID PktName Layers Proto Size State Device Delay Count/CntX
574 1 sysARP_servic... E----- ARP 60 config lo 100 msec 1/0 (100%)
575 2 Test E-Q-IT 125 config+I eth0 15 usec 10/0 (100%)
576 3 PKT0003 E----- LLDP 36 config eth0 30 sec 0/12 (0%)
577 4 PKT0004 E---I- IGMP 46 config eth0 100 msec 0/0 (0%)
578 5 sysBPDU ES---- BPDU 29 active eth0 2 sec 0/256 (0%)
579 5 packets defined, 1 active.
581 Note that the flag 'I' indicates that an interval has been specified for
582 packet 2. The process is not active at the moment (only packet 5 is active
583 here) but it will become active at a regular interval. You can verify the
584 actual interval when viewing the packet details via the 'show packet 2' command.
586 .SS Load prepared configurations:
588 You can prepare packet configurations using the same commands as you would
589 type them in on the CLI and then load them to the CLI. For example, assume we
590 have prepared a file 'test.mops' containing:
595 desc This is only a demonstration how to load a file to mops
598 Then we can add this packet configuration to our packet list using the load
602 Read commands from test.mops...
603 Allocated new packet PKT0002 at slot 2
605 Packet layer flags: E=Ethernet, S=SNAP, Q=802.1Q, M=MPLS, I/i=IP/delivery_off, U=UDP, T=TCP
606 PktID PktName Layers Proto Size State Device Delay Count/CntX
607 1 sysARP_servic... E----- ARP 60 config lo 100 msec 1/0 (100%)
608 2 IGMP_TEST E---I- IGMP 46 config eth0 100 msec 0/0 (0%)
609 2 packets defined, 0 active.
611 The file src/examples/mausezahn/example_lldp.conf contains another example
612 list of commands to create a bogus LLDP packet. You can load this
613 configuration from the mausezahn command line as follows:
615 mz# load /home/hh/tmp/example_lldp.conf
617 In case you copied the file in that path. Now when you enter 'show packet' you
618 will see a new packet entry in the packet list. Use the 'start slot <nr>'
619 command to activate this packet.
621 You can store your own packet creations in such a file and easily load them when
622 you need them. Every command within such configuration files is executed on the
623 command line interface as if you had typed it in -- so be careful about the
624 order and don't forget to use 'configure terminal' as first command.
626 You can even load other files from within a central config file.
628 .SH DIRECT MODE HOWTO
630 .SS How to specify hexadecimal digits:
632 Many arguments allow direct byte input. Bytes are represented as two
633 hexadecimal digits. Multiple bytes must be separated either by spaces, colons,
634 or dashes - whichever you prefer. The following byte strings are equivalent:
636 "aa:bb cc-dd-ee ff 01 02 03-04 05"
637 "aa bb cc dd ee ff:01:02:03:04 05"
639 To begin with, you may want to send an arbitrary fancy (possibly invalid)
640 frame right through your network card:
642 mausezahn ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:08:00:ca:fe:ba:be
644 or equivalent but more readable:
646 mausezahn ff:ff:ff:ff:ff:ff-ff:ff:ff:ff:ff:ff-08:00-ca:fe:ba:be
648 .SS Basic operations:
650 All major command line options are listed when you execute mausezahn without
651 arguments. For practical usage, keep the following special (not so widely
652 known) options in mind:
654 \-r Multiplies the specified delay with a random value.
655 \-p <length> Pad the raw frame to specified length (using random bytes).
656 \-P <ASCII Payload> Use the specified ASCII payload.
657 \-f <filename> Read the ASCII payload from a file.
658 \-F <filename> Read the hexadecimal payload from a file.
659 \-S Simulation mode: DOES NOT put anything on the wire.
660 This is typically combined with one of the verbose
663 Many options require a keyword or a number but the \-t option is an exception
664 since it requires both a packet type (such as ip, udp, dns, etc) and an
665 argument string which is specific for that packet type. Here are some simple
669 mausezahn \-t tcp help
670 mausezahn eth3 \-t udp sp=69,dp=69,p=ca:fe:ba:be
672 Note: Don't forget that on the CLI the Linux shell (usually the Bash)
673 interprets spaces as a delimiting character. That is, if you are specifying
674 an argument that consists of multiple words with spaces in between, you MUST
675 group these within quotes. For example, instead of
677 mausezahn eth0 \-t udp sp=1,dp=80,p=00:11:22:33
679 you could either omit the spaces
681 mausezahn eth0 \-t udp sp=1,dp=80,p=00:11:22:33
683 or, for greater safety, use quotes:
685 mausezahn eth0 \-t udp "sp=1,dp=80,p=00:11:22:33"
687 In order to monitor what's going on, you can enable the verbose mode using
688 the \-v option. The opposite is the quiet mode (\-q) which will keep mausezahn
689 absolutely quiet (except for error messages and warnings.)
691 Don't confuse the payload argument p=... with the padding option \-p. The latter
692 is used outside the quotes!
694 .SS The automatic packet builder:
696 An important argument is \-t which invokes a packet builder. Currently there
697 are packet builders for ARP, BPDU, CDP, IP, partly ICMP, UDP, TCP, RTP, DNS,
698 and SYSLOG. (Additionally you can insert a VLAN tag or a MPLS label stack but
699 this works independently of the packet builder.)
701 You get context specific help for every packet builder using the help keyword,
704 mausezahn \-t bpdu help
705 mausezahn \-t tcp help
707 For every packet you may specify an optional payload. This can be done either
708 via hexadecimal notation using the payload (or short p) argument or directly as ASCII
709 text using the \-P option:
711 mausezahn eth0 \-t ip \-P "Hello World" # ASCII payload
712 mausezahn eth0 \-t ip p=68:65:6c:6c:6f:20:77:6f:72:6c:64 # hex payload
713 mausezahn eth0 \-t ip "proto=89, \\
714 p=68:65:6c:6c:6f:20:77:6f:72:6c:64, \\ # same with other
715 ttl=1" # IP arguments
717 Note: The raw link access mode only accepts hexadecimal payloads (because you specify
718 everything in hexadecimal here.)
720 .SS Packet count and delay:
722 By default only one packet is sent. If you want to send more packets then
723 use the count option \-c <count>. When count is zero then mausezahn will send
724 forever. By default, mausezahn sends at maximum speed (and this is really
725 fast ;-)). If you don't want to overwhelm your network devices or have other
726 reasons to send at a slower rate then you might want to specify a delay using
727 the \-d <delay> option.
729 If you only specify a numeric value it is interpreted in microsecond units.
730 Alternatively, for easier use, you might specify units such as seconds, sec,
731 milliseconds, or msec. (You can also abbreviate this with s or m.)
732 Note: Don't use spaces between the value and the unit! Here are typical examples:
734 Send an infinite number of frames as fast as possible:
736 mausezahn \-c 0 "aa bb cc dd ...."
738 Send 100,000 frames with a 50 msec interval:
740 mausezahn \-c 100000 \-d 50msec "aa bb cc dd ...."
742 Send an unlimited number of BPDU frames in a 2 second interval:
744 mausezahn \-c 0 \-d 2s \-t bpdu conf
746 Note: mausezahn does not support fractional numbers. If you want to specify for
747 example 2.5 seconds then express this in milliseconds (2500 msec).
749 .SS Source and destination addresses:
751 As a mnemonic trick keep in mind that all packets run from "A" to "B". You can
752 always specify source and destination MAC addresses using the \-a and \-b
753 options, respectively. These options also allow keywords such as rand, own,
754 bpdu, cisco, and others.
756 Similarly, you can specify source and destination IP addresses using the \-A
757 and \-B options, respectively. These options also support FQDNs (i.e. domain
758 names) and ranges such as 192.168.0.0/24 or 10.0.0.11-10.0.3.22. Additionally,
759 the source address option supports the rand keyword (ideal for "attacks").
761 Note: When you use the packet builder for IP-based packets (e.g. UDP or TCP)
762 then mausezahn automatically cares about correct MAC and IP addresses (i.e.
763 it performs ARP, DHCP, and DNS for you). But when you specify at least a single
764 link-layer address (or any other L2 option such as a VLAN tag or MPLS header)
765 then ARP is disabled and you must care for the Ethernet destination address for
770 .SS `-- Direct link access:
772 mausezahn allows you to send ANY chain of bytes directly through your Ethernet
775 mausezahn eth0 "ff:ff:ff:ff:ff:ff ff:ff:ff:ff:ff:ff 00:00 ca:fe:ba:be"
777 This way you can craft every packet you want but you must do it by hand. Note:
778 On Wi-Fi interfaces the header is much more complicated and automatically
779 created by the Wi-Fi driver. As an example to introduce some interesting options,
780 lets continuously send frames at max speed with random source MAC address and
781 broadcast destination address, additionally pad the frame to 1000 bytes:
783 mausezahn eth0 \-c 0 \-a rand \-b bcast \-p 1000 "08 00 aa bb cc dd"
785 The direct link access supports automatic padding using the \-p <total frame
786 length> option. This allows you to pad a raw L2 frame to the desired length.
787 You must specify the total length, and the total frame length must have at
788 least 15 bytes for technical reasons. Zero bytes are used for padding.
792 mausezahn provides a simple interface to the ARP packet. You can specify the
793 ARP method (request|reply) and up to four arguments: sendermac, targetmac,
794 senderip, targetip, or short smac, tmac, sip, tip. By default, an ARP reply is
795 sent with your own interface addresses as source MAC and IP address, and a
796 broadcast destination MAC and IP address. Send a gratuitous ARP request (as used for
797 duplicate IP address detection):
799 mausezahn eth0 \-t arp
803 mausezahn eth0 \-t arp "reply, senderip=192.168.0.1, targetmac=00:00:0c:01:02:03, \\
804 targetip=172.16.1.50"
806 where by default your interface MAC address will be used as sendermac,
807 senderip denotes the spoofed IP address, targetmac and targetip identifies the
808 receiver. By default, the Ethernet source address is your interface MAC and the
809 destination address is the broadcast address. You can change this
810 using the flags \-a and \-b.
814 mausezahn provides a simple interface to the 802.1D BPDU frame format (used to
815 create the Spanning Tree in bridged networks). By default, standard IEEE 802.1D
816 BPDUs are sent and it is assumed that your computer wants to become the
817 root bridge (rid=bid). Optionally the 802.3 destination address can be a
818 specified MAC address, broadcast, own MAC, or Cisco's PVST+ MAC address. The
819 destination MAC can be specified using the \-b command which, besides MAC
820 addresses, accepts keywords such as bcast, own, pvst, or stp (default). PVST+
821 is supported as well. Simply specify the VLAN for which you want to send a BPDU:
823 mausezahn eth0 \-t bpdu "vlan=123, rid=2000"
825 See mausezahn \-t bpdu help for more details.
829 mausezahn can send Cisco Discovery Protocol (CDP) messages since this protocol
830 has security relevance. Of course lots of dirty tricks are possible; for
831 example arbitrary TLVs can be created (using the hex-payload argument for
832 example p=00:0e:00:07:01:01:90) and if you want to stress the CDP database of
833 some device, mausezahn can send each CDP message with another system-id using
836 mausezahn \-t cdp change \-c 0
838 Some routers and switches may run into deep problems ;-) See
839 mausezahn \-t cdp help for more details.
841 .SS `-- 802.1Q VLAN Tags:
843 mausezahn allows simple VLAN tagging for IP (and other higher layer) packets.
844 Simply use the option \-Q <[CoS:]VLAN>, such as \-Q 10 or \-Q 3:921. By
845 default CoS=0. For example send a TCP packet in VLAN 500 using CoS=7:
847 mausezahn eth0 \-t tcp \-Q 7:500 "dp=80, flags=rst, p=aa:aa:aa"
849 You can create as many VLAN tags as you want! This is interesting to create
850 QinQ encapsulations or VLAN hopping: Send a UDP packet with VLAN tags 100
851 (outer) and 651 (inner):
853 mausezahn eth0 \-t udp "dp=8888, sp=13442" \-P "Mausezahn is great" \-Q 100,651
855 Don't know if this is useful anywhere but at least it is possible:
857 mausezahn eth0 \-t udp "dp=8888, sp=13442" \-P "Mausezahn is great" \\
858 \-Q 6:5,7:732,5:331,5,6
862 mausezahn eth0 \-t udp "dp=8888, sp=13442" \-P "Mausezahn is great" \-Q 100,651 \-M 314
864 When in raw Layer 2 mode you must create the VLAN tag completely by yourself.
865 For example if you want to send a frame in VLAN 5 using CoS 0 simply specify
866 81:00 as type field and for the next two bytes the CoS (PCP), DEI (CFI), and
867 VLAN ID values (all together known as TCI):
869 mausezahn eth0 \-b bc \-a rand "81:00 00:05 08:00 aa-aa-aa-aa-aa-aa-aa-aa-aa"
873 mausezahn allows you to insert one or more MPLS headers. Simply use the option
874 \-M <label:CoS:TTL:BoS> where only the label is mandatory. If you specify a
875 second number it is interpreted as the experimental bits (the CoS usually). If
876 you specify a third number it is interpreted as TTL. By default the TTL is
877 set to 255. The Bottom of Stack flag is set automatically, otherwise the frame
878 would be invalid, but if you want you can also set or unset it using the
879 S (set) and s (unset) argument. Note that the BoS must be the last argument in
880 each MPLS header definition. Here are some examples:
884 mausezahn eth0 \-M 214 \-t tcp "dp=80" \-P "HTTP..." \-B myhost.com
886 Use three labels (the 214 is now the outer):
888 mausezahn eth0 \-M 9999,51,214 \-t tcp "dp=80" \-P "HTTP..." \-B myhost.com
890 Use two labels, one with CoS=5 and TTL=1, the other with CoS=7:
892 mausezahn eth0 \-M 100:5:1,500:7 \-t tcp "dp=80" \-P "HTTP..." \-B myhost.com
894 Unset the BoS flag (which will result in an invalid frame):
896 mausezahn eth0 \-M 214:s \-t tcp "dp=80" \-P "HTTP..." \-B myhost.com
900 IP, UDP, and TCP packets can be padded using the \-p option. Currently 0x42 is
901 used as padding byte ('the answer'). You cannot pad DNS packets (would be
906 mausezahn allows you to send any malformed or correct IP packet. Every field
907 in the IP header can be manipulated. The IP addresses can be specified via
908 the \-A and \-B options, denoting the source and destination address,
909 respectively. You can also specify an address range or a host name (FQDN).
910 Additionally, the source address can also be random. By default the source
911 address is your interface IP address and the destination address is a
912 broadcast address. Here are some examples:
916 mausezahn eth0 \-t ip \-A rand \-B 192.168.1.0/24 \-P "hello world"
920 mausezahn eth0 \-t ip \-A 10.1.0.1-10.1.255.254 \-B 255.255.255.255 p=ca:fe:ba:be
922 Will use correct source IP address:
924 mausezahn eth0 \-t ip \-B www.xyz.com
926 The Type of Service (ToS) byte can either be specified directly by two
927 hexadecimal digits, which means you can also easily set the Explicit
928 Congestion Notification (ECN) bits (LSB 1 and 2), or you may only want to
929 specify a common DSCP value (bits 3-8) using a decimal number (0..63):
931 Packet sent with DSCP = Expedited Forwarding (EF):
933 mausezahn eth0 \-t ip dscp=46,ttl=1,proto=1,p=08:00:5a:a2:de:ad:be:af
935 If you leave the checksum as zero (or unspecified) the correct checksum will
936 be automatically computed. Note that you can only use a wrong checksum when
937 you also specify at least one L2 field manually.
941 mausezahn supports easy UDP datagram generation. Simply specify the
942 destination address (\-B option) and optionally an arbitrary source address
943 (\-A option) and as arguments you may specify the port numbers using the
944 dp (destination port) and sp (source port) arguments and a payload. You can
945 also easily specify a whole port range which will result in sending multiple
946 packets. Here are some examples:
948 Send test packets to the RTP port range:
950 mausezahn eth0 \-B 192.168.1.1 \-t udp "dp=16384-32767, \\
951 p=A1:00:CC:00:00:AB:CD:EE:EE:DD:DD:00"
953 Send a DNS request as local broadcast (often a local router replies):
955 mausezahn eth0 \-t udp dp=53,p=c5-2f-01-00-00-01-00-00-00-00-00-00-03-77-77-\\
956 77-03-78-79-7a-03-63-6f-6d-00-00-01-00-01"
958 Additionally you may specify the length and checksum using the len and sum
959 arguments (will be set correctly by default). Note: several protocols have same
960 arguments such as len (length) and sum (checksum). If you specified a UDP type
961 packet (via \-t udp) and want to modify the IP length, then use the alternate
962 keyword iplen and ipsum. Also note that you must specify at least one L2 field
963 which tells mausezahn to build everything without the help of your kernel (the
964 kernel would not allow modifying the IP checksum and the IP length).
968 mausezahn currently only supports the following ICMP methods: PING (echo
969 request), Redirect (various types), Unreachable (various types). Additional
970 ICMP types will be supported in future. Currently you would need to tailor them
971 by yourself, e.g. using the IP packet builder (setting proto=1). Use the
972 mausezahn \-t icmp help for help on currently implemented options.
976 mausezahn allows you to easily tailor any TCP packet. Similarly as with UDP you
977 can specify source and destination port (ranges) using the sp and dp arguments.
978 Then you can directly specify the desired flags using an "|" as delimiter if
979 you want to specify multiple flags. For example, a SYN-Flood attack against
980 host 1.1.1.1 using a random source IP address and periodically using all 1023
981 well-known ports could be created via:
983 mausezahn eth0 \-A rand \-B 1.1.1.1 \-c 0 \-t tcp "dp=1-1023, flags=syn" \\
984 \-P "Good morning! This is a SYN Flood Attack. \\
985 We apologize for any inconvenience."
987 Be careful with such SYN floods and only use them for firewall testing. Check
988 your legal position! Remember that a host with an open TCP session only accepts
989 packets with correct socket information (addresses and ports) and a valid TCP
990 sequence number (SQNR). If you want to try a DoS attack by sending a RST-flood
991 and you do NOT know the target's initial SQNR (which is normally the case) then
992 you may want to sweep through a range of sequence numbers:
994 mausezahn eth0 \-A legal.host.com \-B target.host.com \\
995 \-t tcp "sp=80,dp=80,s=1-4294967295"
997 Fortunately, the SQNR must match the target host's acknowledgement number plus
998 the announced window size. Since the typical window size is something between
999 40000 and 65535 you are MUCH quicker when using an increment via the ds argument:
1001 mausezahn eth0 \-A legal.host.com \-B target.host.com \\
1002 \-t tcp "sp=80, dp=80, s=1-4294967295, ds=40000"
1004 In the latter case mausezahn will only send 107375 packets instead of
1005 4294967295 (which results in a duration of approximately 1 second compared to
1006 11 hours!). Of course you can tailor any TCP packet you like. As with other L4
1007 protocols mausezahn builds a correct IP header but you can additionally access
1008 every field in the IP packet (also in the Ethernet frame).
1012 mausezahn supports UDP-based DNS requests or responses. Typically you may want
1013 to send a query or an answer. As usual, you can modify every flag in the header.
1014 Here is an example of a simple query:
1016 mausezahn eth0 \-B mydns-server.com \-t dns "q=www.ibm.com"
1018 You can also create server-type messages:
1020 mausezahn eth0 \-A spoofed.dns-server.com \-B target.host.com \\
1021 "q=www.topsecret.com, a=172.16.1.1"
1023 The syntax according to the online help (\-t dns help) is:
1025 query|q = <name>[:<type>] ............. where type is per default "A"
1026 (and class is always "IN")
1027 answer|a = [<type>:<ttl>:]<rdata> ...... ttl is per default 0.
1028 = [<type>:<ttl>:]<rdata>/[<type>:<ttl>:]<rdata>/...
1030 Note: If you only use the 'query' option then a query is sent. If you
1031 additionally add an 'answer' then an answer is sent. Examples:
1034 q = www.xyz.com, a=192.168.1.10
1035 q = www.xyz.com, a=A:3600:192.168.1.10
1036 q = www.xyz.com, a=CNAME:3600:abc.com/A:3600:192.168.1.10
1038 Please try out mausezahn \-t dns help to see the many other optional command
1041 .SS `-- RTP and VoIP path measurements:
1043 mausezahn can send arbitrary Real Time Protocol (RTP) packets. By default a
1044 classical G.711 codec packet of 20 ms segment size and 160 bytes is assumed. You
1045 can measure jitter, packet loss, and reordering along a path between two hosts
1046 running mausezahn. The jitter measurement is either done following the variance
1047 low-pass filtered estimation specified in RFC 3550 or using an alternative
1048 "real-time" method which is even more precise (the RFC-method is used by
1049 default). For example on Host1 you start a transmission process:
1051 mausezahn \-t rtp \-B 192.168.1.19
1053 And on Host2 (192.168.1.19) a receiving process which performs the measurement:
1057 Note that the option flag with the capital "T" means that it is a server RTP
1058 process, waiting for incoming RTP packets from any mausezahn source. In case
1059 you want to restrict the measurement to a specific source or you want to
1060 perform a bidirectional measurement, you must specify a stream identifier.
1061 Here is an example for bidirectional measurements which logs the running
1062 jitter average in a file:
1064 Host1# mausezahn \-t rtp id=11:11:11:11 \-B 192.168.2.2 &
1065 Host1# mausezahn \-T rtp id=22:22:22:22 "log, path=/tmp/mz/"
1067 Host2# mausezahn \-t rtp id=22:22:22:22 \-B 192.168.1.1 &
1068 Host2# mausezahn \-T rtp id=11:11:11:11 "log, path=/tmp/mz/"
1070 In any case the measurements are printed continuously onto the screen; by
1071 default it looks like this:
1074 |-------------------------|-------------------------|-------------------------|
1076 #################### 0.14 msec
1082 ############# 0.10 msec
1084 ########################################### 0.31 msec
1086 ############################################## 0.33 msec
1087 ############### 0.11 msec
1088 ########## 0.07 msec
1089 ############### 0.11 msec
1090 ########################################################## 0.42 msec
1093 More information is shown using the txt keyword:
1095 mausezahn \-T rtp txt
1096 Got 100 packets from host 192.168.0.3: 0 lost (0 absolute lost), 1 out of order
1097 Jitter_RFC (low pass filtered) = 30 usec
1098 Samples jitter (min/avg/max) = 1/186/2527 usec
1099 Delta-RX (min/avg/max) = 2010/20167/24805 usec
1100 Got 100 packets from host 192.168.0.3: 0 lost (0 absolute lost), 1 out of order
1101 Jitter_RFC (low pass filtered) = 17 usec
1102 Samples jitter (min/avg/max) = 1/53/192 usec
1103 Delta-RX (min/avg/max) = 20001/20376/20574 usec
1104 Got 100 packets from host 192.168.0.3: 0 lost (0 absolute lost), 1 out of order
1105 Jitter_RFC (low pass filtered) = 120 usec
1106 Samples jitter (min/avg/max) = 0/91/1683 usec
1107 Delta-RX (min/avg/max) = 18673/20378/24822 usec
1109 See mausezahn \-t rtp help and mz \-T rtp help for more details.
1113 The traditional Syslog protocol is widely used even in professional networks
1114 and is sometimes vulnerable. For example you might insert forged Syslog
1115 messages by spoofing your source address (e.g. impersonate the address of a
1116 legit network device):
1118 mausezahn \-t syslog sev=3 \-P "You have been mausezahned." \-A 10.1.1.109 \-B 192.168.7.7
1120 See mausezahn \-t syslog help for more details.
1124 When multiple ranges are specified, e.g. destination port ranges and
1125 destination address ranges, then all possible combinations of ports and
1126 addresses are used for packet generation. Furthermore, this can be mixed with
1127 other ranges e.g. a TCP sequence number range. Note that combining ranges
1128 can lead to a very huge number of frames to be sent. As a rule of thumb you
1129 can assume that about 100,000 frames and more are sent in a fraction of one
1130 second, depending on your network interface.
1132 mausezahn has been designed as a fast traffic generator so you might easily
1133 overwhelm a LAN segment with myriads of packets. And because mausezahn could
1134 also support security audits it is possible to create malicious or invalid
1135 packets, SYN floods, port and address sweeps, DNS and ARP poisoning, etc.
1137 Therefore, don't use this tool when you are not aware of the possible
1138 consequences or have only a little knowledge about networks and data
1139 communication. If you abuse mausezahn for 'unallowed' attacks and get caught,
1140 or damage something of your own, then this is completely your fault. So the
1141 safest solution is to try it out in a lab environment.
1143 Also have a look at the netsniff-ng(8) note section on how you can properly
1144 setup and tune your system.
1147 mausezahn is licensed under the GNU GPL version 2.0.
1151 was originally written by Herbert Haas. According to his website [1], he
1152 unfortunately passed away in 2011 thus leaving this tool unmaintained.
1153 It has been adopted and integrated into the netsniff-ng toolkit and is further
1154 being maintained and developed from there. Maintainers are Tobias Klauser
1155 <tklauser@distanz.ch> and Daniel Borkmann <dborkma@tik.ee.ethz.ch>.
1157 [1] http://www.perihel.at/
1160 .BR netsniff-ng (8),
1165 .BR astraceroute (8),
1169 Manpage was written by Herbert Haas and modified by Daniel Borkmann.
1172 This page is part of the Linux netsniff-ng toolkit project. A description of the project,
1173 and information about reporting bugs, can be found at http://netsniff-ng.org/.