37 stable releases (7 major)

✓ Uses Rust 2018 edition

new 7.0.8 Aug 20, 2019
6.0.5 Jul 6, 2019
5.2.2 Jun 12, 2019
4.1.2 Apr 6, 2019
0.1.3 Feb 19, 2019

#17 in Command line utilities

Download history 42/week @ 2019-05-07 63/week @ 2019-05-14 77/week @ 2019-05-21 66/week @ 2019-05-28 66/week @ 2019-06-04 102/week @ 2019-06-11 123/week @ 2019-06-18 144/week @ 2019-06-25 238/week @ 2019-07-02 178/week @ 2019-07-09 38/week @ 2019-07-16 8/week @ 2019-07-23 120/week @ 2019-07-30 184/week @ 2019-08-06 53/week @ 2019-08-13

461 downloads per month

GPL-3.0-only

98KB
2K SLoC

anevicon


An open-source, high-performant traffic generator, designed to be as convenient and reliable as it is possible. It generates numerous UDP packets which lets you test your server against the abnormaly high activity.

Pulse · Stargazers · Releases · Contributing


Table of contents


Advantages

  • Linux-accelerated. Anevicon communicates with a Linux kernel by a few specific system calls to reduce the CPU load significantly. However, it makes the program platform-dependent.

  • Functional. I've tried to implement as many things to make a multi-functional tool and stay simple at the same time. Such features as multiple tests, verbosity levels, and even IP spoofing are supported.

  • Written in Rust. How you can see, all the logic is written completely in Rust, which means that it leverages bare-metal performance and high-level safety (no SIGSEGV, SIGILL, and other "funny" stuff).


Disadvantages

  • Platform-dependend. Like most of pentesting utilities, this project is developed for only Linux-based systems. If you are a Windows user, you probably need a virtual machine or another computer with Linux.

Installation

Building from crates.io

$ cargo install anevicon

Building from sources

$ git clone https://github.com/Gymmasssorla/anevicon.git
$ cd anevicon
$ cargo build --release

Pre-compiled binaries

$ wget https://github.com/Gymmasssorla/anevicon/releases/download/vX.X.X/anevicon-x86_64-linux
$ chmod a+x anevicon-x86_64-linux

Usage

Flags

Name Explanation
-b, --allow-broadcast Allow sockets to send packets to a broadcast address specified using the --endpoints option
-h, --help Prints help information
-V, --version Prints version information

Options

Name Value Default Explanation
--date-time-format String %X A format for displaying local date and time in log messages. Type man strftime to see the format specification
-e, --endpoints String None Two endpoints specified as <SENDER-ADDRESS>&<RECEIVER-ADDRESS>, where address is a string of a <IP>:<PORT> format.

A sender and a receiver can be absolutely any valid IPv4/IPv6 addresses (which is used to send spoofed packets sometimes).

This option can be specified several times to identically test multiple web servers in concurrent mode.
--ip-ttl Unsigned integer 64 Specifies the IP_TTL value for all future sockets. Usually this value equals a number of routers that a packet can go through
-p, --packets-count Positive integer 18 '446 '744 '073 '709 '551 '615 A count of packets for sending. When this limit is reached, then the program will immediately stop its execution
--random-packet Positive integer 1024 Repeatedly send a random-generated packet with a specified bytes length
-f, --send-file Filename None Interpret the specified file content as a single packet and repeatedly send it to each receiver
-m, --send-message String None Interpret the specified UTF-8 encoded text message as a single packet and repeatedly send it to each receiver
-d, --test-duration Time span 64years 64hours 64secs A whole test duration. When this limit is reached, then the program will immediately stop its execution
--test-intensity Packets 1000 A maximum number of packets transmitted per a second. It's guaranteed that a number of packets sent per a second will never exceed this value
-v, --verbosity From 0 to 5 3 Enable one of the possible verbosity levels. The zero level doesn't print anything, and the last level prints everything.

Note that specifying the 4 and 5 verbosity levels might decrease performance, do it only for debugging.
-w, --wait Time span 5secs A waiting time span before a test execution used to prevent a launch of an erroneous (unwanted) test

Overview

First of all, please remember that Anevicon uses raw sockets that require root permissions, so in order to run Anevicon you must already have them. Just type the commands below before running Anevicon:

$ sudo -s
$ PATH+=":/home/gymmasssorla/.cargo/bin"

Minimal command

All you need is to provide a source address and a server address, each of which consists of an IP address and a port number, separated by the colon character. You must specify them as <SENDER-ADDRESS>&<RECEIVER-ADDRESS>:

# Test example.com:80 with the 192.168.1.41:17333 source address
$ anevicon --endpoints="192.168.1.41:17333&93.184.216.34:80"

Multiple endpoints

You can specify as many endpoints as you want to test several receivers in separate threads. Test both 176.34.155.23:80 (DuckDuckGo), 93.184.216.34:80 (Example.com), and 216.58.205.238:80 (Google):

# Test duckduckgo.com:80, example.com:80, and google.com:80 concurrently
$ anevicon \
--endpoints="192.168.1.41:17333&176.34.155.23:80" \
--endpoints="192.168.1.41:17333&93.184.216.34:80" \
--endpoints="192.168.1.41:17333&216.58.205.238:80"

IP address spoofing

Anevicon provides functionality for IP spoofing since the --endpoints option accepts any IPv4/IPv6 addresses. For example, you can specify your source address as Google's:

# Test example.com:80 using the Google's IP (172.217.18.14:80) as a source
$ anevicon --endpoints="172.217.18.14:80&93.184.216.34:80"

Logging options

Consider specifying a custom verbosity level from 0 to 5 (inclusively), which is done by the --verbosity option. There is also the --date-time-format option which tells Anevicon to use your custom date-time format.

# Use a custom date-time format and the last verbosity level
$ anevicon -e="192.168.1.41:17333&93.184.216.34:80" --date-time-format="%F" --verbosity=5

Different verbosity levels print different logging types. As you can see in the table below, the zero verbosity level prints nothing, and the last one prints everything. The levels in the middle print logs selectively:

Errors Warnings Notifications Debugs Traces
Zero (0)
First (1)
Second (2)
Third (3)
Fourth (4)
Fifth (5)

Exit conditions

Note that the command above might not work on your system due to the security reasons. To make your test deterministic, there are two end conditions called --test-duration and --packets-count (a test duration and a packets count, respectively):

# Test example.com:80 with the two limit options
$ anevicon -e="192.168.1.41:17333&93.184.216.34:80" --test-duration=3min --packets-count=7000

Custom messages

By default, Anevicon will generate a random packet with a default size (1024). In some kinds of UDP-based tests, packet content makes sense, and this is how you can specify it using the --send-file or --send-message options:

# Test example.com:80 with the custom file 'message.txt'
$ anevicon -e="192.168.1.41:17333&93.184.216.34:80" --send-file="message.txt"

# Test example.com:80 with the custom text message
$ anevicon -e="192.168.1.41:17333&93.184.216.34:80" --send-message="How do you do?"

Also, you are able to specify one or more random packets with your own lengths using the --random-packet option. This example specifies two random-generated packets with the sizes 1454 and 29400:

# Test example.com:80 with two random packets
$ anevicon -e="192.168.1.41:17333&93.184.216.34:80" --random-packet=1454 --random-packet=29400

Test intensity

In some situations, you don't need to transmit the maximum possible amount of packets per second, you might want to decrease the intensity of packets sending. To do so, there is one more straightforward option called --test-intensity.

# Test example.com:80 sending maximum 500 packets per second
$ anevicon -e="192.168.1.41:17333&93.184.216.34:80" --test-intensity=500

Multiple messages

v5.2.0 introduced the multiple messages functionality, which means that you can specify several messages to be sent to a tested web server (but order is not guaranteed).

# Test example.com:80 with these messages
#   1) A custom file "file.txt";
#   2) A text message "Hello, Pitty! You're my worst friend.";
#   3) A text message "Hello, Scott! This is just a test.";
#   4) A text message "Goodbye, Albret! You're my best friend.";
#   5) A random packet of 5355 bytes;
#   6) A random packet of 2222 bytes.
$ anevicon --endpoints="192.168.1.41:17333&93.184.216.34:80" \
--send-file="file.txt" \
--send-message="Hello, Pitty! You're my worst friend." \
--send-message="Hello, Scott! This is just a test." \
--send-message="Goodbye, Albert! You're my best friend." \
--random-packet=5355 \
--random-packet=2222

Important notes

  • Use the concrete source port number (17333 in the above examples) instead of the unspecified port because UDP packets with the unspecified port might be dropped by your router.

  • Anevicon does not reserve port numbers of your computer and does not handle incoming traffic, it only sends UDP/IPv4 or UDP/IPv6 (at your option) datagrams to a specified web server.


Contributing

You are always welcome for any contribution to this project! But before you start, you should read the appropriate document to know about the preferred development process and the basic communication rules.


Legal disclaimer

Anevicon was developed as a means of testing stress resistance of web servers, and not for hacking, that is, the author of the project IS NOT RESPONSIBLE for any damage caused by your use of his program.


Contacts

Temirkhan Myrzamadi <gymmasssorla@gmail.com> (the author)

Dependencies

~4.5MB
~73K SLoC