3 since version 0.38, Mausezahn supports a multi-threaded interactive mode with
4 a Cisco-style command line.
6 Try e. g. "mz -x 99" and telnet to port 99. This mode utilizes a new protocol
7 and packet management framework called MOPS (Mausezahn's Own Packet System).
8 All new features will be added to the MOPS which represents the new core
9 framework of Mausezahn.
11 If you execute Mausezahn traditionally, specifying all packet parameters as
12 arguments on the LINUX/UN*X shell, then MOPS is NOT used (libnet instead).
13 MOPS on the other hand does not need libnet anymore but creates all PDUs
14 completely by itself. This allows for a much more flexible header treatment,
15 such as an arbitrary number of MPLS headers or intentionally 'wrong' header
18 The most interesting new features introduced by MOPS are:
20 *) Nanosecond interpacket delay and overall transmission intervals (days, hours, ... )
21 *) New additional protocols: LLDP, IGMPv1 and IGMPv2, extended spanning tree
22 options (for RSTP, MSTP, PVST+)
23 *) Valid or wrong checksums on multiple layers
24 *) RTP measurement compatibility with legacy and MOPS RTP mode
25 *) Access to *all* header fields, even to those "reserved" or "must be zero"
26 *) Very flexible and user friendly QoS options (ToS, DSCP, IPP, CoS, ...) in
27 different notations (hex, dec, binary, "EF", "AF32", ...)
28 *) New 'launch' command to start often-used packet processes quickly (will be
30 *) Each packet process can be tied to another physical interface
31 *) Each physical interface can be given an arbitrary fake MAC and/or IP address.
32 *) 802.1Q and MPLS tags with all parameters can be configured easily with the
36 You can store your packet configurations in text files and load them from the
37 Mausezahn command line interface.
40 *** PLEASE send be bug reports! ***
42 Next planned features: (among many others)
44 - IPv6 support for MOPS
45 - XML-based definitions of custom protocols
46 - Graphical user interface
48 - ICMP support for MOPS