Anevicon is a high-performance 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.
$ cargo install anevicon
anevicon 0.1.0 Temirkhan Myrzamadi <firstname.lastname@example.org> An UDP-based server stress-testing tool, written in Rust. USAGE: anevicon [FLAGS] [OPTIONS] --receiver <ADDRESS> FLAGS: --debug Enable the debugging mode -h, --help Prints help information -V, --version Prints version information OPTIONS: --display-periodicity <PACKETS> A count of packets per displaying test summaries. It is not recommended to set this option to a small value (say, 6) for the performance reasons. [default: 300] -d, --duration <TIME-SPAN> A program working time. The default value is too big, that is, a test will be performed until you explicitly stop the process. [default: 64years 64hours 64secs] -l, --length <BYTES> A size of each UDP-packet, specified in bytes. Note that your system or a target server might not be able to handle the default value. [default: 65000] -p, --packets <COUNT> A count of packets for sending. The default value equals to the largest number available for the inner data type. [default: 18446744073709551615] -r, --receiver <ADDRESS> A receiver of generated traffic, specified as an IP-address and a port number, separated by the colon character. --send-periodicity <TIME-SPAN> A periodicity of sending packets. The default value equals to zero seconds, that is, all packets will be sent momentarily. [default: 0secs] --send-timeout <TIME-SPAN> If sending calls will continue longer than this timeout, the program will exit with an error. By default, all the sending calls will continue indefinitely. -s, --sender <ADDRESS> A sender of generated traffic, specified as an IP-address and a port number, separated by the colon character. [default: 0.0.0.0:0] -w, --wait <TIME-SPAN> A waiting time before a test execution. It is mainly used to prevent a launch of an erroneous (unwanted) test. [default: 5secs] For more information see <https://github.com/Gymmasssorla/anevicon>.
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:
# Test the 80 port of the example.com site using your local address $ anevicon --receiver 220.127.116.11:80
Using the IP spoofing technique, hackers can protect their bandwidth from server response messages and hide their real IP address. You can imitate it via the
--sender command-line option, as described below:
# Test the 80 port of the example.com site using its own IP address $ anevicon --receiver 18.104.22.168:80 --sender 22.214.171.124:80
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 (a test duration and a packets count, respectively):
# Test the 80 port of the example.com site with the two limit options $ anevicon --receiver 126.96.36.199:80 --duration 3min --packets 7000
Note that the test below will end when, and only when one of two specified end conditions become true. And what is more, you can specify a global packet length in bytes:
# Test the 80 port of example.com with the packet length of 4092 bytes $ anevicon --receiver 188.8.131.52:80 --length 4092
Wait 7 seconds, and then start to test, displaying summaries after every 400 packets, wait 270 macroseconds between sending two packets, and exit with an error if time to send a packet is longer than 200 milliseconds:
# Test the 80 port of the example.com site using the specific options $ anevicon --receiver 184.108.40.206:80 --wait 7s --display-periodicity 400 --send-periodicity 270us --send-timeout 200ms
Since Anevicon is a free (in sense of freedom) kind of software, you are always welcome to contribute! Please look through our code of conduct and the liberal GPLv3 license, under which the product is distributed. Now let's discuss how to make your contribution productive:
Issues are meant for reporting found bugs, errors, and maybe grammar mistakes. You can also push your issues to suggest new functionality in what you interested in. Discussions are welcome too, and I will try to answer you in near future.
Pulls are meant for implementing new functionality, fixing bugs, errors, and maybe grammar mistakes. You can suggest your work without asking for permission or any other coordination. Other people can criticize your code, and you should answer them.
To make code easy to read for any contributor, there is a great tool called rustfmt by the original Rust team, which formats a whole project just in one command (
cargo fmt). Please type this command before pushing any changes to this repository.
The goal of Anevicon is to produce the maximum possible (for the attacking system) load on the specified target address. Thereby, this DOES NOT MEAN that Anevicon will break ABSOLUTELY ANY SERVER while running on your computer.
Anevicon was developed as a means of testing the stress resistance of servers, and not for hacking, that is, the author of the project IS NOT RESPONSIBLE for any damage caused by your use of my program. See the license notice.
Despite the fact that Anevicon is heavily tested both automatically and manually, does not mean that the author is responsible for any bug in his work. The program comes with ABSOLUTELY NO WARRANTY, see the license disclaimer.