38 stable releases (7 major)
✓ Uses Rust 2018 edition
|7.0.9||Aug 26, 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|
#50 in Command line utilities
322 downloads per month
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
- Important notes
- Legal disclaimer
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).
- 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.
$ cargo install anevicon
$ git clone https://github.com/Gymmasssorla/anevicon.git $ cd anevicon $ cargo build --release
$ wget https://github.com/Gymmasssorla/anevicon/releases/download/vX.X.X/anevicon-x86_64-linux $ chmod a+x anevicon-x86_64-linux
| ||Allow sockets to send packets to a broadcast address specified using the |
| ||Prints help information|
| ||Prints version information|
| ||String|| ||A format for displaying local date and time in log messages. Type |
| ||String||None||Two endpoints specified as |
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.
| ||Unsigned integer|| ||Specifies the |
| ||Positive integer|| ||A count of packets for sending. When this limit is reached, then the program will immediately stop its execution|
| ||Positive integer|| ||Repeatedly send a random-generated packet with a specified bytes length|
| ||Filename||None||Interpret the specified file content as a single packet and repeatedly send it to each receiver|
| ||String||None||Interpret the specified UTF-8 encoded text message as a single packet and repeatedly send it to each receiver|
| ||Time span|| ||A whole test duration. When this limit is reached, then the program will immediately stop its execution|
| ||Packets|| ||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|
| ||From 0 to 5|| ||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.
| ||Time span|| ||A waiting time span before a test execution used to prevent a launch of an erroneous (unwanted) test|
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"
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
# Test example.com:80 with the 192.168.1.41:17333 source address $ anevicon --endpoints="192.168.1.41:17333&18.104.22.168:80"
You can specify as many endpoints as you want to test several receivers in separate threads. Test both
22.214.171.124:80 (Example.com), and
# Test duckduckgo.com:80, example.com:80, and google.com:80 concurrently $ anevicon \ --endpoints="192.168.1.41:17333&126.96.36.199:80" \ --endpoints="192.168.1.41:17333&188.8.131.52:80" \ --endpoints="192.168.1.41:17333&184.108.40.206:80"
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 (220.127.116.11:80) as a source $ anevicon --endpoints="18.104.22.168:80&22.214.171.124:80"
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&126.96.36.199: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:
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
--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&188.8.131.52:80" --test-duration=3min --packets-count=7000
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
# Test example.com:80 with the custom file 'message.txt' $ anevicon -e="192.168.1.41:17333&184.108.40.206:80" --send-file="message.txt" # Test example.com:80 with the custom text message $ anevicon -e="192.168.1.41:17333&220.127.116.11: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&18.104.22.168:80" --random-packet=1454 --random-packet=29400
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 example.com:80 sending maximum 500 packets per second $ anevicon -e="192.168.1.41:17333&22.214.171.124:80" --test-intensity=500
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&126.96.36.199: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
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.
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.
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.