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