anevicon


A high-performant traffic generator, designed to be as convenient and reliable as it is possible. It sends numerous UDP packets to a server, thereby simulating an activity that can be produced by your end users or a group of hackers. This tool can be also used as a bot to build a botnet for simulating [UDP flood attacks](https://en.wikipedia.org/wiki/UDP_flood_attack) (but only for educational and pentesting purposes). This is achieved by the [Anevicon Core Library](https://crates.io/crates/anevicon_core) with which this program depends on.

Pulse · Stargazers · Releases · Contributing


Contents


Features


Installation

Currently, this project requires unstable standard library features, so this is why you must switch to the nightly channel to avoid compilation errors:

bash $ rustup override set nightly-2019-04-11

Building from crates.io

bash $ cargo install anevicon

Building from sources

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

Pre-compiled binaries

The easiest way to run Anevicon on your system is to download the pre-compiled binaries from the existing releases, which doesn't require any external software (unlike the two previous approaches).


Options

``` anevicon 5.1.0 Temirkhan Myrzamadi gymmasssorla@gmail.com A high-performant UDP-based load generator, written in Rust.

USAGE: anevicon [FLAGS] [OPTIONS] --receiver ...

FLAGS: -b, --allow-broadcast Allow sockets to send packets to a broadcast address -h, --help Prints help information --select-if Displays an interactive menu of network interfaces to use. If unset, a default one will be used.

                         This option conflicts with the `--sender` because
                         it will automatically bind an appropriate
                         interface's IP.
-V, --version            Prints version information

OPTIONS: --date-time-format A format for displaying local date and time in log messages. Type man strftime to see the format specification [default: %X] --ip-ttl Specifies the IP_TTL value for all future sockets. Usually this value equals a number of routers that a packet can go through -l, --packet-length Repeatedly send a random-generated packet with a specified bytes length. The default is 32768 -p, --packets-count A count of packets for sending. When this limit is reached, then the program will exit [default: 18446744073709551615] --packets-per-syscall A count of packets which the program will send using only one syscall. After the operation completed, a test summary will have been printed [default: 600] -r, --receiver ... A receiver of generated traffic, specified as an IP-address and a port number, separated by a colon.

        This option can be specified several times to identically test
        multiple receivers in parallel mode.
-f, --send-file <FILENAME>
        Interpret the specified file content as a single packet and
        repeatedly send it to each receiver
-m, --send-message <STRING>
        Interpret the specified UTF-8 encoded text message as a single
        packet and repeatedly send it to each receiver
    --send-periodicity <TIME-SPAN>
        A time interval between sendmmsg syscalls. This option can be used
        to decrease test intensity [default: 0secs]
-t, --send-timeout <TIME-SPAN>
        A timeout of sending every single packet. If a timeout is reached,
        then a packet will be sent later [default: 10secs]
-s, --sender <SOCKET-ADDRESS>
        A sender of generated traffic, specified as an IP-address and a port
        number, separated by a colon [default: 0.0.0.0:0]
-d, --test-duration <TIME-SPAN>
        A whole test duration. When this limit is reached, then the program
        will exit.

        Exit might occur a few seconds later because of long sendmmsg
        syscalls. For more precision, decrease the `--packets-per-syscall`
        value. [default: 64years 64hours 64secs]
-v, --verbosity <LEVEL>
        Enable one of the possible verbosity levels. The zero level doesn't
        print anything, and the last level prints everything [default: 3]
        [possible values: 0, 1, 2, 3, 4, 5]
-w, --wait <TIME-SPAN>
        A waiting time span before a test execution used to prevent a launch
        of an erroneous (unwanted) test [default: 5secs]

For more information see https://github.com/Gymmasssorla/anevicon. ```


Overview

Minimal command

All you need is to provide the testing server address, which consists of an IP address and a port number, separated by the colon character. By default, all sending sockets will have your local address:

```bash

Test the 80 port of the example.com site using your local address

$ anevicon --receiver=93.184.216.34:80 ```

Custom message

By default, Anevicon will generate a random packet with a specified size. 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:

```bash

Test the 80 port of example.com with the custom file 'message.txt'

$ anevicon --receiver=93.184.216.34:80 --send-file="message.txt"

Test the 80 port of example.com with the custom text message

$ anevicon --receiver=93.184.216.34:80 --send-message="How do you do?" ```

Multiple receivers

Anevicon also has the functionality to test multiple receivers in parallel mode, thereby distributing the load on your processor cores. To do so, just specify the --receiver option several times.

```bash

Test the 80 port of example.com and the 13 port of google.com in parallel

$ anevicon --receiver=93.184.216.34:80 --receiver=216.58.207.78:13 ```

Test intensity

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

```bash

Test the example.com waiting for 270 microseconds after each sendmmsg syscall

$ anevicon --receiver=93.184.216.34:80 --send-periodicity=270us ```

End 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):

```bash

Test the 80 port of the example.com site with the two limit options

$ anevicon --receiver=93.184.216.34:80 --test-duration=3min --packets-count=7000 ```

Network interfaces

There is also an ability to bind all future sockets to a specific network interface. Consider the --select-if flag, which displays an interactive menu of network interfaces in a command line:

```bash

Test example.com with a custom network interface using --select-if

$ anevicon --receiver=93.184.216.34:80 --select-if ```

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.

```bash

Use a custom date-time format and the last verbosity level

$ anevicon --receiver=64.233.165.113:80 --date-time-format="%F" --verbosity=5 ```


Using as a library

Just copy this code into your main.rs file and launch the compiled program, which simply sends one thousand empty packets to the example.com site:

(examples/minimal.rs) ```rust

![feature(iovec)]

use std::io::IoVec; use std::net::UdpSocket;

use anevicon_core::{TestSummary, Tester};

fn main() { // Setup the socket connected to the example.com domain let socket = UdpSocket::bind("0.0.0.0:0").unwrap(); socket.connect("93.184.216.34:80").unwrap();

// Setup all the I/O vectors (messages) we want to send
let payload = &mut [
    (0, IoVec::new(b"Generals gathered in their masses")),
    (0, IoVec::new(b"Just like witches at black masses")),
    (0, IoVec::new(b"Evil minds that plot destruction")),
    (0, IoVec::new(b"Sorcerers of death's construction")),
];

// Send all the created messages using only one system call
let mut summary = TestSummary::default();
let mut tester = Tester::new(&socket, &mut summary);

println!(
    "The total packets sent: {}, the total seconds passed: {}",
    tester.send_multiple(payload).unwrap().packets_sent(),
    summary.time_passed().as_secs()
);

} ```

This is how you are able to build your own stress-testing bot. Now you can follow the official documentation to learn more about the anevicon_core abstractions.


Gallery

Statistics

Network interfaces

Being verbose


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.


Target platform

Like most of pentesting utilities, this project is developed, tested, and maintained for only Linux-based systems. If you are a Windows user, you probably need a virtual machine or another computer with GNU/Linux.


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.


Project links


Contacts

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