Mausezahn is a fast traffic generator which allows you to send nearly every possible and impossible packet. Mausezahn can be used, for example, as a traffic generator to stress multicast networks, for penetration testing of firewalls and IDS, for simulating DoS attacks on networks, to find bugs in network software or appliances, for reconnaissance attacks using ping sweeps and port scans, or to test network behavior under strange circumstances. Mausezahn gives you full control over the network interface card and allows you to send any byte stream you want (even violating Ethernet rules).
|Operating Systems||POSIX Linux|
I assume this version is more stable and the the packet sequence feature will be widely appreciated. Next I plan to migrate the direct mode to MOPS (Mausezahn's Own Packet System) to let the direct mode immediately benefit from the interactive mode MOPS features. During summer following releases are planned.
Release Notes: Configured packets can now be grouped to 'packet sequences'. IP auto-fragmentation is now supported in interactive mode. Jitter measurements now uses the SSRC option consistently to distinguish different RTP streams. PVST+ and the Loose Source Route IP option works now correctly. There are many bugfixes.
Release Notes: This release adds better RTP support, fixes the nasty CPU consumption bug which occurred on systems with a recent libpcap-dev, improves RTP jitter measurement, and updates the documentation. All users should upgrade to this release for security and stability reasons.
Release Notes: Mausezahn now supports a multi-threaded mode with a Cisco-style command line and incorporating Mausezahn's Own Packet System (MOPS). Basic support for IGMP (v1, v2) was added with querier and client mode. Basic LLDP support was added, also with 'bad' TLV creation. Also added were multi-device support, support for nanosecond inter-packet delays (MOPS), an ARP observation service, improved IP range configuration in legacy code, and support for independent measurements of concurrent RTP streams (as part of legacy code): each RTP stream can be assigned an arbitrary ID. Many other changes were made.
Release Notes: This release fixes some problems during the build process on different platforms, plus some cosmetic issues.
Release Notes: This is essentially a security-related bugfix, but there are some additional features, including improvements for the RTP measurements. For example, RTP jitter estimation as specified in RFC3550 (smoothed mean deviation) is now supported. This is not the promised great summer update (which will come in August), but only a small update of the 'legacy code' to fix some security bugs. Since the previous version (0.34.6) seems to be potentially vulnerable against stack smashing attacks, everybody is encouraged to upgrade.