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